Howdy, Stranger!

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

Bhikkhu Pesala

About

Username
Bhikkhu Pesala
Joined
Visits
795
Last Active
Roles
Member
Points
59
Posts
83
  • Re: Show me your failures!

    My embarrassing mistakes are too many to list, but this one comes close to being the worst. FontCreator's Preview toolbar using a Windows control that does not support colour, and most apps don't yet support colour fonts either, but that's not the problem.

    I designed my multi-coloured glyphs primarily for use on the Web, but they should at least work in monochrome. After a recent update to "fix" problems with intersecting contours I managed to break the monochrome version. I am still too busy to fix it properly. Reverting to an earlier version would lose too many other fixes.

    Top is how it should look in monochrome:


    Bottom is how it actually looks in colour and monochrome:
    The colour versions is still fine, and works in Web Browsers, but the Stylistic Alternates cannot be used in print applications that don't support coloured font technology.

  • Re: Units per em

    Abraham Lee said:
    I presumed that the main reason for increasing the funits/em would be to support delicate features, but I never would have imagined going to 4096 or 8192 funits/em. Are there many fonts that do this? Is the only reason _not_ to that it will increase file size because you're using larger integers? Does that have that much of an impact? Thanks for feeding my curiosity.
    I have only come across a few that used 8192, and as I said Gabriola uses 4096. One foundry that deserves to remain anonymous (but not for that reason) uses 4096 funits/em.

    File size increase for my Guru Italic font with 2,893 glyphs (and 1,265 composites) is as follows:

    Hinted

    2048 funits/em = 916 KB (938,232 bytes)
    4096 funits/em = 940 KB (962,928 bytes)
    8192 funits/em = 959 KB (982,232 bytes)

    Unhinted
    2048 funits/em = 719 KB (736,496 bytes)
    4096 funits/em = 737 KB (755,016 bytes)
    8192 funits/em = 761 KB (779,384 bytes)

    I think there is still a good reason for sticking to multiples of 2^ however fast modern computer chips may be, and in spite of Microsoft's recommendations being made in 2002. Even microseconds add up if many operations are performed when rendering text for the screen on zooming in or reflowing text. 

    For Mac OX, 1,000 funits/em is recommended. Apparently, there's a bug that affects PDF output for fonts with different funits/em values.
  • Re: Units per em

    If a font contains very fine details, http://forum.high-logic.com/viewtopic.php?f=3&t=5093&p=22507 use a higher funits/em value. 

    At 2048 funits/em very small circles will no longer be circular, so increase the value to 4096 or 8192 funits/em.




    Scripts with fine lines like Gabriola use 4096 funits/em. 
  • Re: How do I tell if a given .otf file is TT or PS-flavored?

    Yes. Windows Font Viewer still does this. It is still worth installing the free version of MainType though if you're using Windows, as it's a useful font manager for home users.
  • Re: Special dash things: softhyphen, horizontalbar

    Three type designers walked into a bar. 
    The first two said, “I must dash,” and left without another word.
    The third muttered to himself—after a space—“What’s wrong with ’em?”