174540 - Browser fails to display the correct character set: page unreadable

Status: VERIFIED DUPLICATE of bug 52746

(Firefox :: General, defect)

Description

[Allah the grate]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021014 Phoenix/0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021014 Phoenix/0.3

The page at http://www.amarujala.com/today/default.asp (Indian newspaper) is
unreadable (question marks instead of expected text) with Phoenix 0.3.

Reproducible: Always

Steps to Reproduce:
1. Access the page at http://www.amarujala.com/today/default.asp
2. From main menu, select View > Character coding and "play" with all the
different options: the page is never displayed correctly.
Actual Results:  
All text is replaced with question marks. In some case (selecting Gujarati
character sets) it is displayed with other characters such as "çàæßâðÙæ Âý×é¹
ÕæÜ Ææ·Úð Ùð ·ãæ ãñ ç", but never with the right font.

Expected Results:  
Page should be displayed correctly. FYI, with Microsoft IE 6.0 SP1, on the same
platform, the page appears just fine with the right characters, so it's not a
problem of font avalability on the PC.

Comment 1

[Niklas Dougherty]

They've got much money in India, but no rise and no curry. And no Unicode. They
use @font-face with unspecified encoding.

Comment 2

[Allah the grate]

Actually they DO have money and rice and curry and they even got nukes !!  Now,
more seriously, whatever coding this site is using, maybe you're right, but then
how come does it display just fine in MSIE 6 ? 
Moreover, on top of the page, you might see a "Download font" graphic tab -
didn't have to use it with MSIE - but even if you download and install the font
(TTF on Windows 2000), same results.

Comment 3

[Niklas Dougherty]

MSIE 6 supports dynamic fonts. Mozilla probably will in the future (I believe
the bug conerning that matter is assigned, but it is also a matter of getting
vendors like BitStream lightening up their TrueDoc specs).

Comment 4

[Allah the grate]

Once again, it does not have to do with the font it self. See my previous
comment: the bug appears *even* if you download and install the necessary font
(which is available on purpose) from that same website. To make it short, I
strongly believe it's not a matter of font availability, but rather the
automatic detection of the page encoding that doesn't work in Phoenix 0.3 (build
#20021015). 

Comment 5

[Niklas Dougherty]

Look at the code:

<meta http-equiv='Content-Type' content='text/html; charset=x-user-defined'>

This means that the encoding is embedded in the font to come:

<style type=text/css>
@font-face {
font-family: au;
font-style:  normal;
font-weight: normal;
src: url(http://216.15.255.34/DBFNT0.eot);
}

This is an embedded Open Type font. Dynamic fonts are not supported by Mozilla
and derivatives, so it is not downloaded and used. Therefore, there is no way to
know the encoding (which is not Unicode-compliant). If you download this font,
it may or may not work, depending on how it was created. Most dynamic fonts have
copy protection builtin and will only render when downloaded from a certain host
(not from disk, not from cache).

Therefore, it will not work until Mozilla incorporates dynamic fonts in Gecko.
Personally, I think this is an evangelism issue, since India Times can adopt
Unicode instead. It is piece of cake writing Devanagari straight for the web
with UTF-8 or UTF-16.

Comment 6

[Neil Cronin]

this should be resolved as a dupe of 52746.

Comment 7

[Neil Cronin]

resolving as a dupe.  

Pascal, if after bug 52746 is fixed phoenix still does not behave as expected,
reopen this bug.

*** This bug has been marked as a duplicate of 52746 ***

Comment 8

[Allah the grate]

Will do. BTW, any plan or date for this to be fixed?

Comment 9

[Simon Paquet [:sipaq]]

Mass verifiying of old duplicates.