RE: [xliff-comment] Determining what <note> elements refer to

["Gerard Cattin des Bois" <gcatt@windows.microsoft.com>]

That makes sense John and Hi to John (1 and 2) 

-----Original Message-----
From: John Reid [mailto:JREID@novell.com] 
Sent: Friday, September 12, 2003 3:25 PM
To: xliff-comment@lists.oasis-open.org
Subject: Re: [xliff-comment] Determining what <note> elements refer to

Hi John,

It's good to hear from you, again.

You wrote: "... However in <trans-unit> elements, the only way to
determine whether a <note> refers to the <source> or the <target> is to
rely on some convention for the 'from' attribute. ..."

Please, can you elaborate on how you see this being utilized? The 1.1
spec says, "All child elements of <trans-unit> pertain to their sibling
<source> element" Thus, a strict reading of this says any <note> in a
<trans-unit> pertains to the <source>. Unless there is consideration to
programmatically differentiate between notes relating to the <source> or
<target>, exclusive of the other, there seems to be little advantage of
adding the attribute. 

You wrote: "Are there any plans to produce a standardized skeleton file
format in future releases?"

There is a usefulness, if not a necessity, for this in the context of
the profiles we wish to specify. In other words, a standardization of
the skeleton file for files of the same file type, makes perfect sense.
However, a standard skeleton file format could be impossible across file
types. For example, the skeleton files generated for a DLL file must be
remarkably different from those produced for an HTML file. However, it
would be advantageous to create a standard skeleton format for HTML,
another for DLLs, and others for those formats we specify profiles for.

cheers,

JohnR



To unsubscribe from this list, send a post to
xliff-comment-unsubscribe@lists.oasis-open.org.