OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [xliff] XLIFF 2.0 Core

Defining the set of XLIFF elements and attributes which are a part of the "Core" is an important starting point for determining what other "Modules" are being considered for XLIFF 2.0. In my opinion, the most basic use of XLIFF is when product developers are defining the text to be translated for their product. They have only general globalization knowledge, but they do clearly understand the original file format

As a starting point, I would like to suggest that the "Core" consists of the following elements and attributes.

  1. <xliff> Root element.
    1. version. It is necessary to know the version of XLIFF which the file is defined with.
  2. <file>
    1. datatype. It should be required to define the original file format for the text in this file.
    2. original. The file name of the original file that this XLIFF file was created from.
      If this file was not created from another file, then this could have a required value of something like "none".
    3. source-language. The language of the source text must be defined.
    4. target-language. If this is a required attribute, then initially it would have the same value as "source-language".
      The assumption would be that its value would be changed when the file is translated.
  3. <body>
  4. <trans-unit> Container for one block of translatable text.
    1. id. The identifier for this unit of text.
  5. <source> Source text.
  6. <target> Translated text. For the non-translated version of this file, we should consider whether:
    a. This element is optional.
    b. This should be an empty element with no content.
    c. This should be the same as the <source> section.
  7. Inline elements The set of inline elements that the inline sub-committee comes up with.
    All inline items must be handled by XLIFF inline elements.


Example:

<?xml version="1.0" encoding="UTF-8"?>
<xliff version="1.2">
<file original="example.html" datatype="html" source-lang="en-US" target-language="en-US">
<body>
<trans-unit id="1">
<source>Sample document</source>
<target>Sample document</target>
</trans-unit>
</body>
</file>
</xliff>


I look forward to your comments.

David

Corporate Globalization Tool Development
EMail: waltersd@us.ibm.com
Phone: (507) 253-7278, T/L:553-7278, Fax: (507) 253-1721

CHKPII: http://w3-03.ibm.com/globalization/page/2011
TM file formats: http://w3-03.ibm.com/globalization/page/2083
TM markups: http://w3-03.ibm.com/globalization/page/2071

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]