[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Groups - XLIFF Meeting (rescheduled from 15 June) modified
XLIFF Meeting (rescheduled from 15 June) has been modified by Tony Jewtushenko (email@example.com). Date: Tuesday, 06 July 2004 Time: 04:00pm - 05:00pm Greenwich Mean Time Event Description: 04:00PM London/Dublin / 08:00 AM PST 1. Call one of the MeetingPlace phone numbers: From the AMER region dial: * 1-888-967-2253 * +1-650-607-2253 From the APAC region dial: * +61 2 8817 6100 From the EMEA region dial: * +44 118 924 9000 2. Enter the Meeting ID (126680) followed by the # key 3. Press 1 to confirm the Meeting ID 4. If the organizer has not started the meeting you will be: a. Asked to speak your name followed by the # key b. Placed in the waiting room on music hold until the organizer starts the meeting. If the organizer has started the meeting you will be: a. Asked to enter the Meeting Password (030543) b. Asked to speak your name followed by the # key Agenda: Rescheduled from 15 June 2004 Agenda: 1/roll call 2/approve minutes of last meeting: http://lists.oasis-open.org/archives/xliff/200405/msg00014.html 3/ Work in Progress: a. Representation Guides: i. HTML / RTF: Update: http://www.oasisopen.org/archives/xliff/200404/msg00019.html Yves has identified 3 types of HTML element: - Inline - Structural - Subflow content Yves has submitted an HTML file restype-ctype-inline.htm which attempts to classify all HTML elements and attribute res types to them. Committee members should have reviewed the list by now, and agree how any unclassified elements should be treated. Yves also mentioned that we should see how HMTL extraction tool developers have approached the subject in each individual case. The issue of setting up a separate subcommittee was raised, but it was decided to tackle the issue via exchange of emails for the time being. Tony asked for final comments to be submitted by 8 June. ii. WinRes (John, Yves) iii. Resx (Enda, Gerard) http://lists.oasis-open.org/archives/xliff/200403/msg00007.html iv. Java Resource Bundles (Tony & John) v. XForms ( Andrzej ) 4/ Unresolved or New Bugs / Proposals a. Andrzej: Adding inline term info to XLIFF http://lists.oasis-open.org/archives/xliff/200404/msg00001.html Update: http://www.oasis-open.org/archives/xliff/200404/msg00007.html Update: http://www.oasis-open.org/archives/xliff/200404/msg00011.html Latest update: http://lists.oasis-open.org/archives/xliff/200406/msg00001.html Comment recieved: http://lists.oasis-open.org/archives/xliff/200406/msg00014.html Yves has supplied a solution to this topic which does not involve any changes to the XLIFF spec (http://www.oasis-open.org/archives/xliff/200404/msg00002.html). Discussion centered on the best way to capture the solution. Options were to create an "errata" document or a "best practices. It was decided that a "best practices" document would be a better solution. Andrzej created the document and distributed it for the TC's comment. b. Andrzej: Translations Grouped Across trans Units. Initial: http://lists.oasis-open.org/archives/xliff/200404/msg00000.html Latest update: http://www.oasis-open.org/archives/xliff/200404/msg00010.html Andrzej stated that an additional "not-equivalent" attribute would also be required to cover the two types of eventuality where a translator cannot provide an equivalent translation for a given trans-unit. It was agreed that this formed part of the work of the segmentation subcommittee and would form part of its recommendations. c.Mat: Translation of Voice XML Issues Initial: http://lists.oasis-open.org/archives/xliff/200403/msg00016.html Latest Update: http://www.oasis-open.org/archives/xliff/200403/msg00017.html Mat raised a very interesting problem caused during the translation of Voice XML documents where variable quantitative values have to be rendered in a given target language. This poses real technical difficulties in the instance of languages such as Polish which is strongly inflected and has pronounced gender affected adjectives. The initial source language text requires multiple target language variants. There is no easy way to tackle this at present in XLIFF. Mat's submission references an earlier document that he submitted last year on this subject. Mat was to send out additional information. The TC agreed to comment on his document and look for best practices. d.Mat: Accepting Suggested Translations In XLIFF Initial: http://lists.oasis-open.org/archives/xliff/200407/msg00000.html Mat raised the issue of how to identify which provided Alt-Trans, if any, has been used by a translator. 5/ Status Report from Segmentation SC (Magnus) - the Segmentation SC is on hiatus for the summer 6/ Report from Localization World 7/ All other business Minutes: View event details: http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=5433 PLEASE NOTE: If the above link does not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.