Closed Bug 271622 Opened 20 years ago Closed 19 years ago

Some Unicode characters are not displayed by Mozilla

Categories

(Core Graveyard :: GFX: Gtk, defect)

1.7 Branch
x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: jm, Assigned: blizzard)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041119
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041119

Mozilla browser (1.7.3 and several previous versions at least) does not display
some Unicode characters and leaves either a blank space instead or blanks more
spaces up to the rest of the paragraph (until a next Unicode character only?).

For example, the symbols: lambda λ, theta θ, sigma σ, etc.

Reproducible: Always
Steps to Reproduce:
1. Create a simple web page with, for example, the symbols: lambda λ, theta
θ, sigma σ, etc.
2. View it in the Mozilla browser.


Actual Results:  
The Unicode characters are not displayed.

Expected Results:  
Display the symbols.
Worksforme in a current trunk build.  Which exact build do you use (what does
about:buildconfig say)?  This sounds like a bug in a font or font subsystem.
Here it is:

about:buildconfig

Build platform
target
i686-pc-linux-gnu

Build tools
Compiler 	Version 	Compiler flags
gcc 	gcc version 3.4.2 	-Wall -W -Wno-unused -Wpointer-arith -Wcast-align
-Wno-long-long -O2 -pipe -march=pentium4 -pthread -pipe
c++ 	gcc version 3.4.2 	-frtti -fno-exceptions -Wall -Wconversion
-Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy
-Wno-non-virtual-dtor -Wno-long-long -O2 -pipe -march=pentium4 -pthread -pipe
-I/usr/X11R6/include

Configure arguments
--prefix=/usr --enable-shared --disable-static --with-system-jpeg
--with-system-zlib --with-system-png --with-system-mng --enable-crypto
--enable-xinerama --disable-tests --disable-debug '--enable-optimize=-O2 -pipe
-march=pentium4' --enable-reorder --enable-strip --enable-elf-dynstr-gc
--enable-cpp-rtti --enable-xterm-updates --enable-toolkit-gtk2
--enable-default-toolkit=gtk2 --enable-old-abi-compat-wrappers --enable-xft
--disable-freetype2 --disable-gnomevfs --disable-mailnews
--enable-extensions=default,-irc 
OK.  So it's either an XFT bug or a bug in the font XFT is using....  What XFT
version do you have installed?
Assignee: general → blizzard
Component: General → GFX: Gtk
Product: Mozilla Application Suite → Core
QA Contact: general → ian
Version: unspecified → Trunk
The installed xft is part of the XFree86 version 4.4.0 and all fonts accompany
the XFree86 version 4.4.0 (got installed 100dpi fonts, scalable fonts (Type 1
and ps fonts I guess), and cyrilic fonts).
Component: GFX: Gtk → General
Product: Core → Mozilla Application Suite
Version: Trunk → 1.7 Branch
Component: General → GFX: Gtk
Product: Mozilla Application Suite → Core
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.