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.


Paul van der Laan
Last Active
Member, Type Person
  • 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!
  • Re: Florin sign (ƒ)

    The /florin – as with other currency symbols – needs to work with numbers and therefore I usually design it differently than italic /f. Especially when it needs to work with lining numbers I make the descending part shorter. Also I might design the proportions wider, and place the horizontal bar on a different height than x-height.

    Here is an example of /florin versus /f from AudiType Bold Italic:

  • Re: Naming font modifications

    One reason why we always strongly advise our clients on changing the name for custom font modifications is that their use is rarely contained within the organisation/company itself.

    Third parties – such a freelance designers, printers, banner makers, web developers – need to use these fonts too. In these cases a lot of confusion/frustration is avoided if the customised fonts are clearly named differently.

    For this very reason we think it is best to add the name of the client to the font name.
  • Re: Why are composite glyphs not used whenever possible in exported TTF files?

    I can imagine one reason why sometimes it might not be preferable for certain glyphs to be made of composites: hinting.
  • Re: How do I set up various IJ digraphs in my typeface?

    In Dutch, a word like fijn (nice) should not use an fi ligature. It is the ij that are the ligature. My fij Standard ligature fixes that problem. 
    The Dutch /ij is not a ligature, it is a digraph which means that it is just a combination of two seperate letters.

    In lowercase the use of a connected form for /ij is rarely preferable unless one tries to mimmick handwriting. In uppercase the use of a connected form for /IJ is a nice typographical touch, but nothing more than that.

    Both connected forms of ij/IJ are better off in the <dlig> feature than in standard ligatures.