- From: <bugzilla@jessica.w3.org>
- Date: Thu, 28 Jul 2011 20:42:08 +0000
- To: public-i18n-core@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12417 --- Comment #31 from Felix Sasaki <felix.sasaki@dfki.de> 2011-07-28 20:42:08 UTC --- (In reply to comment #29) > Question which might be borderline but do not hesitate to tell me if there is > something wrong with the reasoning. > > <p lang="en"> > <span title="Organization for the human rights" > translate="no">Amnesty International</span>, > in a report, said… > </p> > > > Automatic translation to French for example > > <p lang="fr"> > <span title=" […] " > translate="no">Amnesty International</span> > a dit dans un rapport… > </p> > > is title translated or not into "Organisation pour les droits de l'homme"? > > and this might be even trickier with nested blocks where the parents has > translate="no". Think about images with an alt="" text in a block of text with > a translate="no". > > How is it done with the current choices and/or hacks mentioned earlier? The choices and hacks focus only on element content. In this respect they are identical to the "spelling and grammar checking" mechanism, that is: not addressing attribute content - taken from http://dev.w3.org/html5/spec/Overview.html#spelling-and-grammar-checking : "To determine if a word, sentence, or other piece of text in an applicable *element* (as defined above) is to have spelling- and/or grammar-checking enabled, the UA must use the following algorithm: ..." There are various mechanism one could envisage to cover attributes, e.g. defaults, or "global rules" using e.g. CSS selectors to depict attributes. But I think this would be the next step, once we agree on a basic mechanism for element content. This would already be of value, like in the case of spell checking. > > PS: not pushing back, just trying to see the consequences for each decision. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Thursday, 28 July 2011 20:42:10 UTC