XLIFF Inline Markup Subcommittee Teleconference

[Yves Savourel <ysavourel@enlaso.com>]

XLIFF Inline Markup Subcommittee Teleconference

Every second Tuesday of every month at 15:00 UTC
7:00am PT, 8:00am MT, 10:00am ET, 11:00 Montevideo,
3:00pm London, 4:00pm Berlin.

Teleconference meeting place:
https://www1.gotomeeting.com/join/408998929
Meeting ID: 408-998-929
You can use the following US phone number, or the VOIP option provided by GoToMeeting:
Dial 630-869-1010
Access Code: 408-998-929

The summary of our main items is here:
http://wiki.oasis-open.org/xliff/OneContentModel/Requirements

Latest draft is here:
See http://tools.oasis-open.org/version-control/svn/xliff/trunk/xliff-20/xliff-core.pdf



=== Annotations representation
(req 1.5: Must allow to associate spans of content with metadata)

Current proposed representation:
http://lists.oasis-open.org/archives/xliff-inline/201110/msg00013.html

<mrk [id='id'] type='type' [value='some value'] [ref='someId'] [translate='yes|no']>...</mrk>


--- Splitting mrk:

Solution currently: use several <mrk> elements.

Yves had the action item to try implementation.
-> Some progress and a first remark:
Using duplicated well-formed elements instead of the same start+end markers as with <sc/>/<ec/> forces the implementer to do more work. Using start+end markers would allow the implementer to just re-use the same code as for <sc/>/<ec/>/<pc> with a few changes.


=== splitting non-clonable

See Fredrik's notes:
http://lists.oasis-open.org/archives/xliff-inline/201202/msg00001.html



=== Validation/compliance

Christian had the action item to bring back the validation tool question to the TC.



=== Representation of editing hints

Need to have notation for 'permissions'

See latest email:
http://lists.oasis-open.org/archives/xliff-inline/201202/msg00000.html



=== Bi-direction markers

Several tools use Unicode characters in 1.2.
Goes against W3C recommendation but seems common practice.
-> need to know about other tools
-> ask for info to W3C
Sent (but not passed the W3C check yet).

Some reference material:
- http://www.w3.org/International/questions/qa-bidi-controls
- http://www.w3.org/International/wiki/BidiProposal



=== Codes and effect on segmentation
(req 1.16: Inline codes should have a way to store information about the effect on the segmentation)

Related email:
http://lists.oasis-open.org/archives/xliff-inline/201109/msg00005.html



=== Representation of added codes

Need to clarify use of duplicated code.
e.g. why not re-use same code?
(See http://lists.oasis-open.org/archives/xliff-inline/201110/msg00021.html)



=== Plural form example:

Example of possible issue:
Java string: "There {0,choice,0#are no files|1#is one file|1"
And PO, Android, TS plural.

Action item: Yves to escalated the issue to TC.
-> See http://lists.oasis-open.org/archives/xliff/201201/msg00024.html
And thread.



=== Any other business

None.

-end