Jumping in here..
Please note that Unicode 6.3 adds directional isolate characters, which could be useful for joining segments.
See: http://www.unicode.org/reports/tr9/#Directional_Formatting_Characters
Directional isolate characters were introduced in Unicode 6.3 after it became apparent that directional embeddings usually have too strong an effect on their surroundings and are thus unnecessarily difficult to use. The new characters were introduced instead of changing the behavior of the existing ones because doing so might have had an undesirable effect on those existing documents that do rely on the old behavior. Nevertheless, the use of the directional isolates instead of embeddings is encouraged in new documents – once target platforms are known to support them.
-s
Yves Savourel ---12/12/2013 05:50:43---For reference, the bidi text I’m talking about is this one: [[
From: Yves Savourel <>
To: <>
Date: 12/12/2013 05:50
Subject: RE: [xliff] Segmentation Modifications
Sent by: <>
For reference, the bidi text I’m talking about is this one:
[[
If the dir attributes of the <source> or <target> elements differ: The content of the <source> or <target> elements set to a
different directionality than the directionality for the <source> or <target> elements of the joined segment MUST be enclosed
between Unicode bi-directional control characters reflecting their original directionality (U+202A and U+202C for left-to-right
spans, and U+202B and U+202C for right-to-left spans).
]]
From the attached file in this post:
https://lists.oasis-open.org/archives/xliff/201311/msg00176.html
The question is basically: are those Unicode control characters the one to use for this mapping?
I based the text on this article:
http://www.w3.org/International/questions/qa-bidi-controls
Thanks,
-yves
From: Yves Savourel [mailto:]
Sent: Thursday, December 12, 2013 6:04 AM
To: ''
Subject: RE: [xliff] Segmentation Modifications
Hi David,
I can do the change, that will free you time for other ones.
Did you double check the bidi mapping?
I’m not expert on bidi, so it’d be good to have more than my input on that part.
Cheers,
-yves
From: Dr. David Filip [mailto:]
Sent: Thursday, December 12, 2013 5:48 AM
To: Yves Savourel
Cc:
Subject: Re: [xliff] Segmentation Modifications
Yves, all I did not hear any dissent on that
As far as i checked this, your proposal is equivalent to what was there for csprd02 with two small exceptions that add to clarity:
1) You use an explicit bidi provision, so that people do not need to research the Unicode BiDi algorithm for merging segments with
different dir
2) You also proposed to have an option to downgrade state on split segments, which makes sense to me
Otherwise it is is just reorganizing the PRs by the perfomred type of modification, which seems fine and I do not have a preference
regarding the presentation of the provisions.
@Yves, Do you want to implement this proposal in the spec or should I?
Please let me know
Thanks
dF
Dr. David Filip
=======================
LRC | CNGL | LT-Web | CSIS
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734
http://www.cngl.ie/profile/?i=452
mailto:
On Sat, Nov 30, 2013 at 1:56 PM, Yves Savourel <> wrote:
Hi all,
As mentioned here: https://lists.oasis-open.org/archives/xliff/201311/msg00138.html, I've been trying to implement segmentation
modification for XLIFF 2.0 for a while now and I have a few comments.
For reference, the cs02 section for this is here:
http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd02/xliff-core-v2.0-csprd02.html#d0e9317
--- The section (starting with its new title) keeps talking about "segmentation modification" and "resegmentation". Could we just
talk about segmentation modification everywhere? The two things are the same thing.
--- That section has many constraints and processing requirements.
It was quite difficult to follow when I tried to implement it.
For example: (take a deep breath) "Modifiers MUST copy all attributes including values, except for the id and order attributes, from
their original instances on or within the original <segment> element onto both instances on and within the resulting two <segment>
or <ignorable> elements, except for attributes that do not have valid instances on the eventually resulting <ignorable> element."
To make a long story short and get to the point, I think that section should be re-worded to be simpler, organized by action (split
or join), and completed with a few things (some subState PRs, explicit directionality conversion, etc.)
The proposed modified text is in the attached document.
I believe it covers what is needed, but it's a complex set of PRs and it should be carefully checked by all. For example I'd like a
confirmation on the Unicode control characters used for the directionality conversion.
Thanks,
-yves
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
