Hi Arle,
Of Rodolfo's stunning brilliance I have no doubt, but on
reflection my personal choice would not be to invent yet another
element when we already have <g> and <x/>. Everyone
involved with XLIFF knows what these are and what they mean and they
have the added benefit of being backwards compatible with all
versions of XLIFF and even OpenTag.
Best Regards,
Andrzej Zydroń
CTO
XTM International
Tel: +44 (0) 1753 480 469
Fax: +44 (0) 1753 480 465
Mob: +44 (0) 7966 477 181
email:
www: http://www.xtm-intl.com
Skype: zydron
This message contains confidential information and is
intended only for
the individual named. If you are not the named addressee you may
not
disseminate, distribute or copy this e-mail. Please notify the
sender
immediately by e-mail if you have received this e-mail by
mistake and
delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or
error-free as
information could be intercepted, corrupted, lost, destroyed,
arrive
late or incomplete, or contain viruses. The sender therefore
does not
accept liability for any errors or omissions in the contents of
this
message which arise as a result of e-mail transmission. If
verification
is required please request a hard-copy version. Unless
explicitly stated
otherwise this message is provided for informational purposes
only and
should not be construed as a solicitation or offer.
On 26/10/2011 19:04, Arle Lommel wrote:
So does this mean we're looking at something more like
the <itag> proposal Rodolfo and I made for TMX that used
only a single tag that could optionally encapsulate content? If
so, I can dust off the proposal we made then and see what loose
change it has in its pockets that we can use ;-)
I’m not arguing to reuse it (unless it turns out to have been
a work of stunning brilliance due to Rodolfo’s influence, which
is entirely possible) but just to see what might have been
useful in it.
-Arle
On Oct 26, 2011, at 09:52 , Andrzej Zydron wrote:
Hi Bryan, Rudolfo
and Arle,
I would like to carry this through also into TMX 2.0,
which I will be working on in November. Then we will
finally have a sane and secure way of handling inline
coding between XLIFF and TMX.
Rodolfo's point is imminently correct: only <g>
is absolutely necessary. I am still mulling over
<x/>. What do the rest of the committee think?
Best Regards,
Andrzej Zydroń
CTO
XTM International
