Hi,
Thank you for the input.
I looked up
XLIFF Version 1.2
http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html
and it goes like (as in
“2. General Structure”)
<xliff version='1.2'
xmlns='urn:oasis:names:tc:xliff:document:1.2'>
<file original='hello.txt' source-language='en' target-language='fr'
datatype='plaintext'>
<body>
<trans-unit id='hi'>
<source>Hello world</source>
<target>Bonjour le monde</target>
<alt-trans>
<target xml:lang='es'>Hola mundo</target>
</alt-trans>
</trans-unit>
</body>
</file>
</xliff>
The original text is in <source>, (translation) target text is in <target>, alternate translations are
put in <alt-trans>, and all those elements are put in <trans-unit>.
Regards,
Ryu
From: [mailto:]
On Behalf Of Maxwell, Kyle
Sent: Wednesday, February 03, 2016 1:26 AM
To: Chet Ensign; Wunder, John A.
Cc:
Subject: RE: [cti] Idea for Internationalization
I feel like this is something we should pursue. Most (or perhaps all) of these types of issues have been dealt with in other subject fields, so it's
worth learning from the folks who have done this before. (FTR, I have too, but it's been a while and was focused on UI implementation as much as it was on content).
--
Kyle Maxwell []
Senior Analyst, iDefense Applied Security Intelligence
From:
[] on behalf of Chet Ensign []
Sent: Tuesday, February 02, 2016 08:13
To: Wunder, John A.
Cc:
Subject: Re: [cti] Idea for Internationalization
In case this is of interest, OASIS does have active experts in internationalization/translation. The XML Localisation Interchange File Format (XLIFF) TC (https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff)
is working on standards to support multi-lingual data exchange for localisation. If anyone wanted to kick best practices / pros & cons around on that subject, I'm sure you'd find folks on that side happy to talk.
Best,
/chet
