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] [xliff-inline] Representing information for the starting/ending/standalone parts

Hi Frederik,

No problemo - we can extend <x/> in the same way is <itag>.

Best Regards,

Andrzej Zydroń


XTM International


Tel:         +44 (0) 1753 480 469
Fax:        +44 (0) 1753 480 465
Mob:       +44 (0) 7966 477 181
email:     azydron@xtm-intl.com
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 27/10/2011 09:18, Estreen, Fredrik wrote:



I don’t see how using only <g> and <x/> would be a step forward for non XML source formats. Unless the <x> tag is greatly extended with additional attributes like the <itag> that was proposed for TMX 2.0. Consider this old style HTML example:


This <b> is traditional <i>HTML</b> with overlap</i>.


It can of course be tagged using <x> tags but we then lose all information on the pairing of the native codes like this:


This <x id=”1” /> is traditional <x id=”2” />HTML<x id=”3” /> with overlap<x id=”4” />.


Using <g> is not possible since the result would not be XML.



Fredrik Estreen


From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Arle Lommel
Sent: den 26 oktober 2011 22:53
To: Andrzej Zydron
Cc: xliff@lists.oasis-open.org
Subject: Re: [xliff] [xliff-inline] Representing information for the starting/ending/standalone parts


I wasn't arguing to use <itag>, but rather to look at it for anything useful that might help.



On Oct 26, 2011, at 12:33 , Andrzej Zydron wrote:

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ń


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