[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, working on it,But have a question for the Inline SC I guessWhy is dir not allowed on <ph>? I know it does not enclose content, but can be useful nevertheless for Extractor/Merger?Dr. David Filip=======================LRC | CNGL | LT-Web | CSISUniversity of Limerick, Ireland
telephone: +353-6120-2781cellphone: +353-86-0222-158facsimile: +353-6120-2734mailto: david.filip@ul.ieOn Fri, Dec 20, 2013 at 1:10 PM, Yves Savourel <ysavourel@enlaso.com> wrote:
Hi David, all,
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,
> 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.
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]