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


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-comment message

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

Subject: Re: A few questions about XLIFF standard

Hi Elena, 

Thank you for your questions and for choosing XLIFF. 

The XLIFF Technical Committee is the group that develops and maintains the standard. I am copying the TC's comment mailing list on this reply. Comments and questions on the standard can always be sent to this list. 

You need to subscribe to the list to send emails directly. This can be done by sending an empty email to xliff-comment-subscribe@lists.oasis-open.org. Reply to the confirmation email you receive and you will be subscribed. 

Members of the XLIFF TC, please see Elena's questions attached. 

Best regards, 


On Wed, Mar 13, 2013 at 5:28 AM, Elena Makarenko <emakarenko@across.net> wrote:

Dear Mr. Ensign,


I am writing you on behalf of the development team which is now working on the XLIFF format processing.


Could you please clarify a few questions we have regarding the correct treatment of XLIFF tags?

1.       Some declared tags have the ‘clone’ attribute which indicates whether this tag can be copied several times or not.

But what about tags without this attribute: <bpt>, <ept>, etc.? Are they ‘clonable’ by default?

2.       It is also not clear why the <bx/> tag has the ‘clone’ attribute, but <ex/> does not have it?

a.       What is the purpose of this tag? Could you please provide an example which shows its usage?

b.      Should the related <bx/>/<ex/> tags be within one <source> element or it is allowed to have them occur even in different <trans-unit>-s?

3.       Could  a <target> element contain tags which are not present in the corresponding <source> element?

Here is an example (tags not present in <source> are highlighted):
<source>The <x id="1" />formatted<x id="2" /> <bpt id="1" ctype="italic">{}</bpt>sentence<ept id="1">{}</ept> <bpt id="2" ctype="bold">{}</bpt>with<ept id="2">{}</ept> two fields.</source>

<target>The <x id="1" />formatted<x id="2" /> <bpt id="1" ctype="italic">{}</bpt>sentence<ept id="1">{}</ept> <bpt id="2" ctype="bold">{}</bpt>with<ept id="2">{}</ept> two <bpt id="3" ctype="italic">{}</bpt> another <ept id="3">{}</ept> <bpt id="4" ctype="bold">{}</bpt>fields <ept id="4">{}</ept>new <x id="3" />text<x id="-1" />.</target>

If this situation is possible and is considered valid, can you please tell us whether this behavior applies for all XLIFF tags or for a subset of them only?


We would also like to ask you to recommend a reliable tool for XLIFF validation, if it is possible.


Thank you for your consideration.

We look forward to your reply.


Sincerely yours,

Elena Makarenko,
Software Developer

Across Systems GmbH
> Language Technology for a Globalized World

email             emakarenko@across.net 
web               www.across.net


Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open

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