W3C home > Mailing lists > Public > www-international@w3.org > January to March 2015

[Bug 28266] [webvtt] 6.2.1 processing model handling of bidi [I18N-ISSUE-432]

From: <bugzilla@jessica.w3.org>
Date: Fri, 27 Mar 2015 07:11:01 +0000
To: www-international@w3.org
Message-ID: <bug-28266-4285-jZXBBvBgvZ@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28266

Glenn Adams <glenn@skynav.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |glenn@skynav.com

--- Comment #4 from Glenn Adams <glenn@skynav.com> ---
(In reply to Philip J├Ągenstedt from comment #3)
> I am fully prepared that there's a problem that needs to be solved here, but
> it would be very illuminating with one or a few examples of caption files
> along with the rendering that is desired. I'm guessing it would be something
> like captions in mainly Arabic, but a single cue somewhere with only Latin
> text. What I can't guess is a desired rendering that's hard to achieve
> without a file-wide directionality.
> 
> Note that my assumption here is that the text directionality only affects
> the position of the cue text and not how it actually rendered. If this is
> not true, please correct me :)

As Addison says, the Unicode Bidi Algorithm needs to know the default bidi
level to apply to a "paragraph level". This information is needed to resolve
the dir3ectionaly of neutral or weakly directional characters, particularly at
the beginning and end of the paragraph. Although there is an algorithm that
chooses a default directionality in the absence of an external direction
property, that algorithm often requires an explicit directionality to achieve
the desired results.

So basically, it does determine how text is rendered, and not just alignment.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 27 March 2015 07:11:03 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:38 UTC