Howdy, Stranger!

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

Belleve Invis


Belleve Invis
Last Active
  • Re: Units per em

    I would think that Asian fonts like Chinese, would be much easier to deal with at very high UPM. There are an awful lot more layers and strokes than compared to Latin.
    All type foundaries I know use a 1000×1000 square when drawing Kanjis.
    When building CJK typefaces for MS they sent me a lot of JSON files where coordinates are in float number!
    The target UPM is 2048, though. Most of the bytes in the file are instructions.
  • Re: Dedicate library for identifying strokes/stems?

    Do you mean to extract the skeletons inside black shapes? They're imaginary.
    Well, not exactly same. I'd like a separate library to identify horizontal / vertical stems.

  • Re: Eau de Garamond — a sans distilled from the essence of Garamond

    Eau’s Regular/Bold/Italic/BoldItalic does not have name ID 16 and 17.
  • Automatic generation of large-scale handwriting fonts via style learning (SIGGRAPH Asia 2016)

    Generating personal handwriting fonts with large amounts of characters is a boring and time-consuming task. Take Chinese fonts as an example, the official standard GB18030-2000 for commercial font products contains 27533 simplified Chinese characters. Consistently and correctly writing out such huge amounts of characters is usually an impossible mission for ordinary people. To solve this problem, we propose a handy system to automatically synthesize personal handwritings for all characters (e.g., Chinese) in the font library by learning style from a small number (as few as 1%) of carefully-selected samples written by an ordinary person. Experiments including Turing tests with 69 participants demonstrate that the proposed system generates high-quality synthesis results which are indistinguishable from original handwritings. Using our system, for the first time the practical handwriting font library in a user’s personal style with arbitrarily large numbers of Chinese characters can be generated automatically. 

  • Re: [OTVar] Introducing OpenType variable fonts

    How about the "mixed installation" situation? Especially for UI fonts with complex shapes (like: ideographs), we can provide a set of fully-hinted, non-variable series (the hints are calculated using an AI), and one variable file that covers all other styles...

    @Belleve Invis,

    A "mixed installation" -- combining a variable font with non-variable instance fonts -- is certainly possible. It would be up to different applications or platforms to determine which would be used if the axis values corresponding to the non-variable font were selected; the OpenType spec doesn't specify which should be preferred (just as it doesn't say what to do if you happen to have two fonts with the same family/subfamily names). In DirectWrite, I think we will likely select the more specific, i.e., the non-variable instance.

    Note, though, that there's no reason why the variable font can't be hinted. Indeed, the approach to hinting that Greg Hitchcock, Mike Duggan and gang are recommending these days fits well with variable fonts since it avoids deltas and uses a limited number of CVTs, and means that hinting of a family represented as a variable font requires a lot less time than hinting a number of non-variable instance fonts.

    But, if you want to display complex characters, like ideographs, clearly, you HAVE TO add deltas. It is a completely different MONSTER.
    ... not to speak of the lack of y-axis AA in GDI.
    When hinting letters, you have enough pixels, so the task is simply align points to key lines, and preserve stem widths. But ideographs are completely different. YOU DO NOT HAVE ENOUGH PIXELS. Just imagine: you have to fit 11 horizontal strokes in 12 pixels, and still preserving that character legible. Therefore, delta instructions are necessary, it will place some strokes to the same position, so you can read the general shape of that character.
    (so, another question: is GDI too complex and old to maintain? I've heard that it is completely written in assembly, and have many JIT compilers in it.)