- From: <bugzilla@jessica.w3.org>
- Date: Wed, 27 Jul 2011 11:03:44 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12417 --- Comment #12 from Karl Dubost <karl+w3c@la-grange.net> 2011-07-27 11:03:42 UTC --- (In reply to comment #9) > > Using class="notranslate" isn't an abuse as far as I can tell. > > The class attribute is used for other things. Overloading it with "notranslate" is not a viable solution. I think the question that hixie had, was does it answer the use cases? In which ways, what does it break, what does it improve? (with code scenarios) > > This seems like a feature that would get only narrow use. > > Is it really worth adding to the language? > > I disagree. Several content providers are using workaround because a standard > solution does not exist. Is there a document with what the content providers are doing? What code (workaround) are they using? How to solve it with code without focusing on one possible solution? > > It seems like the ideal solution would be a new > > language subtag, frankly. > > Using a subtag is not the solution either. It overloads the value with > information that has nothing to do with the language. In which ways? Could you give more details. (code+explanation) -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 27 July 2011 11:03:49 UTC