Description: Standing XLIFF TC Teleconference (Weekly)
Tuesdays 04:00PM London/Dublin / 08:00 AM PST
NOTE THE CORRECT DIAL-UP NUMBER:
International Dial-In: +44 118 376 9023
Meeting ID: 30543
==========
Agenda: 1. Roll Call
2. Accept / Reject previous meeting minutes: minutes: http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=978&day=1050404400
3. Review Vote result of "state" attributes values list proposal:
http://www.oasis-open.org/apps/org/workgroup/xliff/ballot_archive.php
4.(item carried - over from last meeting) Design loophole - XLIFF permits multiple languages in single XLIFF document, so that you could create one file that contains multilingual resources for all langs. For example, a single XLIFF document container could consist of multiple files with source-target pairs like: english/french, italian/spanish, german/portuguese. This loophole stretches the design intent of XLIFF, and means that the content of such a document would not be exchangeable between localization tools that operate on the bilingual model.
Discuss if it is feasible to limit within the XSD that only bilingual or monolingual language may be specified per XLIFF document, or if we should indicate through prose in the spec that only a single bilingual source/language pair should be contained within the same file, or if we should indicate anything about this loophole at all in the spec (ie, leaving it open to implementor to possibly exploit this loophole).
5. Proposal from Mirek and Milan of Moravia to add 3 new items to "restype" attributes list:
usercontrol Indicates a user-defined control like CONTROL control in Windows
binary Indicates a raw data resource for an applications like RCDATA in Windows.
versioninfo Indicates a version information about a resource like VERSIONINFO in Windows
Discussion and decision or vote on disposition of this proposal.
Original email: http://www.oasis-open.org/archives/xliff/200304/msg00040.html
6. Discussion of Shigemichi's suggestion that size-unit "glyph" attribute value is not an accurate name for the entity it describes.
Shigemichi suggests that Unicode's term ""grapheme cluster" is more accurate (definition -> http://www.unicode.org/reports/tr29/tr29-4.html#Grapheme_Cluster_Boundaries)
Discussion and decision or vote on disposition of this proposal.
Original email: http://www.oasis-open.org/archives/xliff/200304/msg00039.html
7.Plans and timetable for XLIFF 1.1 committee spec approval.
8.Any other business.
Next meeting Tuesday, 6 May 2003, 4pm London/Dublin, 8am PST
==========
Minutes: http://www.oasis-open.org/archives/xliff/200304/msg00045.html
==========
Attendance:
Achieved quorum: true
Counts toward voter eligibility: true
Individual Attendance- Members: 10 of 41 (24%)
- Voting Members: 8 of 17 (47%) (used for quorum calculation)
Company Attendance- Companies: 7 of 19 (36%)
- Voting Companies: 6 of 10 (60%)
Quorum rule: 51% of voting members