RE: [xliff-inline] Req 1.15 Representation of invalid XML characters

[Yves Savourel <ysavourel@enlaso.com>]

I went ahead and added <cp> support for inside the inline codes <sc>, <ec>, and <ph>, as well as in <data> for the storage outside the content. It wasn't too difficult to implement.

As for the processing expectations I would suggest something like this:

- Writers MUST encode all invalid XML code points of the inline content using <cp>.

- Writers SHOULD NOT encode valid XML code points of the inline content using <cp>.

- Readers MUST process all <cp> elements regardless whether their hex value is a valid or invalid XML code points.

- If the value of the hex attribute is invalid, the Readers MUST generate an error and MAY terminate the process. If the process is not terminated, the code point with the error MUST be replaced with a question mark character (U+003F). [[or should we use U+FFFD?]]

The latest snapshot of Rainbow implement all this.
(http://okapi.opentag.com/snapshot)

Cheers,
-ys