Doug,
Your wording is less convoluted ... I like it.
thanks,
john
>>> "Doug Domeny" <> 4/22/03
10:42:18 AM >>>
John,
Nicely done. The <target> children of
<alt-trans>, however, may also be of a different
language.
How about this...?
Recommendation: It is strongly recommended that content within the <file> element
be uniformly bilingual. In other words, each <source> and <target> element that is a child of <trans-unit> is of the same language as the
source-language and target-language
attributes of the <file>
element, respectively. The xml:lang
attribute should not be used in those elements. The
exception is that <source> and
<target> elements that are children of <alt-trans> may contain an xml:lang attribute of a different
language than that of the source-language and
target-language attributes
of the <file> element.
Example,
<?xml version="1.0" encoding="UTF-8"?>
<xliff
xmlns="urn:oasis:names:tc:xliff:document:1.1" version="1.1">
<file
original="hello.txt" source-language="en" target-language="fr"
datatype="plaintext">
<body>
<trans-unit
id="hi">
<source>hello
world</source>
<target>bonjour
monde</target>
<alt-trans>
<target
xml:lang="es">hola mundo</target>
</alt-trans>
</trans-unit>
</body>
</file>
</xliff>
Regards,
Doug Domeny
Software Analyst
Ektron, Inc.
+1 603
594-0249 x212
http://www.ektron.com
-----Original
Message-----
From: John Reid
[mailto:]
Sent: Tuesday, April 22, 2003 12:13
PM
To: >
Subject: [xliff] Language for bilingual
<file>
Hi Enda & Tony,
Is the following sufficient? Too verbose? Understandable? If not, please
feel free to edit.
"Recommendation: It is strongly recommended that this is a uniformly
bilingual file. In other words: each <source> element child of
<trans-unit> are of the same language as the source-language
attribute of <file>; that the xml:lang attribute of <source> is
not used in those elements; that only <source> children of
<alt-trans> can contain an xml:lang attribute of a different language
than that of the source-language attribute of <file>."
cheers,
john
