Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3953 - firefox utf8 problem

Attached to Project: Arch Linux
Opened by Benoit C (benoitc) - Sunday, 12 February 2006, 14:36 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Jan de Groot (JGC)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Firefox don't display rigght website with unicode or utf8 (see screenshot attached of http://ja.wikipedia.org). The pb don't seem to be related to pango or gtk2 but ...
   Screenshot.png (498.7 KiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 19 February 2006, 00:10 GMT
Reason for closing:  Implemented
Additional comments about closing:  pango support is enabled again now. Users can control pango rendering with MOZ_DISABLE_PANGO=1 environment variable to fall back to XFT.

For the weird characters: make sure you install fonts that support them, standard bitstream vera doesn't have them.
Comment by Jan de Groot (JGC) - Sunday, 12 February 2006, 17:52 GMT
This is because firefox hasn't been built with pango support. Pango is a huge amount slower than XFT when it comes to rendering, so I disabled it on many requests. I found out that it is possible to have both pango and xft enabled, and pango 1.12 should be quite a bit faster than 1.10, so I will enable pango at the moment pango 1.12 becomes stable.
Comment by Benoit C (benoitc) - Tuesday, 14 February 2006, 00:18 GMT
so there is no possibility to have unicode support waiting pango 1.12? that's what you mean ?

Loading...