OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [xliff] RE: Call for dissent on BIDi solution Re: [xliff] bidi


Yves
I did the previously agreed groundwork 
1) Introducing the value "auto" as the third and default value.
2) Removing dir from source and target
I also tentatively introduced dir on isolated <ec>s
This will be visible in the next print out

As result the section on Bidirectional text needs more changes

Previous text:

Text directionality in XLIFF content is defined by inheritance. Source and target content can have different directionality.
The initial directionality for both the source and the target content is defined in the <file> element, using the optional attributes srcDir for the source and trgDir for the target. The default value for both attributes is ltr.
The <group> and <unit> elements also have the two optional attributes srcDir and trgDir. Their values must be either ltr or rtl. The default value of the srcDir is inherited from the value of the srcDir attribute of the respective parent element. The default value of the trgDir attribute is inherited from the value of the trgDir attribute of the respective parent element.
The <source> element has an optional attribute dir with a value ltr or rtl. The default value is the same as the value of the of the srcDir attribute on the <unit> element, in which the element is located.
The <target> element has an optional attribute dir with a value ltr or rtl. The default value is the same as the value of the trgDir attribute of the <unit>, in which the element is located.
The <pc> and <sc> elements have an optional attribute dir with a value ltr or rtl. The default value is inherited from the parent <source>, <target>, or <pc> element, in which the respective element is located.
Adding bidirectional information in the text content is done using the Unicode bidirectional control characters [UAX #9].
In addition, the <data> element has an optional attribute dir with a value ltr or rtl that is not inherited. The default value is ltr.



New text:

Text directionality in XLIFF content is defined by inheritance. Source and target content can have different directionality.
The initial directionality for both the source and the target content is defined in the <file> element, using the optional attributes srcDir for the source and trgDir for the target. The default value for both attributes is auto.
The <group> and <unit> elements also have the two optional attributes srcDir and trgDir. The default value of the srcDir is inherited from the value of the srcDir attribute of the respective parent element. The default value of the trgDir attribute is inherited from the value of the trgDir attribute of the respective parent element.
The <pc>, <sc>, and isolated <ec> elements have an optional attribute dir with a value ltr, rtl, or auto. The default value is inherited from the parent <pc> element. In case the inline element is a child of a <source> element, the srcDir attribute value will be inherited from the enclosing <unit> element, whereas the trgDir attribute value will be inherited in case the inline element is a child of a <target> element.

Warning: 
While processing isolated <ec> elements with explicitly set directionality, please beware that unlike directionality set on the <pc> and <sc> , this method decreases the stack level as per [UAX #9].

In addition, the <data> element has an optional attribute dir with a value ltr, rtl, or auto that is not inherited. The default value is auto.
Directionality of source and target text contained in the <source> and <target> elements is fully governed by [UAX #9], whereas explicit XLIFF-defined structural and directionality markup is a higher-level protocol in the sense of [UAX #9]. The XLIFF-defined value auto determines the directionality based on the first strong directional character in its scope and XLIFF-defined inline directionality markup behaves exactly as Explicit Directional Isolate Characters, see [UAX #9], http://www.unicode.org/reports/tr9/#Directional_Formatting_Characters.

Note:
Please note that this specification does not define explicit markup for inline directional Overrides or Embeddings; in case those are needed. Extractors and Modifiers will need to use [UAX #9] defined Directional Formatting Charcters.


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 Fri, Dec 20, 2013 at 1:10 PM, Yves Savourel <ysavourel@enlaso.com> wrote:
Hi David, all,

> We might want to say that our inline spans and pairs
> should be interpreted as the isolates rather than the the
> embeddings if transformed into plaintext.
> So this would be an addition to our Directionality section.

Doing edits in the specification is a pain, so maybe, to save some time and efforts, you could post an email with the proposed text,
and we can dissent or not on it.

Currently the paragraphs about inline content are like this:

[[
...
The <pc> and <sc> elements have an OPTIONAL attribute dir with a value ltr or rtl. The default value is inherited from the parent
<source>, <target>, or <pc> element, in which the respective element is located.

Adding bidirectional information in the text content is done using the Unicode bidirectional control characters [UAX #9].

In addition, the <data> element has an OPTIONAL attribute dir with a value ltr or rtl that is not inherited. The default value is
ltr.
]]

What would be the new text?

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




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]