If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

file select box uses chinese fonts




15 years ago
12 years ago


(Reporter: fritz.heinrichmeyer, Assigned: jag (Peter Annema))



Firefox Tracking Flags

(Not tracked)





15 years ago
User-Agent:       Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030519
Build Identifier: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030519

when compiled with gcc33 and g++33 (released recently) mozilla file dialog comes
up with chinese fonts, not useable for me. Recompiling with 3.2 under freebsd 5.0 

Reproducible: Always

Steps to Reproduce:
1.compile mozilla (1.3.1 or 1.4b with gcc33 under FreeBSD current)
2. open File -> Open File Dialog
3. read chinese

Actual Results:  
chinese file listings

Expected Results:  
western font file listing

Comment 1

15 years ago
I second this bug.

It is Chinese just by coincidence because it converts each character code XX to
XX00, i.e. "ab" (0x65 0x66) becomes 0x6500 0x6600 which happened to be in
Chinese part of Unicode.

It happens because LANG env variable is not set.

Solution to this is to set

Comment 2

15 years ago
in my environment i have


so this should not be an issue.

The strange thing is that mozilla behaves as i like it when i recompile it with
gcc32 (default in FreeBSD-CURRENT) (this fact was an essential part of my bug
report). Also the download manager was infected by chinese glyphs(?). 

Mozilla seems to default to unicode when compiled with gcc33 in contrast a gcc22
compiled binary? Maybe a gcc33 issue?

Comment 3

15 years ago
same effect with mozilla-firebird:

compiled with gcc32: can read filenames in File->Open box

compiled with gcc33: characters are expanded to 16 bit and then interpreted as
chinese chars.

Comment 4

13 years ago
Worksforme on FreeBSD 5.3 (which comes with gcc 3.4 ).
Fritz, are you still experiencing the same problems?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.