Closed
Bug 241767
Opened 21 years ago
Closed 20 years ago
Font not displayed correctly
Categories
(Core :: Internationalization, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: abhijeetkarpe, Assigned: smontagu)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Firefox crashes after adding any new extension and clicking on tools
Reproducible: Didn't try
Steps to Reproduce:
1. Type www.esakal.com in address bar.
2. download subak font from the site to font folder..
3. Refresh the page.
Actual Results:
99% of the text is displayed correctly , except the “$” string which is a error.
Expected Results:
Should have showed all text correctly.
Got a microsoft error window , which said firefox has crashed.
Comment 1•21 years ago
|
||
I think you've mixed text from your other bug 241769 into this one. Did this
bug really cause a crash because of a missing font? Does it really have
anything to do with adding an extension?
Just to add a bit more info to what is happening here:
unicode character U+0024 is displayed as a space in the susak-1 font by other
programs e.g. OpenOffice.
"$" is the representation of this character in standard Latin fonts.
Someone can correct me, but I think this belongs more in Browser->Layout: Fonts
and Text, so I'm moving it there.
Assignee: firefox → nobody
Component: General → Layout: Fonts and Text
Product: Firefox → Browser
QA Contact: core.layout.fonts-and-text
Version: unspecified → Trunk
Probably invalid.
Assignee: nobody → smontagu
Component: Layout: Fonts and Text → Internationalization
QA Contact: core.layout.fonts-and-text → amyy
Not Sure why this has been moved to internationalisation, the font uses the
standard first page of unicode... so IMHO it's really just a font issue, just
because the glyphs happen to be in a different language shouldn't make a
difference, the same thing could occur with an English font that has the same
entry for the character U+0024. That's my 2c anyway.
Comment 6•21 years ago
|
||
As dbaron wrote, this bug is very likely to be invalid. The page relies on a
hacked font that seems to put __incorrect__ glyphs at U+0024 and other code
points. Probably, the intent was to preserve the ASCII portion and to use the
'right half' of ISO-8859-1 (corresponding to U+00A1/0 - U+00FE/F) for an Indic
script used in the page, but apparently, the font doesn't preserve ASCII,
either. (I couldn't figure out which link to follow to download the font. If
the reporter can give me the url, I'll download the font and confirm my
suspicion). Mozilla can't do anything with those kinds of broken/hacked fonts.
You could well be right. I wasn't trying to comment on the validity of the bug,
just where it should be filed (I think it's font issue, not internationalization).
http://www.esakal.com/prog/frm_downloadfont.htm to get instructions for
downloading font. From memory I think it's the first one (Subak1) that is important.
Comment 8•21 years ago
|
||
*** Bug 248821 has been marked as a duplicate of this bug. ***
Comment 9•21 years ago
|
||
dupe of bug 105688 ?
Comment 10•20 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 11•20 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: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•