 |
|
|
Hi,
some threads above Gerald Aichholzer mentioned an article he found about
XLIFF (XML Localisation Interchange File Format) at
http://www-106.ibm.com/developerworks/xml/library/x-localis/.
XLIFF seems to translate documents that already contain
language-specific data. That means everytime a user does not use the
standard language I'd have to throw away my standard-data and replace
them with the other data.
Isn't this a bit too much work? I solve it like this:
In the first step some component generates XML data without any
language- or display-specific content. In the second step I want to add
the specialized content. In the third step I want to create the GUI code
(HTML, WML, whatever).
What I want to know is if you know about any standards for I18N via XML,
or any good techniques proven in practice.
Greetings,
Sebastian
|
|
| |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
| |
| |
|
|
|
