Closed
Bug 411143
Opened 18 years ago
Closed 18 years ago
window title encoding : question marks ("?????") displayed instead of unicode characters
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 373398
People
(Reporter: frosty.z, Unassigned)
References
(
URL
)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1)
Build Identifier: Mozilla/5.0 (Windows; U; Win98; fr; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Hi,
It seems that there is an encoding problem with the display of unicode characters in the title bar (Windows XP). Question marks ("????") are displayed instead of the characters.
It seems to be Ok with iso-8859-1 characters, but characters which unicode index is over 255 appear as "?"
Note: this bug may be related to bug #287176
Thanks for your attention,
MP.
Reproducible: Always
Steps to Reproduce:
1. Open one of the proposed sites (http://www.france24.com/france24Public/ar/nouvelles/monde.html , http://www.sina.com.cn/ ...)
2. Look at the content (displayed Ok), then look at the tab title (if any) (appears Ok), then look at the page title displayed in the top left "title zone" of the Firefox window : question marks ("?????") are shown instead of the unicode text (same problem, as well, when looking at the task bar).
This is a windows "bug". The default font used in the title bar does not contain the full range of unicode characters (I think it's Trebuchet MS). If you switch your display to windows classic mode and use a font in the title bar that has full unicode support (like Arial), the characters display fine.
Comment 2•18 years ago
|
||
Note that the same thing happens in Internet Explorer - it really is a Windows bug.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Hi,
Thank you very much for your quick answers.
After having tested on a coworker PC, it seems actually that the problem comes from my system.
Sorry to have opened an additional bug, when searching I did not find bug #373398.
Best Regards,
MP
You need to log in
before you can comment on or make changes to this bug.
Description
•