On 11/06/2015 06:12 AM, Augustin Trancart wrote:
> Summarizing what Zibi and David said, I apply these rules of thumb:
>
> 1/ If your string is managed by l{1,20}n it should work 95% of cases.
> Don't do anything. If not see 4/
It's not. These strings come from user data (specifically ID3 tags for
music).
> 3/ If you do need ellipsis, use dir="auto".
[snip]
> Normally, you shouldn't really need to use <bdi>. Note that ellipsis do
> work with <bdi> but make sure they are added to the bdi element, and not
> the parent... That probably requires you to add extra css rules for
> that, so that might be better to use dir="auto" anyway.
I'll try with dir="auto". I seem to recall this breaking something
before, which is why I switched to using <bdi> in my patches, but it's
possible I'm misremembering.
> 4/ In other cases, FSI/PDI can help a lot (it serves as clue for the
> BiDi algorithm to figure out which part of your string is LTR and which
> is RTL), see [1]
> Note that l{10,20}n already wraps latin element with FSI/PDI in
> non-latin context. However in some rare cases, it might not be enough
> [2]. In these cases, [RLM] can help.
Embedding FSI/PDI is possible, but would be a pain, since - as mentioned
above - these strings don't come from us. I suppose I could just wait
for the Unicode patch as Andrew mentions, which I'm glad to see we're
finally working on. I've been waiting for that since we originally
started doing RTL.
I'll muck about with this and see if I can make it do what I want.
Thanks to everyone who replied!
- Jim
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos
