OASIS XML Localisation Interchange File Format (XLIFF) TC

Hi all, One more issue in the specification (editorial): In the section about Segmentation Modification we have the following PR: "If the directionality attributes, srcDir, trgDir, or dir differ the Modifier MUST insert Unicode bidirectional control characters [UAX #9] to secure proper directionality in the <segment> and its children." The srcDir and trgDir are not used in <segment>, <source>, <target>, or <ignorable>, therefore they are not relevant here. Only dir (which can be used in <source> and <target>) is relevant. I suggest the following new text (with additional changes to be consistent with the other PRs): "If the directionality attributes dir differ Modifiers MUST insert Unicode bidirectional control characters [UAX #9] to ensure proper directionality in the <source> or <target> elements." Cheers, -yves

Thanks, Yves, this sounds straightforward, unless someone is unhappy with the proposed, I can make the change in the spec. I guess that the reason for mentioning srcDir and trgDir is that dir values are inherited from them. Maybe worth a note? if it is removed from the normative language.. @Bryan, as our excellent tracker gardener would you please add this to the tracker, it can either receieve its own comment number or be subsumed under 133 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: david.filip@ul.ie On Wed, Oct 30, 2013 at 7:07 PM, Yves Savourel < ysavourel@enlaso.com > wrote: Hi all, One more issue in the specification (editorial): In the section about Segmentation Modification we have the following PR: "If the directionality attributes, srcDir, trgDir, or dir differ the Modifier MUST insert Unicode bidirectional control characters [UAX #9] to secure proper directionality in the <segment> and its children." The srcDir and trgDir are not used in <segment>, <source>, <target>, or <ignorable>, therefore they are not relevant here. Only dir (which can be used in <source> and <target>) is relevant. I suggest the following new text (with additional changes to be consistent with the other PRs): "If the directionality attributes dir differ Modifiers MUST insert Unicode bidirectional control characters [UAX #9] to ensure proper directionality in the <source> or <target> elements." Cheers, -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

Hi David, all, > this sounds straightforward, unless someone is unhappy > with the proposed, I can make the change in the spec. I'm happy with the proposed change. But you may want to hold off in doing actual editing for the segmentation Modification section. I will submit many more comments on that section when I have an implementation that seems to work. > I guess that the reason for mentioning srcDir and trgDir > is that dir values are inherited from them. Maybe worth a note? > if it is removed from the normative language.. We should not mention them. srcDir and trgDir (which live in <file>, <group> or <unit>) do not affect the segmentation changes. They apply to <source> and <target> elements without explicit dir attributes, but there is nothing you have to do to or with them when splitting or joining segments/ignorables parts. Cheers, -yves

On Tue, Nov 5, 2013 at 12:28 PM, Yves Savourel < ysavourel@enlaso.com > wrote: We should not mention them. srcDir and trgDir (which live in <file>, <group> or <unit>) do not affect the segmentation changes. They apply to <source> and <target> elements without explicit dir attributes, but there is nothing you have to do to or with them when splitting or joining segments/ignorables parts. I agree that you do not do anything to them when re-segmenting, the note would be just a caveat to look for the defaults in these structural attributes, when it appears that dir is not set.. I think it is wrorth a note because the value is inherited from a different attribute, not the same as in case of translate or canResegment.. I propose this wording: Please note that dir is inherited from trgDir or srcDir if not set explicitly, see dir [link] for its default values. 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: david.filip@ul.ie