The current draft states<div><br><div>"<span class="Apple-style-span" style="font-family: monospace; font-size: 16px; white-space: pre; ">Language tags, as defined by [<a href="http://tools.ietf.org/html/draft-davis-t-langtag-ext-02#ref-BCP47" title=""Tags for the Identification of Language (BCP47)"">BCP47</a>], are useful for identifying the</span></div>
<span class="Apple-style-span" style="font-family: Times; font-size: 16px; "><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; "> language of content. There are mechanisms for specifying variant
subtags for special purposes. However, these variants are
insufficient for specifying text transformations, including content </pre></span><div><span class="Apple-style-span" style="font-family: monospace; font-size: 16px; white-space: pre; "> that has been transliterated, transcribed, or translated.</span>"<br>
<br></div><div>I am requesting a clarification from the editors, that includes a liaison with the Unicode ULI TC <a href="http://uli.unicode.org/">http://uli.unicode.org/</a> , and a clarification in the draft.</div><div>
<br></div><div>Language tags so far have described *states*: an object is in a language, a script etc. The proposed extension extends languages to describe the outcome of a *process*: objects have been transformed, with a source object as the basis for this process. According to the paragraph above, this transformation includes also translation.</div>
<div><br></div><div>So far formats like TBX, XLIFF or others have been used for aligning source and target contents. These formats also use language tags, via xml:lang. However, the transformation, i.e. the process information, is not expressed via the language tag, but via XML structures (pairs of source and target elements). The language tags are purely for identifying the state of an object.</div>
<div><br></div><div>To avoid confusion for users of the above and other, process related formats about where to put language identification information and where to put process related information, I am asking you to</div>
<div>1) Liaise with the ULI TC about the issue described above and see what issues they see here</div><div>2) Document the outcome of this liaison on this list and in the draft </div><div>There is no need to have long explanations in the draft, but guidance about the topic will be very helpful to avoid confusion.</div>
<div><br></div><div>As a side note, formats like TBX, XLIFF and others reduce the usage of a language tag for good reasons: information related to processes like translation can be very complex, e.g. expressing translation state, cycle, quality. So I have the general concern that language tags might be overloaded with key value pairs in areas that would require more complex information and that potentially overlap with formats that provide that information. Nevertheless I won't object against moving this extension forward, if the concerns are explained properly in the draft.</div>
<div><br></div><div>Felix</div><div><br><div class="gmail_quote">2011/7/12 Mark Davis ☕ <span dir="ltr"><<a href="mailto:mark@macchiato.com">mark@macchiato.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font face="'times new roman', serif">We've posted a new version of <a href="http://tools.ietf.org/html/draft-davis-t-langtag-ext" target="_blank">http://tools.ietf.org/html/draft-davis-t-langtag-ext</a></font><div>
<font face="'times new roman', serif"><br></font></div><div><font face="'times new roman', serif">Diffs are here: <a href="http://tools.ietf.org/rfcdiff?url2=draft-davis-t-langtag-ext-02.txt" target="_blank">http://tools.ietf.org/rfcdiff?url2=draft-davis-t-langtag-ext-02.txt</a><br>
</font><div><font face="'times new roman', serif"><br></font></div><div><font face="'times new roman', serif">The changes are:</font></div><div><font face="'times new roman', serif"><br>
</font></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:'times new roman', serif;font-size:13px">* Made it clear that application to the case of speech was included, added Peter C's example.</span><font face="'times new roman', serif"><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-size:13px"><div>
<font face="times new roman,serif">* Fixed references, adding authors, removing unneeded reference.</font></div><div><font face="times new roman,serif">* Changed ABNF. Mostly just the table form, but also defined alphanum.</font></div>
<div><font face="times new roman,serif">* Made it clear that the CLDR committee must post proposals publicly.</font></div><div><font face="times new roman,serif">* Added more information on the XML structure, including the description attribute. (Note that the CLDR committee had decided to add the description attribute before this process began.)</font></div>
<div><font face="times new roman,serif">* Added fixes for typos noted by CEW.</font></div><div><font face="times new roman,serif"><br></font></div><div><font face="times new roman,serif">Please let us know of further feedback.</font></div>
<div><font face="times new roman,serif"><br></font></div></span></font><font face="'times new roman', serif"><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-size:13px"><div>
<font face="times new roman,serif">Note to Doug: The CLDR committee had agreed to move the descriptions into the bcp47 files, such as <a href="http://unicode.org/repos/cldr/trunk/common/bcp47/calendar.xml" target="_blank">http://unicode.org/repos/cldr/trunk/common/bcp47/calendar.xml</a>. Yoshito has the action to do that, and was able to accelerate it. So please take a look if you have the time.</font></div>
<div><font face="times new roman,serif"><br></font></div><div><font face="times new roman,serif">Mark</font></div></span></font><font face="'times new roman', serif"><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-size:13px"><div>
<font face="times new roman,serif"><br></font></div><div><font face="times new roman,serif"><br></font></div></span></font></div></div>
<br>_______________________________________________<br>
Ltru mailing list<br>
<a href="mailto:Ltru@ietf.org">Ltru@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/ltru" target="_blank">https://www.ietf.org/mailman/listinfo/ltru</a><br>
<br></blockquote></div><br></div></div>