StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><code><alt-trans></code> is not intended for having <code><target></code>s in more than one language in each trans-unit; it's rather intended for <a href="http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#alt-trans" rel="noreferrer">translation match</a> be it translation memory, machine translation matches, or simple an outdated target string which needs to be updated according to most recent changes in the source string. Having said that, in some cases <code><alt-trans></code> is perceived as a <a href="http://www.opentag.com/xliff.htm#WhyBilingual" rel="noreferrer">workaround</a> for translating what the industry calls "adaptive languages" (French for Canada is often adapted from French translation) without having separate files. As a localization practitioner who has to deal with Xliffs from various sources and presented in various schemas, I recommend to avoid this hack. It is more common and accepted to use the <code><file></code> tag to embed trans-units for multiple languages in one Xliff file:</p> <pre><code><?xml version="1.0" encoding="utf-8" ?> <xliff version="1.1" xml:lang='en'> <file source-language='en' target-language='de' datatype="plaintext" original="Sample.po"> ... <body> <trans-unit id="1" restype="button" resname="IDC_TITLE"> <source>Title</source> </trans-unit> <trans-unit id="2" restype="label" resname="IDC_STATIC"> <source>&amp;Path:</source> </trans-unit> ... </file> <file source-language='en' target-language='fr' datatype="plaintext" original="Sample.po"> <trans-unit id="1" restype="button" resname="IDC_TITLE"> ... </body> </file> </xliff> </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload