Font Encoding and MSIE5

[ArchivePoster]

Posted by: towerofpower
         

[ArchivePoster]

Posted by: Si
         
Does the problem occur when using the real font as well, or only when using the embedded font?

Cheers, Si

[ArchivePoster]

Posted by: towerofpower
         

It does occur with the real font as well. It's a truetype font, installed in the Windows fonts folder, and when I call-up that font by means of a fontface tag
(non-CCS-style):

äöüÖÄß

_AND_ MSIE is set to ISO/WesternEurope-Coding the special characters are being displayed in MSIE's default font.

Is there something wrong with the font encoding I performed in WEFT? I used WEFT Version 2 since weft3b5.exe doesn't complete the install on my
computer: "Failed to install component". That problem seems to be related to Icom.dll since that's the component being shown in the installation window when
that error message appears. OS is Win98SE / German.

Thanks!

Oliver

[ArchivePoster]

Posted by: Si
         
The encoding problem - if the real installed font has the problem then the issue relates to IE and/or the font itself (and not WEFT). This isn't really something I can help with. Maybe an HTML wizzard on this list (or another) may be able to suggest a solution.

The install problem - a few people have reported this - Michael is investigating and hopefully we will have a fix soon.

Si

[ArchivePoster]

Posted by: kai
         

It does occur with the real font as well. It's a truetype font, installed in the Windows fonts folder, and when I call-up that font by means of a fontface tag
(non-CCS-style):

äöüÖÄß

_AND_ MSIE is set to ISO/WesternEurope-Coding the special characters are being displayed in MSIE's default font.

So, your first posting was wrong. You do not have to use "user-defined" to make it display. ;-)

You can embed fonts only with CSS and should forget about FONT FACE tags, anyway. Besides, it doesn't make sense to use it for fonts usually not available on a visitors system since FONT FACE can't embed them.

[ArchivePoster]

Posted by: Si
         

Kai, this...

You can embed fonts only with CSS and should forget about FONT FACE tags, anyway. Besides, it doesn't make sense to use it for fonts usually not available on a visitors system since FONT FACE can't embed them.

is wrong. The link to the embedded font object is CSS...

  @font-face {
    font-family: FGM;
    font-style:  normal;
    font-weight: normal;
    src: url(/typography/graphics/FRANKLI0.eot);  }

But then whenever the font name 'FGM' is specified in a web page - using CSS or FONT FACE the embedded font will be used.

Si

 

[ArchivePoster]

Posted by: towerofpower
         

Kai,

I use Cascading Style Sheets for the complete design, and define the usage of all fonts within those style sheets. Thus, I don't use the fontface tag anywhere within the code.

My second posting, which mentions the fontface tag, was a reply to a question whether the original source font (truetype) would be OK. I checked that with Wordpad _and_ by means of using the fontface  tag in a piece of ordinary HTML code. _That_ HTML code does _not_ use CSS and it does _not_ instruct Internet Explorer to download embedded fonts.

This way MSIE checks whether it finds that particular font in the Windows fonts directory. And, if it does so, it will use that TrueType font from the fonts directory.

Strangely, the special characters of the source TT font display correctly with Wordpad, but they don't within the browser. MSIE uses it's default font for those special characters -- no matter whether the font has been downloaded via WEFT or is installed locally as a TT font -- except for one special case: If MSIE is set to "User Defined Encoding" in the View-menu then those special characters are being displayed in the font I asked for. And that holds true for the "local" font as well as for the download-font.

That problem occurs with _all_ the TT fonts I converted so far.

When I convert those fonts with the Bitstream tool (PFR), they display fine in Navigator - including the special characters. And they display OK in any Windows application.

Maybe it's a problem related to the mapping of characters within the fonts. I have no tools to check that, and I'm not very knowledgeable about that kind of stuff anyhow.

Oliver

[ArchivePoster]

Posted by: kai
         

My second posting, which mentions the fontface tag, was a reply to a question whether the original source font (truetype) would be OK.

Oh, I see.

Strangely, the special characters of the source TT font display correctly with Wordpad, but they don't within the browser. MSIE uses it's default font for those special characters -- no matter whether the font has been downloaded via WEFT or is installed locally as a TT font -- except for one special case: If MSIE is set to "User Defined Encoding" in the View-menu then those special characters are being displayed in the font I asked for. And that holds true for the "local" font as well as for the download-font.

I just wanted to check this with one of my pages and the newly converted HelveticaBQ TTF font. The Umlauts were displaying, but then I realized that it might just be the system fonts. So, I went to another machine and checked there. It doesn't display the fonts at all, it's IE 5.5 and apparentally IE 5.5 has lost embedding completely :-( So, I can't say for sure if the Umlauts show here or not. However, I can say that other special characters like ô or • do display in IE 5.01 when embedded and no system font is available. At least for me. Maybe a matter of the use of entities?

Do you have a URL with some examples and possibly fonts I do not have installed, so I can check them from here?

[ArchivePoster]

Posted by: mjan
         

fyi - Font embedding works fine in IE 5.5

 

[ArchivePoster]

Posted by: kai
         
You are right, mistake on my side. I hoped it would embed for www.domain if I bind it to domain, it didn't. It works now and I can reproduce the above-mentioned problem: Umlauts and other special characters do not show. Seems to be an IE problem, also in IE 5.5.

[Tags:]

Jump to: Please select a destination: ----------------------------- News and announcements ----------------------------- => Announcements from the forum’s moderators => News from the font industry ----------------------------- Type design and font technology ----------------------------- => Principles of type design => OpenType Layout feature development => Hinting => Font Formats and OpenType => Web font embedding => Font licensing ===> Electronic EULA Abstract (EEULAA) ----------------------------- Education and collaboration ----------------------------- => Work: Offers => Work: Looking for => Education: Offers => Education: Looking for => Typographic Events and Conferences ----------------------------- FontLab products ----------------------------- => News from FontLab => FontLab Studio ===> FontLab Studio Problems ===> FontLab Studio Tips and Tricks ===> FontLab Studio Wish List ===> FontLab Studio Public Preview => Fontographer ===> Fontographer Problems ===> Fontographer Wish List => TypeTool => AsiaFont Studio => TransType => ScanFont => SigMaker => Other Products ----------------------------- Photofont products ----------------------------- => BitFonter => Photofont WebReady => Photofont Start => Photofont ID => Photofont QX => The Photofont technology ----------------------------- Adobe Type products ----------------------------- => Adobe FDK for OpenType (AFDKO) ----------------------------- Apple Font products ----------------------------- => Apple Font Tools ----------------------------- Microsoft Typography products ----------------------------- => Microsoft Font Validator => Microsoft Visual OpenType Layout Tool (VOLT) => Microsoft Web Embedding Fonts Tool (WEFT) => Microsoft Visual TrueType (VTT) ----------------------------- Other products and Python scripting ----------------------------- => Python scripting => FontTools/TTX => Other font-related tools ----------------------------- Special interest groups ----------------------------- => SBL Fonts ===> SBL Hebrew ===> SBL Greek ===> SBL BibLit ----------------------------- FAQ and TechNotes ----------------------------- => OpenType Layout feature development FAQ and TechNotes => Hinting FAQ and TechNotes => Font Formats and OpenType FAQ and TechNotes => Web font embedding FAQ and TechNotes => Font licensing FAQ and TechNotes => FontLab Studio FAQ and TechNotes => Fontographer FAQ and TechNotes => TypeTool FAQ and TechNotes => AsiaFont Studio FAQ and TechNotes => TransType FAQ and TechNotes => ScanFont FAQ and TechNotes => SigMaker FAQ and TechNotes => BitFonter FAQ and TechNotes => Photofont WebReady FAQ and TechNotes => Photofont Start FAQ and TechNotes => Photofont ID FAQ and TechNotes => Photofont QX FAQ and TechNotes ----------------------------- Archive (MSN Groups) ----------------------------- => Archive: Old FontLab forum ===> Archive: FontLab Tips and Tricks ===> Archive: FontLab Bugs and Problems ===> Archive: FontLab Wish List ===> Archive: FontLab Announcements => Archive: Old Microsoft Font Validator group => Archive: Old Microsoft VOLT group => Archive: Old Microsoft VTT group ===> Archive: VTT Downloads ===> Archive: VTT Support ===> Archive: VTT Suggestions => Archive: Old Microsoft WEFT group ===> Archive: WEFT III ===> Archive: EOT for Email => Archive: Old SBL Fonts group ===> Archive: SBL Hebrew ===> Archive: SBL Greek ----------------------------- Various ----------------------------- => fontlab.com — the FontLab website => forum.fontlab.com — this forum => Other Topics