xliff-inline — archive

[Yves Savourel]

XLIFF Inline Markup Subcommittee Teleconference Summary === 1) Administration Attending: Andrew, Milan, Arle, Yves, Lucia, Dimitra Regrets: Asgeir === 2) Discussion: Requirements Requirement working page: http://wiki.oasis-open.org/xliff/OneContentModel/Requirements We had several action items: -- ACTION ITEM: Yves to find a real example for requirement #4 --> Sorry, still not done at this time (forgot). Andrew: The bookmark element in ODF is a good illustration. Yves: thanks, will use that then. -- ACTION ITEM: Arle to bring any additional requirements from OSCAR. Arle: Nothing at the moments. Arle: Have to step out for a moment. -- Discussion on requirement #13: http://lists.oasis-open.org/archives/xliff-inline/201008/msg00016.html Andrew: Should it me just text? Include codes as well. Consensus on: "Must be able to represent separately different flows of text and codes when, in the original format, they are mixed together. Example 1: In DITA a footnote is stored at the location where it is referred to: Palouse horses have spotted coats. This p element contains two separate flows: "Palouse horses have spotted coats" and "A Palouse horse is the same as an Appaloosa." Example 2: The value of the HTML ALT attribute is stored in the IMG tag and can be within a paragraph: Click here: . -- Discussion on requirement #14: Milan: should be optional. Andrew: is the direction important? Milan: could be with different context, so specifying exact relationships may be difficult. Consensus on: Should be able to represent the mutual relationships between a nested flow of text and its parent The format should be able to represent both flows and have some information about their relationships, so the two text can be put in context when needed. For example, the relation between the value of an HTML ALT attribute and the paragraph element where it appears should be somehow preserved: Click here: . -- Discussion on requirement #15: Milan: for a unique char or string of invalid? Andrew: experience is one by one. ACTION ITEM: Yves to check the term used in XML specification "illegal" or "invalid", and use it everywhere. Consensus on: Should be able to represent illegal XML characters in the content Some characters are illegal in XML, but they may appear in extracted text and we should have a common way to represent them so they can be preserved and merged back if necessary, without causing the XML tools to fail. For example in the following Java property string "Text with \u001a" the character U+001A is illegal in XML but needs to have a representation in XLIFF. Note: An example of how some XML formats handle this case is the TS format from Qt-Linguist, which uses a