X
Tryk her for at gå til webstedets mobilversion.

Supportforum

Many fonts don't render when Firefox opens local html file

Skrevet

I'm using a 3rd-party program called Fontlist. It reads all fonts in the Windows fonts folder, and then uses a user-chosen line of text to generate an html file on the hard drive that shows the line of text displayed in each font. Since it's a 3rd-party program, I don't have control over it's html programming.

When the generated html file is browsed with Internet Explorer, all fonts display correctly. When browsing it with Firefox, perhaps half or more of the fonts have an ordinary-looking backup font substituted. I've not been able to discern any pattern as to what kind of font displays correctly or does not.

In researching the problem online, I saw a hint that setting security.fileuri.strict_origin_policy to false might fix the issue. I tried it, and it did not have any effect. Also, in the Fonts and Colors Advanced option, I've checked the box to let web pages choose their own fonts.

Might there be any other settings that would enable Firefox to render virtually any industry-standard font installed on the system? This can affect any html files from 3rd-party sources, not just Fontlist.

I'm using a 3rd-party program called Fontlist. It reads all fonts in the Windows fonts folder, and then uses a user-chosen line of text to generate an html file on the hard drive that shows the line of text displayed in each font. Since it's a 3rd-party program, I don't have control over it's html programming. When the generated html file is browsed with Internet Explorer, all fonts display correctly. When browsing it with Firefox, perhaps half or more of the fonts have an ordinary-looking backup font substituted. I've not been able to discern any pattern as to what kind of font displays correctly or does not. In researching the problem online, I saw a hint that setting security.fileuri.strict_origin_policy to false might fix the issue. I tried it, and it did not have any effect. Also, in the Fonts and Colors Advanced option, I've checked the box to let web pages choose their own fonts. Might there be any other settings that would enable Firefox to render virtually any industry-standard font installed on the system? This can affect any html files from 3rd-party sources, not just Fontlist.

Valgt løsning

The css generated by Fontlist does not put quotes around font family names, including those with a numeric parameter. This explains part of the failures, but not all of them.

It's obvious that the html and css accepted by Internet Explorer is a lot more forgiving than FF.

The Fontlist developer would have to address this issue.

Læs dette svar i sammenhæng 0

Yderligere systemdetaljer

Installerede plugins

  • Shockwave Flash 16.0 r0
  • Next Generation Java Plug-in 10.60.2 for Mozilla browsers
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • Adobe PDF Plug-In For Firefox and Netscape 11.0.07
  • 5.1.30214.0
  • Amazon MP3 Downloader Plugin 1.0.18
  • The plug-in allows you to open and edit files using Microsoft Office applications
  • Office Authorization plug-in for NPAPI browsers
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
  • DRM Netscape Network Object
  • Npdsplay dll
  • DRM Store Netscape Plugin

Program

  • Firefox 29.0.1
  • User Agent: Mozilla/5.0 (Windows NT 5.1; rv:29.0) Gecko/20100101 Firefox/29.0
  • Support-URL: https://support.mozilla.org/1/firefox/29.0.1/WINNT/en-US/

Udvidelser

  • Add Bookmark Here ² 29.0.20140506 (abhere2@moztw.org)
  • Auto-Sort Bookmarks 2.3 (sortbookmarks@bouanto)
  • Cookie Cleanup Utility 1.0 (CookieCleanup@LarrysComputer)
  • DOM Inspector 2.0.14 (inspector@mozilla.org)
  • InspectorWidget 4.04.20121231 ({c671b520-abe9-11d8-8ebc-000c6e787bf7})
  • Restart 1.0.11 (Restart@schuzak.jp)
  • SQLite Manager 0.8.1 (SQLiteManager@mrinalkant.blogspot.com)
  • Troubleshooter 1.1a (troubleshooter@mozilla.org)
  • userChromeJS 1.5 (userChromeJS@mozdev.org)
  • Microsoft .NET Framework Assistant 1.0 ({20a82645-c095-46ed-80e3-08825760534b}) (Inactive)

Javascript

  • incrementalGCEnabled: True

Grafik

  • adapterDescription: Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family
  • adapterDescription2:
  • adapterDeviceID: 0x2592
  • adapterDeviceID2:
  • adapterDrivers: ialmrnt5
  • adapterDrivers2:
  • adapterRAM: Unknown
  • adapterRAM2:
  • adapterVendorID: 0x8086
  • adapterVendorID2:
  • direct2DEnabled: False
  • direct2DEnabledMessage: [u'tryNewerDriver', u'6.1400.1000.5218']
  • directWriteEnabled: False
  • directWriteVersion: 0.0.0.0
  • driverDate: 11-2-2004
  • driverDate2:
  • driverVersion: 6.14.10.3943
  • driverVersion2:
  • info: {u'AzureCanvasBackend': u'skia', u'AzureFallbackCanvasBackend': u'cairo', u'AzureContentBackend': u'cairo', u'AzureSkiaAccelerated': 0}
  • isGPU2Active: False
  • numAcceleratedWindows: 0
  • numAcceleratedWindowsMessage: [u'tryNewerDriver', u'6.1400.1000.5218']
  • numTotalWindows: 1
  • webglRendererMessage: [u'tryNewerDriver', u'6.1400.1000.5218']
  • windowLayerManagerRemote: False
  • windowLayerManagerType: Basic

Ændrede indstillinger

  • accessibility.typeaheadfind.flashBar: 0
  • browser.cache.check_doc_frequency: 0
  • browser.cache.disk.capacity: 358400
  • browser.cache.disk.smart_size.first_run: False
  • browser.cache.disk.smart_size.use_old_max: False
  • browser.cache.disk.smart_size_cached_value: 266240
  • browser.newtab.url: about:blank
  • browser.places.smartBookmarksVersion: -1
  • browser.search.update: False
  • browser.search.useDBForOrder: True
  • browser.sessionstore.restore_on_demand: False
  • browser.sessionstore.upgradeBackup.latestBuildID: 20140506152807
  • browser.startup.homepage_override.buildID: 20140506152807
  • browser.startup.homepage_override.mstone: 29.0.1
  • browser.tabs.loadInBackground: False
  • browser.tabs.warnOnOpen: False
  • dom.mozApps.used: True
  • extensions.lastAppVersion: 29.0.1
  • gfx.blacklist.direct2d: 3
  • gfx.blacklist.layers.direct3d10: 3
  • gfx.blacklist.layers.direct3d10-1: 3
  • gfx.blacklist.layers.direct3d9: 3
  • gfx.blacklist.layers.opengl: 3
  • gfx.blacklist.stagefright: 3
  • gfx.blacklist.suggested-driver-version: 6.1400.1000.5218
  • gfx.blacklist.webgl.angle: 3
  • gfx.blacklist.webgl.msaa: 3
  • gfx.blacklist.webgl.opengl: 3
  • gfx.direct2d.disabled: True
  • keyword.enabled: False
  • layers.acceleration.disabled: True
  • network.cookie.cookieBehavior: 1
  • network.cookie.prefsMigrated: True
  • places.database.lastMaintenance: 1423478416
  • places.history.expiration.transient_current_max_pages: 12984
  • plugin.disable_full_page_plugin_for_types: application/pdf
  • plugin.importedState: True
  • privacy.clearOnShutdown.cache: False
  • privacy.clearOnShutdown.cookies: False
  • privacy.clearOnShutdown.downloads: False
  • privacy.clearOnShutdown.history: False
  • privacy.sanitize.migrateFx3Prefs: True
  • privacy.sanitize.sanitizeOnShutdown: True
  • storage.vacuum.last.index: 1
  • storage.vacuum.last.places.sqlite: 1421650511

Diverse

  • User JS: Nej
  • Tilgængelighed: Nej
Luk
guigs 1072 løsninger 11697 svar

In order to better assist you please update the browser to the most recent version: Update Firefox to the latest release

In order to better assist you please update the browser to the most recent version: [[Update Firefox to the latest version]]

Spørgsmålsstiller

I'd prefer to remain on FF 29 for now, unless there is a fix specifically for this problem in a later version. This is a general question about font rendering on recent FF versions.

I'd prefer to remain on FF 29 for now, unless there is a fix specifically for this problem in a later version. This is a general question about font rendering on recent FF versions.
guigs 1072 løsninger 11697 svar

Hi Wizardgoat,

Please make sure that you are also not affected by the update that went out from Microsoft and fonts. http://windowsitpro.com/msrc/patch-tuesday-font-corruption-kb3013...

Hi Wizardgoat, Please make sure that you are also not affected by the update that went out from Microsoft and fonts. [http://windowsitpro.com/msrc/patch-tuesday-font-corruption-kb3013455]
cor-el
  • Top 10 Contributor
  • Moderator
17537 løsninger 158575 svar

Are all the fonts installed locally? Is there a CSS file used or style rules or possibly a font tag?

In that case it should work without problems provided all the fonts are a compatible true type version and not older bitmap or possible not supported Adobe fonts.

Note that on Windows fonts that belong to one font-family might be grouped and a specify font chosen based upon additional style rules like font-style and font-weight (Arial Black) and font-stretch (Arial Narrow).

Are all the fonts installed locally? Is there a CSS file used or style rules or possibly a font tag? In that case it should work without problems provided all the fonts are a compatible true type version and not older bitmap or possible not supported Adobe fonts. Note that on Windows fonts that belong to one font-family might be grouped and a specify font chosen based upon additional style rules like font-style and font-weight (Arial Black) and font-stretch (Arial Narrow). *http://people.mozilla.org/~jdaggett/tests/arialblackweights.html

Spørgsmålsstiller

All the fonts in use are installed locally in the Windows Fonts folder. As it turns out, the generated HTML file causes numerous errors in the FF browser console. The HTML for each font contains a style keyword, and most of the errors are generated while parsing the font-family keyword within the style. For example, "Aldine401" parses okay, but "Aldine 721", containing a space, does not. However, that particular font is named that way in the Windows Fonts folder, so the software is just accurately picking up what's there. Apparently, Internet Explorer accommodates numerous font naming and content issues that FF does not.

All the fonts in use are installed locally in the Windows Fonts folder. As it turns out, the generated HTML file causes numerous errors in the FF browser console. The HTML for each font contains a style keyword, and most of the errors are generated while parsing the font-family keyword within the style. For example, "Aldine401" parses okay, but "Aldine 721", containing a space, does not. However, that particular font is named that way in the Windows Fonts folder, so the software is just accurately picking up what's there. Apparently, Internet Explorer accommodates numerous font naming and content issues that FF does not.
cor-el
  • Top 10 Contributor
  • Moderator
17537 løsninger 158575 svar

Nyttigt svar

Do the font-family names that have a space have quotes around them?

  • font-family:"Aldine 721";

See also:

Font family names must either be given quoted as strings, or unquoted as a sequence of one or more identifiers. This means that punctuation characters and digits at the start of each token must be escaped in unquoted font family names.
Do the font-family names that have a space have quotes around them? *font-family:"Aldine 721"; See also: *https://developer.mozilla.org/en-US/docs/Web/CSS/font-family <blockquote>Font family names must either be given quoted as strings, or unquoted as a sequence of one or more identifiers. This means that punctuation characters and digits at the start of each token must be escaped in unquoted font family names.</blockquote>

Valgt løsning

The css generated by Fontlist does not put quotes around font family names, including those with a numeric parameter. This explains part of the failures, but not all of them.

It's obvious that the html and css accepted by Internet Explorer is a lot more forgiving than FF.

The Fontlist developer would have to address this issue.

The css generated by Fontlist does not put quotes around font family names, including those with a numeric parameter. This explains part of the failures, but not all of them. It's obvious that the html and css accepted by Internet Explorer is a lot more forgiving than FF. The Fontlist developer would have to address this issue.