RE: [xliff-inline] Various XML constructs in inline content

[Yves Savourel <ysavourel@enlaso.com>]

Hi David, all,

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

Maybe we are talking about two different things here:

I think that you may be saying: if an original XML file has processing instructions, when extracting the file to XLIFF, those PIs should be converted to inline elements. (and I agree: that makes sense. And the same goes possibly for comments)

I was assuming that conversion above was always done. And I was talking about PIs that would be generated during the XLIFF output. In other words, PIs that are not from the original extracted file, but some type of tool-specific inline information that tool would rely on to merge things back.

Such PI shouldn't exist, but if an XLIFF reader finds one, it should strip it out (and possibly even generate some warning/error?)

Is that what you have in mind too?
-yves