Closed
Bug 436902
Opened 17 years ago
Closed 17 years ago
Apostrophes display as empty boxes in iWeb-created page
Categories
(Camino Graveyard :: Page Layout, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: adamwilde, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.14) Gecko/20080512 Camino/1.6.1 (like Firefox/2.0.0.14)
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.14) Gecko/20080512 Camino/1.6.1 (like Firefox/2.0.0.14)
On Ron D. Moore's blog page (created in iWeb) apostrophes display incorrectly as empty box characters. (This page does display correctly in Firefox (3.0b5) and Safari.)
Text encoding is set as Unicode and Automatically Detect Page Encoding is checked.
(This doesn't appear to be a previously-identified bug - apologies if it is.)
Reproducible: Always
Steps to Reproduce:
1.Visit web page as above.
2.Observe incorrectly rendered apostrophes.
Actual Results:
Apostrophes are rendered as empty box characters.
Expected Results:
Rendered apostrophes as apostrophes.
Comment 1•17 years ago
|
||
WFM in 1.6.1; what are your font settings?
| Reporter | ||
Comment 2•17 years ago
|
||
Western
Proportional Font (Serif): Verdana (also tried as Times)
Proportional Font (Sans-serif): Helvetica
Monospace: Panic Sans
(Is that the information you need, or am I looking in the wrong place?)
A grab of what I see is here, in case it's useful: http:/homepage.mac.com/adamwilde/camino_apostrophe.png
The site's using Hoefler Text in all of its css, so unless you've checked "Always use my fonts", your font settings won't matter (and it certainly looks like Hoefler Text in your screenshot). Check Font Book and make sure you don't have multiple copies of Hoefler Text and that the font isn't corrupt.
You can also try running with a fresh profile using http://pimpmycamino.com/parts/troubleshoot-camino and see if the page displays correctly.
| Reporter | ||
Comment 4•17 years ago
|
||
There was a duplicate of Hoefler installed. Disabling it fixed the problem. Thanks and apologies!
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•