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: [OASIS Issue Tracker] (XLIFF-72) XLIFF 2.1 spec: the dir values are not sufficient for proper BiDi support

    [ https://issues.oasis-open.org/browse/XLIFF-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68555#comment-68555 ] 

Steven Loomis commented on XLIFF-72:

Some thougnts and discussion:
- A <bdi> or <bdo> from, say, HTML could be extracted into XLIFF with sc / ec elements. This would be pertinent to rendering and also [re]segmentation.  It could be noted that the isolate status of certain elements could be considered in downstream processing.
- Looking at https://www.unicode.org/reports/tr9/#Markup_And_Formatting  for example, the dir values are representable. 
- A future extension module could add the equivalent of the `unicode-bidi` attribute (perhaps even with matching name/values) to represent these values

> XLIFF 2.1 spec: the dir values are not sufficient for proper BiDi support
> -------------------------------------------------------------------------
>                 Key: XLIFF-72
>                 URL: https://issues.oasis-open.org/browse/XLIFF-72
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: New Feature
>          Components: other
>    Affects Versions: 2.1_cos01
>         Environment: http://markmail.org/thread/mjlilczn64jvh2yw
>            Reporter: David Filip
>            Assignee: David Filip
>              Labels: ready-for-vote
>             Fix For: 2.1_os
> I am looking at this:
> http://docs.oasis-open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.html#dir
> The possible values are lrt, rtl, and auto
> (with auto "determined heuristically, based on the first strong directional
> character in scope, see [UAX #9]").
> That is the same as the HTML dir attribute
>     https://www.w3.org/TR/2014/REC-html5-20141028/dom.html#the-dir-attribute
> But that is not enough, because the direction based on the first char
> results in bad rendering at times.
> So the HTML standard added <bdi> and <bdo>
> And also CSS needed to add even more control, with unicode-bidi:
>    https://www.w3.org/TR/CSS2/visuren.html#direction
> The values in the CSS2 standard seem to be normal, embed, bidi-override,
> inherit
> But more are coming: normal, embed, isolate, bidi-override,
> isolate-override, plaintext
> (https://www.w3.org/TR/css-writing-modes-3/#unicode-bidi)
> Mozilla and Chrome (and probably others will follow) already support these
> values:
>     https://developer.mozilla.org/en-US/docs/Web/CSS/unicode-bidi
> Chrome also supports "initial" (I don't check about Firefox)
> So the proposed values for dir seem insufficient.
> Kind of a pity to release something that is already outdated, without
> learning from what others did...

This message was sent by Atlassian JIRA

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