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: RE: Re: [xliff] Wiki Document related to "Generic Inline Markup"

Hi Rodolfo,

I hope you don't mind, but I thought this should be cc'd to the list, so we might be most productive in the meeting.

I have replies for a few of the items in your note to Asgeir.  And I also wonder if we will need a way of tracking comments in the wiki, regarding each of the items under the "Generic Inline Markup" wiki page, as I can see this getting difficult to follow.

Here are the two items that jumped out at me.

You said:
> Section 3.5: in TMX the idea of an inline tag
> is to have a container for markup. This section
> is against the requirements of TMX.

{Schnabel - This comment is problematic for me. I hope it's just a matter of me not understanding what you mean.  It kind of sounds like you're saying the *only* way TMX wants to use inline elements is as a container for markup.  And that inline elements will always be de-element-ized in TMX.  In the following example, <b> is an element:
<p>This is a <b>FUN</b> game</p>

Now it is not:
(A) <seg>This is a <itag pos='start' type='b' />FUN<itag pos='end' type='b' /> game</seg>

Now it is:
(B) <seg>This is a <itag type='b'>FUN</itag> game</seg>

Are you saying that the philosophy of TMX is that (A) is good, and (B) is against the requirements?

If that is the case, in my mind it will be nearly impossible to find common ground with XLIFF

And you said:
> Section 3.11: contradicts section 3.5

{Schnabel - I think this does not contradict 3.5.  I think it just says that both methods should be allowed (storing inline elements as proper XML nodes, or if necessary escaping and storing inline markup (in my mind, like processing malformed XML, or something like RTF)).



-----Original Message-----
From: Rodolfo M. Raya [mailto:rmraya@maxprograms.com]
Sent: Monday, April 06, 2009 4:29 AM
To: Schnabel, Bryan S
Subject: Fw: Re: [xliff] Wiki Document related to "Generic Inline Markup"

Hi Bryan,

Please find below an email I sent to Asgeir with comments about the
text on the wiki.



Date: Thu, 26 Mar 2009 21:09:33 -0300
From: "Rodolfo M. Raya" <rmraya@maxprograms.com>
To: Asgeir Frimannsson <asgeirf@redhat.com>
Subject: Re: [xliff] Wiki Document related to "Generic Inline Markup"

On Thu, 26 Mar 2009 19:28:15 -0400 (EDT)
Asgeir Frimannsson <asgeirf@redhat.com> wrote:

> As a general note to the TC process, I think it would be useful to
> (as a general rule) bring items of discussion up in emails and/or the
> wiki before meetings rather than spending the whole meeting going
> through a list with at times 'unprocessed' ideas being presented.

Some comments that you may consider when updating the wiki:

Section 3.3: in XLIFF you can use a <ph> element for each isolated code

Section 3.5: in TMX the idea of an inline tag is to have a container
for markup. This section is against the requirements of TMX.

Section 3.8: a text-equivalent of the inline code is stored in the
"equiv-text" attribute of <itag>

Section 3.9: the "x" attribute of <itag> and <hi> identifies the tag.
It may be combined with the "pos" attribute if paired <itag> elements.

Section 3.10: the "x" attribute of <itag> and <hi> are used to
associate same codes in different <tuv> elements (no source/target in

Section 3.11: contradicts section 3.5

Section 3.12: In XLIFF you may want to associate a tag with content in
the skeleton, but there is no skeleton in TMX. This is not needed in

Section 3.13: In TMX <itag> can be empty, discarding the actual markup.
In current XLIFF markup must be stored somewhere, either in the tag or
in the skeleton.

Section 3.14: There are no nested "segments" in TMX. Subflows are not
segments, they are parts of a segment.

Section 3.15: Subflows are not segments in TMX. A subflow is an
integral part of a segment.

Section 3.17: In TMX text is already segmented. Segmentation rules can
be stored in the header of the file. Inline elements don't contain
segmentation information, they just contain inline markup. The values
of the "type" attribute refer to the content of an inline tag, they are
not related to segmentation in any way.

Rodolfo M. Raya <rmraya@maxprograms.com>

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