Closed
Bug 274912
Opened 20 years ago
Closed 19 years ago
Bugzilla lines with non-ascii characters fail to render at all
Categories
(Core Graveyard :: GFX: Gtk, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: terra, Assigned: blizzard)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041110 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041110 Firefox/1.0
At http://bugzilla.gnome.org/show_bug.cgi?id=161401, comment 2 is totally blank
for me. If I select part of the line not including the non-ascii character, that
part renders fine.
For "unicode" monospace font I am using "monospace". Ditto for Western.
Reproducible: Always
Steps to Reproduce:
Expected Results:
At the very least I would expect the ascii parts to render.
SuSE 9.1
![]() |
||
Comment 1•20 years ago
|
||
Worksforme with a current trunk build. Reporter, can you reproduce the problem
with a trunk build? Firefox 1.0 is using a very old layout engine....
In any case, not likely to be a view rendering problem; almost certainly an xft
issue.
Assignee: roc → blizzard
Component: Layout: View Rendering → GFX: Gtk
Version: Trunk → 1.7 Branch
Reporter | ||
Comment 2•20 years ago
|
||
Situation is unchanged with trunk build.
However, a bit more experimentation reveals that this is a encoding problem.
* If I have encoding set to Auto->Universal, things work.
* If I have UTF-8, I get blank lines.
I take it that those accented characters are not UTF-8 encoded and, indeed,
what is actually there is not valid UTF-8 at all.
I would still expect one of these:
* ASCII parts render fine, invalid characters show blank or "?" or whatever.
* An error indication.
![]() |
||
Comment 3•20 years ago
|
||
> * ASCII parts render fine, invalid characters show blank or "?" or whatever.
This is what I see in a non-XFT build when I try UTF-8 on the page.
It's also what I see with a Firefox build (GTK2/XFT).
What version of XFT are you using?
Reporter | ||
Comment 4•20 years ago
|
||
My firefox claims to be...
"Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b) Gecko/20050118 Firefox/1.0+"
The firefox-bin binary dynamically links /usr/X11R6/lib/libXft.so.2
# ls -Ll /usr/X11R6/lib/libXft.so.2
-rwxr-xr-x 1 root root 83726 Sep 23 2003 /usr/X11R6/lib/libXft.so.2
# grep version= `which xft-config`
version="2.1.0"
My system is a (patched) SuSE 9.0
![]() |
||
Comment 5•20 years ago
|
||
Odd... I have the same XFT version here...
Comment 6•20 years ago
|
||
Worksforme - displays a ? on the following build - English language.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4
Firefox/1.0.4
Linked against libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x004f7000)..
xft-config is found in the pacakge xorg-x11-devel-6.8.2-37 on Fedora Core 4.
Will retry with latest trunk build.
Comment 7•20 years ago
|
||
Interesting. On Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b2)
Gecko/20050623 Firefox/1.0+, the characters that showed up as ? on the stock
Fedora Firefox build show up as a comma (,). I would argue that this is not the
exepcted behavior. I'm not sure what patches RH included in the Fedora build,
but it is *not* fixed in the above build.
Sorry for the bugspam.
Comment 8•19 years ago
|
||
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/
Comment 9•19 years ago
|
||
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
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•