So, yeah, I rolled my own. The primary change from the prebuilt SS02 version was that I made it standard-width and a bit lighter. And reversed the slash on the zero, just because I could. I included the build plan and the necessary diffs in the Zip file, and only built Regular and Bold with their matching italics.

Completely unrelated, Amazon recommended a new manga series to me: To Save The World, Can You Wake Up The Morning After With A Demi-Human?. In which Our Hero’s mission is to knock up as many monster girls as possible in the hope that one of them will give birth to The Chosen One who will defeat The Demon Lord.

Except that he’d really rather just hold hands with the cute elf girl in his homeroom class. And he passes out whenever the girls get him excited. And then they do him anyway while he’s out. And the more often they all get a fill-up, the more potent his secret sauce becomes, so they’re all willing to share. Even the Legal Loli dwarf girl who can’t quite wrap herself around it yet.

Not an isekai, apparently, just a perfectly ordinary Japan with a wide variety of horny monster girls and a recurring Demon Lord infestation.

9/2 update

I decided to make the bold a bit bolder, to better differentiate it at various sizes. Zip file updated.

After working with SomeType Mono for a little while, I decided to quantify my font ratings.

I started by dusting off my old fontforge svg2ttf script, since I knew its Python API exposed everything I needed. Then I discovered that I can’t get that API to work any more. Somewhere between the Python 2->3 updates and Homebrew’s descent into madness, it done broke.

I know how to extract metrics and outlines using Font::FreeType and Cairo in Perl, and most of what I need is already exposed in my PDF::Cairo module, but I’d have had to do some mucking about with internals to get it all, and it would have added a messy dependency should I decide to share the script.

So I switched to Adobe Font Toolkit, which cleanly installs into a Python virtualenv without any issues. Its tx utility can both extract metadata and calculate precise bounding boxes for every glyph, which allows me to measure many of my concerns:

FONT OfficeCodePro-Regular.otf
x-height 69.012% of ascender height
relative width 100.000%
vertical centering offset from '=':
! greater -3.79%
! less -3.79%
! parenleft -7.04%
! parenright -7.04%
! bracketleft -7.04%
! bracketright -7.04%
! braceleft -7.04%
! braceright -7.04%
! bar -10.83%
width compared to '=':
! asciitilde +4.19%

This tells me that Office Code Pro has a standard typewriter width (Courier, Prestige Elite, etc), a decent x-height, equal widths for -=+, a slightly-wide ~, common vertical centering for =-+~*&#%/\ and digits, a very small vertical offset for <>, a bigger one for ()[]{}, and an annoyingly large one for |. Since I’m not analyzing the glyph outlines yet, I can’t tell that it has a five-lobed asterisk and a slashed zero.

For comparison, here’s the latest release of Iosevka Fixed SS02 Regular:

FONT iosevka-fixed-ss02-regular.ttf
x-height 69.829% of ascender height
relative width 83.333%
vertical centering offset from '=':
! asciitilde -2.11%
! ampersand +3.62%
! percent +3.62%
! zero +3.62%
! X +3.62%
width compared to '=':
! asciitilde +19.47%

Similar x-height, much narrower, &% aligned with caps/numerals, and twiddle a hair low and extra-wide.

The last time I looked at Iosevka, all the “SSnn” variants were built with the same family name, so you couldn’t tell which of the sixteen variations you’d downloaded except by the file name. They’ve cleaned things up quite a bit, and now it’s fully scriptable so you can roll your own variation and Have It Your Way. The downside is that the repo is over 5 gigabytes. The other downside is that it uses npm.

Other fonts I’ve tried recently? IBM Plex Mono (painfully short hyphen, dotted zero, goofy #), Cascadia Mono (the dotted zero and goofy alphabet clobber its otherwise perfect score, although I’d use Light rather than Regular), Go Mono (five-lobed goofy asterisk, serifs, and inconsistent punctuation weight), JetBrains Mono NL (dotted zero, five-lobed asterisk, small-but-consistent vertical offsets for ()[]{}/\|~*), and Code Saver (short hyphen, high /\, low |).

Oh, and the name of my script? Termanal. If I ever roll my own custom font, obviously I’ll call it Termanal Regular. 😁

Update

Just found the current much-expanded version of the Inconsolata family. Slashed zero, ligatures off by default, five-lobed asterisk, annoyingly short hyphen, slightly-low [], annoyingly low |, eight weights, and nine widths (166%, 125%, 100%, 92%, 83%, 75%, 67%, 58%, and 42% for when you need all the columns).

I’m trying out a programming font, the free Sometype Mono. It avoids almost everything I hate about coding fonts, and beats out the previous champ Office Code Pro by not having an italic $ or five-lobed *. Set width is a bit narrower, but not as condensed as the same designer’s non-free Code Saver ($25 for 3 weights and matching italics, if you like squeezing a few extra columns into your windows). Specifically, an 80-column window of Office Code Pro will fit 83 of Sometype Mono, 86 of Code Saver, or 88 of my former standard Anonymous Pro.

I can get Code Saver through my Adobe CC subscription, but I’m going to start with the free one, since I’m setting up a new work laptop this weekend, and it won’t have an Adobe license.

Update

The Programming Fonts web site, which I hadn’t visited for a few years, includes Sometype Mono in its live previews, as well as an increasing number of cleanups of existing fonts to fix many of my complaints. The least-unreadable preview setting at the bottom is the base16-light color scheme and the None syntax coloring.

I have a hate/tolerate relationship with so-called “programmer’s fonts”. Let me count the ways they suck, in no particular order:

0. Not fixed-width. Blech.
1. Too-narrow set width (ranging between condensed and crushed).
2. Inconsistent weight/color between alpha, numeric, and punctuation. The creator of Fira Code actually managed to make \ and / different weights!
3. Twee punctuation.
4. Failure to adequately distinguish 0O, l1, etc.
5. Dotted zero instead of slashed (so that 00 is staring at you; Hack takes this one step further, for an Eye-Of-Sauron effect).
6. Inconsistent centerline for special chars (^>~*+=-})]|\/#$%&@).
7. Special-char centerline inconsistent with digits.
8. - not same length as + and = (surprisingly common!).
9. Five-lobed asterisk, even worse when it’s upside-down.
10. Poor rendering either on or off high-DPI displays.
11. Special Dishonorable Mention to Monofur for having lower-case digits, seemingly-random centerlines, twee punctuation, and a generally obnoxious character design.

For a long time, I’ve been using Anonymous Pro, hand-edited to fix its centerline problem, but the new winner is Office Code Pro, which suffers only from a slightly-twee %, a slightly-italic $, a five-lobed *, and an ever-so-slight centerline offset for braces, parens, and the v-bar (most easily seen in the -{| combo).

It is hands-down the cleanest, most usable fixed-width font I’ve ever found, fixing almost every problem with its parent, Adobe’s free Source Code Pro. Pity the repo just has the compiled fonts rather than the source diffs, because I’d love to fork it and fix those last few niggling flaws.

Let’s say that you have purchased a shovelware disc of Japanese fonts, such as this one from DynaComWare (discontinued, but it turns up occasionally; I bought mine at a going-out-of-business sale).

[Note that when I describe this particular disc as “shovelware”, I’m really referring to the collection of 3,000+ renamed ripoffs of Western fonts (from font pirate Bay Animation) that are thrown in; for Japanese, Chinese, and Korean fonts, DynaComWare is a legitimate foundry.]

The ripoffs (as well as the Korean, Chinese, special-effects, and kana fonts) are just stored on-disc with no protection, but the good stuff is hiding in files with the .t4_ and .t9_ extensions. The only supported way to install them is by running the included Windows program (which might not display correctly on non-Japanese versions of Windows, and of course doesn’t work at all on a Mac), but it turns out that they’re just encrypted ZIP files with a simple 8-digit numeric password, six digits of which can be inferred from the timestamp.

One thing to note is that the disc contains two sets of kanji fonts, in directories labeled JIS90 and JIS2004. The difference between the two is a subtle appearance change in a small number of characters, neatly described in this Adobe PDF file. A small number of fonts are available only in the JIS90 flavor, mostly pseudo-bitmap fonts of little real value; most people won’t notice the difference, and if you do, well, you’ve got both.

I highly recommend the disc, by the way.

Adobe has released an Open Source coding font, appropriately named Source Code Pro. I tried it out, and while it’s mostly nice, a side-by-side comparison of the fixed-width fonts on my machine reconfirmed that the also-free Anonymous Pro still beats them all.

Of course, if you don’t write Perl, you might not need expressions like “$K[$i%@K]” to look good, but I still can’t be comfortable with any font where “00” looks like it’s staring at you…

And my test sample, if you’re interested, consisted of Andale Mono, Anonymous Pro, Consolas, Courier, Inconsolata, Monaco, Osaka, and Lucida Sans Typewriter.

World Tools Pro enables most of the hidden Japanese typography functionality in InDesign, but as I discovered the moment I tried to really use it, they left out the ability to add custom ranges to composite fonts. The fix is to create the composite font as usual, then open the Adobe ExtendScript Toolkit, paste in the following snippet of code, edit as needed, and run it:

app.compositeFonts.item(1).compositeFontEntries.add({
    name:"Macron",
    customCharacters:"āĀēĒīĪōŌūŪ",
    appliedFont:"Minion Pro",
    fontStyle:"Regular",
    relativeSize:100,
    baselineShift:0,
    verticalScale:100,
    horizontalScale:100,
    scaleOption:false
  });

Set the value of item() based on font’s position in the pulldown list; the meaning of the rest should be obvious.

Q: What happens when you print white text on a black background?

A: The black ink bleeds into the letters, making them thinner and obscuring fine details. The extent of this problem depends on the specific printing technology, but a good rule of thumb is to use bolder fonts when you do white-on-black.

Q: What happens when you print white kanji, really small, on a light gray background that’s constructed as a color halftone?

A: Garbage.

more...