Error #E2147 gen. by FV

[ArchivePoster]

Posted by: ise_lekhni
         

Sir,
Comments in the OT spec. for OS/2.fsType - mention that -
For compatibility purposes, most vendors granting Editable embedding rights are also setting the Preview & Print bit (0x000C).

This is what I did for my font. The FV generated Error #E2147 which I think it should not have as in OT spec these bits (1, 2 and 3) are not specified to be mutually exclusive.
In case of mixing bit 1 with 2 or 3, FV may generated a warning; but mixing 2 and 3 should be OK!

Akhil

         

[ArchivePoster]

Posted by: Si*
         

Where did you read this? My reading of the spec is that you should only set one bit for P&P, editable, no embedding or installable - there would be no point in setting P&P and editable as editable would trump the other setting.

Si

         

[ArchivePoster]

Posted by: ise_lekhni
         

Si_r

 

I was referring to OS2.htm that was in Otsp13p.zip that I downloaded from MST in past. This spec 1.3 refers to version 1 and 2 of OS2 table. As the version of OS2 table is not 3 (as in OT sp 1.4) in my font. I thought that it is proper for me to refer to it.

 

Following is the comment in OS2.htm in Otsp13p.zip (what the last 'p' for? 'proposed'! whether it wasn't a spec?)

 

Comments:

If multiple embedding bits are set, the least restrictive license granted takes precedence. For example, if bits 1 and 3 are set, bit 3 takes precedence over bit 1and the font may be embedded with Editable rights. For compatibility purposes, most vendors granting Editable embedding rights are also setting the Preview & Print bit (0x000C). This will permit an application that only supports Preview & Print embedding to detect that font embedding is allowed.

 

Now when I referred to OT sp 1.4, I understood that FV expect version 3 of OS2 table. Whether changing version of OS2 table to 3 requires any changes in other tables. What is the logic for changing version number from 2 to 3 when fields are same? I think I should go thru the ver 1.4 for finding new interpretations of fields etc.

         

[ArchivePoster]

Posted by: Paul
         

The interpretation of the embedding bits has been the same for a long time. In our tool we make multiple bits being set as an error because setting multiple bits don't have valid meaning and it is against the font quality we want to encourage by the use of Font Validator.

 

Regards,

 

Paul

         

[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