Bug 145700 - Konqueror using OpenSymbol font when font is not configured or specified in CSS or HTML
Summary: Konqueror using OpenSymbol font when font is not configured or specified in C...
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-20 11:25 UTC by Chase Venters
Modified: 2008-06-24 23:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chase Venters 2007-05-20 11:25:14 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Gentoo Packages
Compiler:          gcc (GCC) 4.1.1 (Gentoo 4.1.1)
 
OS:                Linux

I have this problem with font selection. I've seen it on a number of pages, and finally decided to file a report. It happens on this page:

http://wiki.noreply.org/noreply/TheOnionRouter/FireFoxTorPerf

The <pre> section under "Procedure 1" renders with the OpenSymbol font. If I increase or decrease the font (Ctrl++ or Ctrl+-), a correct font family is used and the text is readable. 

My settings are for a 9 minimum font size, 12 medium size. Fonts:

Standard: Arial
Fixed: Courier New
Serif: Serif
Sans serif: Sans Serif
Cursive: Sans Serif
Fantasy: Sans Serif

OpenSymbol is configured in no place I can see. The page I reference as being buggy specifies no specific font options in the HTML for the <pre>, but the CSS asks for "font-family: courier, monospace;".
Comment 1 Philip Rodrigues 2007-05-21 23:50:16 UTC
probably related to bug 145695
Comment 2 FiNeX 2008-04-21 12:35:01 UTC
Cannot reproduce on konqueror 3.5.9 AND 4 (trunk).
Comment 3 Chase Venters 2008-06-24 23:43:54 UTC
I can't seem to reproduce this in konqueror 3.5.9 any more either. It seems that the bug Philip references is still open, so I'm not sure what "fixed" the issue.

Marking as "RESOLVED" because I can't come up with any more examples of problematic font rendering, leaving the possibility of the bug having gone away and the certainty of no recourse for the developers in the alternate.