Re: [xliff-inline] Id attribute between source and target

[David Walters <waltersd@us.ibm.com>]

In what situations would a translator be adding new tags to the target text which do not exist in the source text?  How does the tool which converts the XLIFF information into the required output file format know how to handle these new items, or is it expected that the translator knows how to add inline XLIFF elements with the correct encapsulated text?

An example would  be helpful.

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


"Estreen, Fredrik" ---10/19/2011 11:52:55 AM---Hi, When reading through the current working draft I started thinking about the wording regarding th

From:	"Estreen, Fredrik" <Fredrik.Estreen@lionbridge.com>
To:	"xliff-inline@lists.oasis-open.org" <xliff-inline@lists.oasis-open.org>
Date:	10/19/2011 11:52 AM
Subject:	[xliff-inline] Id attribute between source and target
Sent by:	<xliff-inline@lists.oasis-open.org>

---

Hi,
 
When reading through the current working draft I started thinking about the wording regarding the ID of inline codes in the target.
 
“The value of the id attribute for this code in the target MUST be the same as its corresponding code in the source.”
 
I think we might need to reword this to allow new tags with unique Id’s in the target that do not exist in the source. This is very common for some languages. Something like:
 
“The value of the id attribute for this code in the target MUST be the same as its corresponding code in the source if it has one. If it does not have a corresponding code in source it’s id must be unique within both source and target.”
 
Regards,
Fredrik Estreen