<br><br><div class="gmail_quote">2009/9/11 Kent Karlsson <span dir="ltr"><<a href="mailto:kent.karlsson14@comhem.se">kent.karlsson14@comhem.se</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size: 11pt;"><br>
Den 2009-09-10 10.40, skrev "Felix Sasaki" <<a href="http://felix.sasaki@fh-potsdam.de" target="_blank">felix.sasaki@fh-potsdam.de</a>>:<br>
<br>
</span></font><div class="im"><blockquote><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size: 11pt;">There is another reason not to have a machine translation subtag: That kind of information is already covered by vocabularies like XLIFF, see <br>
<a href="http://docs.oasis-open.org/xliff/v1.2/cs02/xliff-core.html" target="_blank">http://docs.oasis-open.org/xliff/v1.2/cs02/xliff-core.html</a><br>
and search for "leveraged-mt". <br>
<br>
Felix<br>
<br>
</span></font></blockquote></div><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size: 11pt;"><br>
To quote the table in full:<br>
==================================<br>
</span></font><font color="#66116d"><font face="Arial Bold"><span style="font-size: 11.5pt;">state-qualifier<br>
</span></font></font><font size="2"><font face="Arial Italic"><span style="font-size: 10pt;"><br>
State-qualifie</span></font><span style="font-size: 10pt;"><font face="Arial">r - Describes the state of a particular translation in a</font><font color="#1d00ee"><font face="Courier, Courier New"><u> <target</u></font></font><font face="Arial">> or</font><font color="#1d00ee"><font face="Courier, Courier New"><u> <bin-target</u></font></font><font face="Arial">> element.<br>
</font><font face="Arial Bold"><br>
Value description</font><font face="Arial">:<br>
<br>
The pre-defined values are defined in the table belo</font><font face="Arial Bold">w.<br>
<br>
Value </font><font face="Arial"><b>Description<br>
</b></font><font face="Courier, Courier New">exact-match</font><font face="Arial"> Indicates an exact match. An exact match occurs when a source text of a segment is exactly the same as the source text of a segment that was translated previously.<br>
</font><font face="Courier, Courier New">fuzzy-match</font><font face="Arial"> Indicates a fuzzy match. A fuzzy match occurs when a source text of a segment is very similar to the source text of a segment that was translated previously (e.g. when the difference is casing, a few changed words, white-space discripancy, etc.).<br>
</font><font face="Courier, Courier New">id-match</font><font face="Arial"> Indicates a match based on matching IDs (in addition to matching text).<br>
</font><font face="Courier, Courier New">leveraged-glossary</font><font face="Arial"> Indicates a translation derived from a glossary.<br>
</font><font face="Courier, Courier New">leveraged-inherited</font><font face="Arial"> Indicates a translation derived from existing translation.<br>
</font><font face="Courier, Courier New">leveraged-mt</font><font face="Arial"> Indicates a translation derived from machine translation.<br>
</font><font face="Courier, Courier New">leveraged-repository</font><font face="Arial"> Indicates a translation derived from a translation repository.<br>
</font><font face="Courier, Courier New">leveraged-tm</font><font face="Arial"> Indicates a translation derived from a translation memory.<br>
</font><font face="Courier, Courier New">mt-suggestion</font><font face="Arial"> Indicates the translation is suggested by machine translation.<br>
</font><font face="Courier, Courier New">rejected-grammar</font><font face="Arial"> Indicates that the item has been rejected because of incorrect grammar.<br>
</font><font face="Courier, Courier New">rejected-inaccurate</font><font face="Arial"> Indicates that the item has been rejected because it is incorrect.<br>
</font><font face="Courier, Courier New">rejected-length</font><font face="Arial"> Indicates that the item has been rejected because it is too long or too short.<br>
</font><font face="Courier, Courier New">rejected-spelling</font><font face="Arial"> Indicates that the item has been rejected because of incorrect spelling.<br>
</font><font face="Courier, Courier New">tm-suggestion</font><font face="Arial"> Indicates the translation is suggested by translation memory.<br>
In addition, user-defined values can be used with this attribute. A user-defined value must start with </font><font face="Courier, Courier New">an</font><font face="Arial"> "x-" prefix.<br>
<br>
===================<br>
<br>
("mt-suggestion" seems to be closer in intent than "leveraged-mt" to the suggestion in the origin of this thread)<br>
<br>
The problem with this is that it applies to XLIFF (XML Localization Interchange File Format) only. A language tag extension, in contrast, can be used<br>
anywhere language tags can already be used.<br></font></span></font></div></blockquote><div><br><br>Yes, but in XLIFF it is a common to store such information in a separate field, that is not as part of a language identifier (which are used as well in XLIFF, via xml:lang). Having a language identifier with similar information would create confusion.<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><font size="2"><span style="font-size: 10pt;"><font face="Arial">
<br>
I think variant subtag(s) for this is quite inappropriate. It is not a language (or orthography) variant; it is a translation status indication that is being discussed in this thread.<br></font></span></font></div></blockquote>
<div> <br><br>I did not propose the table as an input for variant subtags. I rather think that people who mostly need the use case discussed in this thread (the localization industry) lalready have the means the need - they just do not rely on language tags for the purpose of identifying machine translated content.<br>
<br>Felix<br></div></div>