[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff] [xliff-inline] Representing information for the starting/ending/standalone parts
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.
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 ;-)