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: [xliff] TMX 2.0 does not have an inline element to storecontent? (RE: [xliff] Wiki Document related to "Generic Inline Markup")

On Mon, 6 Apr 2009 16:10:03 -0700
<bryan.s.schnabel@tektronix.com> wrote:

> Hmmm. I guess that helps me to form my position on the matter.
> As for your question to me, how would I markup your Word HTML sample
> in XLIFF?, I see no difficulty.  I would just not worry about the
> unbalanced way Word marks up the bold element.  It is well-formed.
> So I would just capture the empty element the same way I would any
> other element (why should I bother with its intent? It will survive
> the round trip completely intact):
> <trans-unit resname="p" w:rsidR="00C93CE8" w:rsidRDefault="00F331AC">
>  <source>
>    <g ctype="r">
>       <g ctype="t" xml:space="preserve">Hello </g>
>    </g>
>    <g ctype="r" w:rsidRPr="00F331AC">
>       <g ctype="rPr">
>          <x ctype="b"/>
>       </g>
>       <g ctype="t">bold </g>
>    </g>
>    <g ctype="r">
>       <g ctype="t" xml:space="preserve"> world.</g>
>    </g>
>  </source>
> </trans-unit>
> (ignoring complexity added with namespaces for the moment, and
> leaving off required attributes for simplicity)

Hi again,

This markup requires 8 inline tags with nesting. Too many tags. This is
not practical because nested tags complicate editing.

I prefer to deal with just 2 inline tags, one to indicate where
formatting starts and another one to mark where it ends.

Rodolfo M. Raya <rmraya@maxprograms.com>

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