- From: <bugzilla@jessica.w3.org>
- Date: Wed, 03 Aug 2011 16:38:15 +0000
- To: public-i18n-core@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12417
--- Comment #41 from Kevin Lenzo <kevinlenzo@gmail.com> 2011-08-03 16:38:15 UTC ---
I'm honestly not certain if 'localize' is better than 'translate', because of
the existence of its:translate, but 'localize' has a couple of things going for
it:
- in cases of things like URIs, the things really are localized rather than
translated;
- this tag may be applied to other things like images that are not necessarily
textual;
- and it has the direction-neutral property (input and output docs can
logically have the same values).
I suppose another possibility for indicating the source vs. target distinction
would be to extend the value structure of the attribute, from 'yes' and 'no' to
include one that indicates that this is the target ('done'? 'target'?) but this
seems awkward.
My general preference would be that the HTML5 document could simply be
localized in place, without having to insert additional state attributes or
value structures. That is, the value of localize= is stable between the source
and target document, and is semantically appropriate.
--
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 Wednesday, 3 August 2011 16:38:19 UTC