Problems with embedding Adobe Type 1 fonts

[ArchivePoster]

Posted by: kai
         

[ArchivePoster]

Posted by: kai
         
Ahm, is it safe to install WEFT 2 parallel to WEFT 3 and check what's the outcome there?

[ArchivePoster]

Posted by: mjan
         

Re. font naming - The names you see comes from the font you use. Yes, you are correct, the names are a mess. You should contact the authors of the font and have them fix it. The name "HelveticaBQ Light" is a "face name". It should *not* be used. The name "Helvetica BQ-light" is the "family name" is should be used. In general, use family names.

Re. adding fonts manually - If WEFT says that a page does not use a particular font, then the page does not. Period! Adding the fonts manually would not make a difference. Also, if you manually add fonts then you need to manually add the CSS code to page that should use the font. 

The problem is probably that you use the face name instead of the family name in the web page. You do not want to use the names in the fonts folder. Use an app like WordPad instead, and see what the fonts are calling in the system font picker dialog.

Re. "add list" - Which "add list"? Do you mean "available fonts" or "font to embed"?

Re. direct file add - Actually, this is what WEFT always does. WEFT works on the font files listed in the "Available fonts" view. To create an eot for a font file without specifying a page, use the "expert create fonts" dialog. Please note that this is for experts. If you do not fully understand the concept of the "bind url", the difference between a face and family name, and fully understand CSS, then you may not be able to get it to work.

 

 

[ArchivePoster]

Posted by: mjan
         

We do not recomend using Weft2 and Weft3 on the same machine.

WEFT Development,
- Michael

[ArchivePoster]

Posted by: kai
         
Thanks, for your reply. You did not understand the core of my problem. I hope I can explain it now better. Your "available fonts" list shows indeed all my system fonts, however, your "Add" list does not. The "Add" list is what I get if I hit "Add" after "Analyzing" or in "Expert Create Fonts". The list is just named "Microsoft WEFT". This dialog does NOT show all the fonts from "available fonts" (the fonts I explained as missing in my original post). F.i. it shows the BQ Light but not the BQ bold and it shows only one Utopia while there are four.

[ArchivePoster]

Posted by: mjan
         

This is by design.

The font picker dialog lists all font families. Each family is then listed with the four font styles that Windows can handle. For example, "Helvetica" "Helvetica Bold", "Helvetica Italic" and "Helvetica BoldItalic" are not four fonts. They are four style variations of the same font. Besides making the list 1/4 as long and 4 times as fast, this is also the most intuitive way of listing fonts (compare to virtually any font picker in any application).

This obviously does not work when you have more sophisticated style variations, such as Semi-bold, light, black, book, heavy, expertset, script, old-style, etc. Since Windows does not allow for a family to contain more than the above mentioned variations, fonts are often broken into sub-families. For example, "Helvetica Narrow" is treated as a different family than "Helvetica". This is not as pretty as one would like, but it does work.

In your case, you are working with two families; "Helvetica BQ" and "Helvetica BQ-light". This is of course all from the technical perspective of Windows. As such, there may be a bold, regular, italic and bold italic version of both families (although a bold version of the light family would not make much sense).

So, "Helvetica BQ Bold" is the "Bold" style of the "Helvetica BQ" family. Pick "Helvetica BQ" and then "Bold" and you are all set. You may also pick combinations that do not really exist, in which case Windows will do it's best to create the style variation for you.

WEFT Development,
- Michael

 

[ArchivePoster]

Posted by: kai
         

Hi Michael, thanks for your explanations.

You say I should use the "font family" "Helvetica BQ" - ahm, that is exactly my problem: your "Add" list does not show it, so I can't add it. It shows in the available fonts but not anymore in the Add list.

I deinstalled Weft3 and installed Weft2 and now I see that all fonts which are not showing in the Weft3 Add dialog are marked as "may be broken".

Helvetica BQ: may be broken

Helvetica BQ-Light: no embedding font

while both show as "installable" in Weft3.

The other problem I mentioned (light shows as bold) seems to be a genuine IE5 problem. Since I now know the correct fonf family names I was able to use the fonts directly instead of embedding them. The Helvetica BQ-Light displays in IE definitely like it were HelveticaBQ (bold) while it shows correctly f.i. in Word. There must be something broken in IE5 (and 5.5) which produces this. I tested by truncating the name a bit to see if it may stop reading the name at the minus sign. No, it doesn't, it sure understands that it should use HelveticaBQ-Light but actually it uses HelveticaBQ. And apparentally the same happens when WEFT3 is run on it, as I understand it relies on IE. It skips Helvetica BQ somehow but produces an .eot from the Helvetica BQ font when I want it to produce one from the Light file.

There is no way to easily convert a Type 1 font to TT or OT, isn't it? (I have to use this font and it's apparentally available only in Type 1 from Berthold.)

I mentioned the same problem with Utopia. Actually this is only ONE font family with four variants, as you describe, that explains why it only shows once in the Add list. The interesting thing is that two of them (Utopia and Utopia Italic) show up as "may be broken" as well while the two others are not. There are several Type 1 fonts marked this way, including ones from Adobe. There are also lots of Bitstream fonts which show "needs repair". I think I read somewhere in the forum that Bitstream fonts often show problems. I'm just wondering why I then can use them in Word f.i. without a problem. When I opened one of them from the "available list" I also got a dialog asking me if I would want to repair. However, after clicking Yes it barked about a missing program for this - what's necessary for this "repair"?

[ArchivePoster]

Posted by: Si
         

It seems as if there's still a little bit more work to do with Type 1 fonts.

The WEFT 2 issue with Bitstream fonts has been discussed - see the thread 'FAQ - BT Fonts'. We're not going to revisit WEFT 2 type 1 issues.

Cheers, Si

[ArchivePoster]

Posted by: mjan
         

I'll look into the problem with the missing "Helvetica BQ" family.

Re. the problem you mention with "needs repair" and "may be broken", please use Weft3 instead to resolve these problem.

WEFT Development,
- Michael

 

[ArchivePoster]

Posted by: kai
         

Re. adding fonts manually - If WEFT says that a page does not use a particular font, then the page does not.

There is a small bug with installed font family names. After I used the correct font family names (instead of the font names) WEFT found the fonts in the page but could not find one of the fonts on the system because of a hyphen in the name. You seem to strip all hyphens from names. So, "HelveticaBQ-Light" could not be found because it's in the page with that name (and identified and shown correctly by IE) but WEFT is looking for "HelveticaBQ Light" (no hyphen) on the system.

[ArchivePoster]

Posted by: mjan
         

Well, no not really. WEFT gets the name of the font from two places; IE and the font files. There are no magic mangeling of the names, such as removing hyphes. However, you may get into trouble if the "wrong" name is being reported back to WEFT after analyzing the page.

Since you are using a font that is badly named, you will get weird results. I am not able to tell you why that is before I have had a chance to look at the font.

WEFT Development,
- Michael

 

[ArchivePoster]

Posted by: kai
         
I will let someone have converted the two fonts to TT and will then check how it works with WEFT and embedding. If I run into problems I will post here. I will then consider Type 1 as "do not use it".

[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