- From: <bugzilla@jessica.w3.org>
- Date: Fri, 27 Jan 2012 06:23:08 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12417 --- Comment #77 from Felix Sasaki <felix.sasaki@dfki.de> 2012-01-27 06:23:06 UTC --- (In reply to comment #76) > (In reply to comment #75) > > Well, if authors don't do what they can do now, there's nothing we can add to > > the language to help them! > When I said "dealing with existing web content" I wasn't talking to the > language and a mechanism for authors, but about consumers of web pages for > translation process purposes - sorry for not being clear. I think Yves' > question > https://www.w3.org/Bugs/Public/show_bug.cgi?id=12417#c65 > was from that consumer perspective. Again, I agree that there is no need to > complicate things for browser implementors and for Web authors - having just > the "translate" attribute with the semantics you describe is already a big win. This may have not been very clear, so let me rephrase: - A is authoring a web page, not following the best practice "don't create attributes with translatable content" - B needs to prepare the web page for subsequent translation, specifying what has to be translated or not. In terms of the industry, B are e.g. localization service providers. - C does the actual translation - as a human translator, a machine translation system, or both. the "translate" attribute is to be used by A and make the life of B and C easier. The mechanism I (and again, I think Yves) talked about is for B. -- Configure bugmail: https://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 Friday, 27 January 2012 06:23:10 UTC