Sorry I missed this meeting since I am
at Unicode conference this week. I don't understand the part about "bidi
info" re paragraph direction in XLIFF context? Why is the directional
attributes a concern of XLIFF? I can understand why one needs <bdi>
in HTML/CSS env for rendering purposes but I don't get why this is needed
in XLIFF?
Best regards,
Helena Shih Chapman
Globalization Technologies and Architecture
+1-720-396-6323 or T/L 938-6323
Waltham, Massachusetts
From:
Yves Savourel <>
To:
<>
Date:
10/18/2011 12:36 PM
Subject:
[xliff] Event
"XLIFF TC Call" - Summary
Sent by:
<>
XLIFF TC Teleconference - Summary
=== 1/ Roll call
Present: Rodolfo, Yves, Lucía, Fredrik, Joachim, David-F, Tom, Christian
Regrets: Bryan, Helena, Andrew, Peter, Arle
=== 2/ Approve Tuesday, 04 October 2011 meeting minutes:
http://lists.oasis-open.org/archives/xliff/201110/msg00009.html
=== 3/ Sub Committee Reports
--- 1. Inline text (Yves)
Summary is here:
http://lists.oasis-open.org/archives/xliff-inline/201110/msg00013.html
- Good discussion on <mrk> element.
Need test implementation now.
- Some discussion about bidi: most present use Unicode chars, not markup.
Possible need for bidi info at text unit level: e.g. paragraph direction
- Some discussion about removing or not <pc>.
--- 2. XLIFF Promotion and Liaison SC Charter
David-F: we had a report on Linport and IN!
Report from Lucía on State of art research (xliff support in tools).
Lucia: Link available for the questionnaire. https://www.surveymonkey.com/s/GLBYGTX
(draft only: not to be completed)
ULI: proposal for a segmentation character.
Got negative feedback on Unicode mailing and W3C i18n XML.
Seem the idea of having a segmentation marker is dropped.
Instead look at existing character with additional character.
Important for segmentation in XLIFF.
David will post the link to Arle proposal.
Christian: Does notion of sentence exists for all languages?
Rodolfo: There are characters for paragraph, section, etc. but not sentence
(e.g. Thai)
Joachim: Thai has notion of it, but no punctuation for is.
David-F: not sure there are language without notion of sentence.
=== 4/ Charter Draft (David F.)
Moved to P & L SC by vote of TC
David-F: did it passed? (only half of members voted)
Rodolfo: yes, got the OASIS email.
Discussion is for the SC.
=== 5/ XLIFF 2.0 (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking)
--- 1. XLIFF 2.0 Technical work
(if applicable, let's move these new items into wiki - either 5.1 or 5.2)
a. Code and content comparison (http://lists.oasis-open.org/archives/xliff/201110/msg00036.html)
Good feedback so far.
Fredrik: different level of comp probably needed.
(namespace e.g.)
b. Representing starting/ending/stand-alone parts (http://lists.oasis-open.org/archives/xliff/201110/msg00044.html)
Rodolfo: original data in attribute break semantic of an XML attribute.
But otherwise it should work
Fredrik: not the only problem with <pc>-<ec><sc>
Rodolfo: need both
Fredrik: we could do all with <sc>/<ec> + <ph>
Can't go across segment with <pc>
<pc> is for <g> in old 1.2
<pc> complicates nested mark-up.
Christian: main concern too
Rodolfo: yes, sub-segmenting is quite complicated
c. Segmentation feature (http://lists.oasis-open.org/archives/xliff/201110/msg00055.html)
Maybe at the file-level.
But then don't work for half-segmented files
Processing expectation then when there are more than one segment.
Yves: Concepts looked fine
Fredrik: may want to be able to remove ignorables (e.g. for asian)
May have to be re-ordered.
-> re-visit the order attribute for <ignorable>
Maybe ignorable with empty source? To allow new target one
-> need to test
--- 2. XLIFF 2.0 Technical issues
Items identified documented under feature tracker page that might
need to be moved to issue tracker or charter?
(example: core vs. module)
--- 3. Conformance criteria
Any volunteer to start drafting the conf section?
David-F: should be based on Proc-req, based on use cases, based on business
processes
It's complex.
This bring back the charter.
Business processes should show where xliff applies (extraction, etc.)
To have proc-req
Rodolfo: maybe work on a specific section of charter.
David-F: yes.
Rodolfo: conf issue with validation too.
David-F: bus proc allow to define state before and after
=== 6/ Current XLIFF business
Note: David F. will parse this list and propose which items should move
to P & L SC
David-F: can't move things without ballot.
Some are moved already.
Can delete those item from the TC agenda.
--- 1. Editing/Translating XLIFF - State-of-affairs of Tool Support (Christian)
(http://lists.oasis-open.org/archives/xliff/201108/msg00010.html)
Moved to SC.
Lucia working on this.
--- 2. XLIFF Symposium 1 Debrief: "Voice of our customer" (Christian)
(add XLIFF Symposium 2?)
a. XLIFF Symposium 2 presentations (http://lists.oasis-open.org/archives/xliff/201110/msg00020.html)
DF: was moved to SC.
b. Notes from the symposium (http://lists.oasis-open.org/archives/xliff/201110/msg00027.html)
- note: Bryan will draft a reply regarding TC member participation vs.
the fact that we care and listen to these valuable inputs
Bryan not present
--- 3. XLIFF Spec in XLIFF (Lucia)
Lucia: News for this.
Will talk with Rodolfo on preparing the translation.
DF: was moved to SC too.
--- 4. Using remaining Multilingual Web Events (e.g. in Limerick) as
an opportunity to talk about the current state and the possible
future of XLIFF (Christian)
David-F: moved to SC too.
--- 5. XLIFF:Doc representation guide (Yves)
http://lists.oasis-open.org/archives/xliff/201109/msg00046.html
David-F: Interoperability Now! Is in the SC too.
=================================================
below this line - move items to XLIFF issue tracker (5.2)?
5. XLIFF and TM, Glossary, Segmentation Rules (Christian)
(http://lists.oasis-open.org/archives/xliff/201105/msg00043.html)
- - Need a full discussion on this topic (Peter)
(http://lists.oasis-open.org/archives/xliff/201105/msg00047.html)
6. Gathering common extension points from
existing XLIFF Tools as a guide for 2.0 features (Bryan,
Thomas)
(http://lists.oasis-open.org/archives/xliff/201101/msg00007.html)
- Lucia has taken over Micah's matrix
- David F is investigating funding for XLIFF tools page
7. Using other standards vs. adding XLIFF modules (Arle, David W.,
Yves, Helena, . . .)
(http://lists.oasis-open.org/archives/xliff/201107/msg00023.html)
(http://lists.oasis-open.org/archives/xliff/201108/msg00001.html)
Lucia's matrix is part of the "State of the art" work
=== 7/ New Business
David-F: Oracle is coming back.
Palex, Logus, Kilgray, TAUS, Welocalize also in their way.
Rodolfo: Pangeanic too.
Lucia: That is the cngl newsletter, in pages 8 and 9 they talked about
cngl researchers in the xliff symposium
-end
---------------------------------------------------------------------
To unsubscribe, e-mail:
For additional commands, e-mail:
