RE: [xliff] TMX 2.0 does not have an inline element to storecontent? (RE: [xliff] Wiki Document related to "Generic Inline Markup")

[<bryan.s.schnabel@tektronix.com>]

Hi Rodolfo,

> 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.

I guess complexity and comfort depend on what tools a developer uses. Dealing with nesting is not that complicated in my world.  I like to process XML source with XML tools.  That way I stand a better chance of not breaking things (or accidentally rendering XML to be malformed). It would be easy enough to write a perl script to turn fake markup into markup. But the risk is that the start and end gets miscalculated or separated.  That's what I consider complicated and not practical.

So I guess the question is, are we creating these standards for people with your taste, or people with my taste, or both?  If the answer is both, then not supporting the option I so strongly advocate for is probably a mistake.

Bryan

-----Original Message-----
From: Rodolfo M. Raya [mailto:rmraya@maxprograms.com]
Sent: Monday, April 06, 2009 4:35 PM
To: xliff@lists.oasis-open.org
Subject: Re: [xliff] TMX 2.0 does not have an inline element to store content? (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.

Regards,
Rodolfo
--
Rodolfo M. Raya <rmraya@maxprograms.com>
http://www.maxprograms.com

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php