Closed
Bug 488251
Opened 16 years ago
Closed 16 years ago
font code 128 does not render
Categories
(Tech Evangelism Graveyard :: English US, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: rsalmon, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.0.7) Gecko/2009030503 Fedora/3.0.7-1.fc9 Firefox/3.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; fr; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8
Font "Code 128 doesn't render under Windows.
Font can be downloaded from bugzilla : https://bugzilla.mozilla.org/show_bug.cgi?id=292271
using single quote or double quotes to define the font (font-family: "Code 128";) doesn't make any difference.
See HTML code below.
Reproducible: Always
Steps to Reproduce:
<html>
<head>
<title>Sample</title>
<style type="text/css">
.code128 {
font-family: "Code 128";
}
</style>
</head>
<body>
<div class="code128" style="font-size: 30pt;">ABCD</div>
</body>
</html>
Actual Results:
The text is shown instead of the barcode.
Expected Results:
Draw the barcode
Font "Code 128" does render on the same OS using IE 6, Excel or swriter.
Firefox does render font "Code 128" under Linux (Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.0.7) Gecko/2009030503 Fedora/3.0.7-1.fc9 Firefox/3.0.7).
|
Reporter | |
Comment 1•16 years ago
|
||
Same issue with Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b4pre) Gecko/20090413 Shiretoko/3.5b4pre
Flags: blocking-firefox3.5?
|
||
Updated•16 years ago
|
Flags: blocking-firefox3.5? → blocking-firefox3.5-
|
|
Reporter | |
Comment 2•16 years ago
|
||
Same problem with fonts windows fonts 'Wingdings' and 'Webdings'. They do render in IE, but not in Firefox.
|
||
Comment 3•16 years ago
|
||
It's not clear to me where there is invalid (HTML, CSS, etc.) code which should be fixed by some non-Mozilla company.
My mention of Tech Evangelism in bug 292271 comment #6 assumed that SourceForge was using HTML or CSS with an unquoted font-name containing quotes. The solution, in that case, would be to convince SourceForge to change their code. However, apparently I read that bug too fast, and there never was invalid code at SourceForge.
In this case, it isn't obvious to me where the supposed bug lies, especially if "Wingdings" or "Webdings" fonts (with no spaces in their names) cannot be displayed either.
See also http://www.mozilla.org/projects/tech-evangelism/site/procedures.html which describes procedures which every reporter of a Tech Evangelism bug should follow before and after reporting the bug.
|
|
Reporter | |
Comment 4•16 years ago
|
||
(In reply to comment #3)
>
> In this case, it isn't obvious to me where the supposed bug lies, especially if
> "Wingdings" or "Webdings" fonts (with no spaces in their names) cannot be
> displayed either.
So, should we close/or mark this bug as a duplicate of bug 292271 (or close the other one). I guess there is no point in keeping 2 bugs open having the same issue ?
|
||
Comment 5•16 years ago
|
||
It doesn't appear that there's an issue of invalid HTML, and it *does* appear that this isn't the only font affected, so we should investigate the real problem. I'm going to close this as INVALID since the bug filed here is not a TE bug.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
|
||
Updated•10 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•