Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Paul van der Laan

Dat zijn rare foutmeldingen. Probeer inderdaad eerst de andere packages opnieuw te installeren. Als dat niet helpt kan ik je mijn kopie van RF sturen, die werkt prima onder FontLab 5.1.4 (4868) en Yosemite.

About

Username
Paul van der Laan
Joined
Visits
7,190
Last Active
Roles
Member, Type Person
Points
228
Posts
184
  • Re: [OTVar] Axes Proposals: variationsguide.typenetwork.com

    In that case I don't see the problem! This far, the usual way of handling a weight change is to change the boldness of a glyph outwards, thus widening the character, but I don't have a problem with an axis that would only change weight inwards. (Or at least without an accompanying advance width change.)
    This view is too simplistic I’m afraid. The correct way of adding weight whilst simultaneously making sure the shape maintains the same *optical* width is by adding weight both outwards and inwards. Usually around 2/3 outwards, and 1/3 inwards depending on the design.

    And this only applies to the (mostly) Latin-centric view that a glyph consists of two vertical parts (such as in /a /b /h /o for example). For a glyph such as /m it already becomes a different matter.

    Also: how do you make glyphs such as /l /i /j /I bolder by adding weight inwards?
  • Re: Munson, a Victorian style slab serif

    Terminology-wise I would not call this design a “slab serif”, nor a “Clarendon”.

    The serifs are clearly bracketed here, and Clarendons are characterised by a much lower thick/thin contrast. This design looks more like a Scotch to me.
  • Re: Origins of Python in Type Design

    And then there was RoboFog, a customised version of Fontograper 3.5 modified by Petr van Blokland, Just van Rossum and Erik van Blokland in 1995, that was the first font editor to include Python scripting. This introduced many type designers at that time to Python.
  • Re: Superscript – missing forms

    I think Fontographer is to blame for making people think that fractions were part of Macintosh encoding in PostScript Type 1 fonts.


  • Re: Font naming and version control - incl. different formats

    The Python FontTools library gives access to the contents of most common font file formats. For OpenType and TrueType fonts it will be a matter of writing a Python program that can iterate through folders with font files, open them via FontTools, and then collect all necessary info from the 'name' table. Additionally the code can check for the existence of a 'glyf', 'CFF ' or 'CFF2' table to determine whether the font is TrueType or PostScript flavoured.

    Output could be a tab-seperated text file which can be imported in a database or spreadsheet.

    Not sure what font formats are exactly used by LaTeX (pfa?). There is a chance that FontTools will be able to open that format too. But you will have to check that particular file format spec how it stores the naming.

    Hope this helps!