- From: <bugzilla@jessica.w3.org>
- Date: Sun, 04 Dec 2011 09:14:02 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12417 --- Comment #54 from Jirka Kosek <jirka@kosek.cz> 2011-12-04 09:14:01 UTC --- (In reply to comment #52) > So the use case for inline fragments marked as not to be translated is things > like product names or quotations from other languages or people's names, etc. > It makes sense to have a dedicated way to mark that up because as automated > translation and assisted translation becomes more widely used, and as sites > become more widely translated, human and computerised translators need > assistance in determining what the original author didn't want translated. Yves already provided examples in #53. Just to speak about technical implementation -- non-translateable content can be both inline (just phrase, few words) and block (complete paragraph, few consecutive paragraphs). Dedicated attribute seems as the most natural way how to support this. -- 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 Sunday, 4 December 2011 09:14:07 UTC