<HTML>
<HEAD>
<TITLE>Re: Machine Translation</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Den 2009-09-10 10.40, skrev "Felix Sasaki" <<a href="felix.sasaki@fh-potsdam.de">felix.sasaki@fh-potsdam.de</a>>:<BR>
<BR>
</SPAN></FONT><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">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><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>
<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>
<BR>
/kent k<BR>
</FONT></SPAN></FONT>
</BODY>
</HTML>