OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-inline message

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


Subject: Re: [xliff-inline] Various XML constructs in inline content


With respect to processing instructions. It seems like just stripping them out could have a negative effect when the translated text is integrated with the skeleton file. It seems more reasonable that XLIFF should require that processing instructions should be converted to standard XLIFF inline elements so that processing instructions can be preserved during the translation process.

David

Corporate Globalization Tool Development
EMail: waltersd@us.ibm.com
Phone: (507) 253-7278, T/L:553-7278, Fax: (507) 253-1721

CHKPII: http://w3-03.ibm.com/globalization/page/2011
TM file formats: http://w3-03.ibm.com/globalization/page/2083
TM markups: http://w3-03.ibm.com/globalization/page/2071


Inactive hide details for Yves Savourel ---07/26/2011 03:28:28 PM---Hi all, Another aspect we have to address is the various XMYves Savourel ---07/26/2011 03:28:28 PM---Hi all, Another aspect we have to address is the various XML constructs one can find in mixed conten


    From:

Yves Savourel <ysavourel@enlaso.com>

    To:

<xliff-inline@lists.oasis-open.org>

    Date:

07/26/2011 03:28 PM

    Subject:

[xliff-inline] Various XML constructs in inline content





Hi all,

Another aspect we have to address is the various XML constructs one can find in mixed content (comments, processing instructions, CDATA sections) and what are the processing expectation for them.

Here is my take:

-- comments

XML comments must be stripped out.
An XLIFF processor must strip XML comments (<!--...-->) found inside a content.
Any comment that need to survive processing needs to be set using the XLIFF notes mechanism.


-- Processing Instructions

XML processing instructions must be stripped out.
An XLIFF processor must strip XML processing instructions (<?...?>) found inside a content.
Tool-specific data should be set using XLIFF's extension mechanism.


-- CDATA sections

CDATA sections (<![CDATA[...]]>) are allowed, but on output they may be changed into normal escaped content by the processor agents.
An XLIFF processor must read properly CDATA sections inside an inline content, but it is not required to preserve the notation when writing out the document.


Any thoughts?
-yves



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





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