On Tue, Nov 15, 2011 at 4:18 AM, Eli Zaretskii <eliz_at_gnu.org> wrote:
>> Date: Mon, 14 Nov 2011 23:27:02 -0800
>> From: David Starner <prosfilaes_at_gmail.com>
>> Cc: naenaguru_at_gmail.com, unicode_at_unicode.org
>>
>> On Mon, Nov 14, 2011 at 10:12 PM, Eli Zaretskii <eliz_at_gnu.org> wrote:
>> >> It's not standards compliant. If it doesn't work on IE, and sometimes
>> >> doesn't work on Firefox, then it hardly qualifies as a solution in my
>> >> book, especially as I'm getting "nivahal heøa" as the label on its tag
>> >
>> > FWIW, the latest Firefox 8 has no problems displaying that page,
>> > including the labels on the tabs.
>>
>> I'm running Iceweasel 8, and it displays the tabs as Latin. I would
>> consider it a bug to do otherwise; the font on those tabs should be
>> under my control.
>
> It _is_ under your control. But what do you expect to happen if you
> select a font that doesn't cover the characters on the page, or force
> the browser to use an encoding different from what the page author
> intended? Selecting a font that cannot handle the tricks played by
> that page is no different.
It is different. If the title of a page is proper Singhala, I can
choose a font for the tabs that supports Singhala and Latin, and
display all the tabs correctly. (It'll take more intelligence if I
want to have Cherokee and Cyrillic and Singhala all as labels of tabs,
but the problem is a known one with solutions; different fonts can be
used for different scripts.) If the title of page is in Latin script
displayed as Singhala by a font, I can't display Latin and Singhala
titles in tabs without accepting the font of the page or manually
changing fonts.
-- Kie ekzistas vivo, ekzistas espero.Received on Tue Nov 15 2011 - 20:01:42 CST
This archive was generated by hypermail 2.2.0 : Tue Nov 15 2011 - 20:01:44 CST