« 作りましょう! | Home | Animated romance day »

Tsukurimashou typeface demo

Sun 28 Nov 2010 by mskala Tags used: ,

I added the Latin alphabet, so far only the uppercase letters, to Tsukurimashou, and this brings it to a point where I feel okay about releasing a demo PDF file, so y'all can download it and take a closer look at my handiwork.

Some things to remember:

  • The main purpose of this typeface family is as a pedagogical exercise. It's the process of creation that is more important than the finished product. Hence the name.
  • It's designed for the Japanese language. Typesetting modern Japanese requires having the glyphs for English too, but that doesn't mean the fonts are usable for general English-language typesetting. In particular, this is a monospace font with a choice of typesetting one character per perfectly square box, or two. That'll make it look unnaturally extended or compressed if you use it to typeset English text of more than a word or two at a time.
  • All five styles shown are generated from the same source code by tweaking a few parameters, and many other styles not shown in the demo can easily be generated with very little extra work.

As I'd hoped, I'm learning a lot about type design by doing this. One interesting observation is that the way the hiragana and Latin alphabet are constructed really is fundamentally different. The hiragana usually consist of a very few complicated brush strokes. They don't have sharp corners like right angles, but they DO frequently have super-sharp corners where the brush suddenly reverses direction. (For instance, at the upper right corner of て, or centre left of を.) Those really screw up some of the technology I'm using (in particular, MetaType1's "pen_stroke" macro and Fontforge's postprocessing) and I'm having to use a lot of wacky numerical tricks to get around it. In the Latin alphabet, on the other hand, there are many right and acute angles, like at the corners of letters like E and W. I think some of those will show up in the katakana as well, which I haven't started yet (will probably do lower-case Latin first).

Moreover the way I've found it convenient to define the coordinates is different between the two. For the hiragana I was printing out a sheet for each character with versions of that character from several other typefaces printed on grids for reference, and a large blank grid where I'd draw my own version with a ballpoint pen. That helped me figure out approximately where all the control points would be, then once I entered the coordinates into the computer I'd go through several iterations of changing the numbers to get it to look right. The result might be quite far from what I'd drawn on the paper, but it usually would have the same arrangement of points - and, importantly, in the Metafont source code the points would all be specified by their explicit coordinates.

With the Latin alphabet it's quite different: I've been designing on the computer directly (okay, that's partly because I did about half the letters on the bus between here and Waterloo, where I couldn't be messing around with paper), but I'm also using Metafont's linear-equation solver much more. Most of the points are defined by percentages of where they sit between other points. I think that's closer to Knuth's vision of how Metafont is meant to be used; what interests me is that it seems to work a lot better for the Latin letters than the Japanese ones. This points to something really different at a basic level in what the letters are all about. The Latin alphabet comes from Roman stone inscriptions, by way of several hundred years of printing tradition. The Japanese hiragana come from Chinese brush writing, and less influence from the printing process.

The shapes of the uppercase Latin alphabet in Tsukurimashou are mostly imitating Gill Sans, but that's not a monospace typeface and this is, so it's interesting to see how the spacing changes the look of the whole thing. I added bars at the top and bottom of the I and the top of the J, because without them those letters stick out oddly in monospace (they are much too narrow for the box). With the bars, they blend a lot better into the line. Another spacing-related thing comes from the fact I'm trying to define both the "full-width" and "half-width" Latin from one set of shapes. What's going on behind the scenes is that I designed the full-width letters and then some tricky code decides how much to squash each letter to fit it into the half-width box. It's nonlinear, depending on both how wide the original is and where it sits in its square box, so the relative proportions of the different letters change by different amounts, with the general effect of making the shapes "more monospace," that is, closer to all having the same width. For example, W gets squashed a lot more than I. I think the result is reasonable; not perfect, but I'm not sure any monospace Latin can be.

9 comments

Axel
Very nice - I like the non-condensed caps. I would eliminate the serif atop the J. Gill Sans is actually a good model for a monospace font because of its formal British stiffness (apologies to Brit readers - the world's best university course for type design is in your country, at Reading, but Gill's old fonts are, well, stiff). Axel - 2010-11-28 08:56
Matt
As of this version I think that bar (I'm calling it a bar instead of a serif because I've seen it in many other faces that are, in general "sans serif"; it seems to me to be more part of the letter than other "serifs") sticks out too far on the right; although it's physically the same length on both sides, it's optically unbalanced. I probably don't want to eliminate it entirely - the earlier versions of J without it really didn't look good in context - but maybe the thing to do is reduce it so it dominates the letter less. I'd like J to remain distinct from T, and at present the compression brings them quite close together.

One thing I didn't notice about Gill Sans until I started dissecting it is that it's quite bottom-heavy. In letters like E, F, B, P, and R, the crossbar is a fair bit higher than the halfway mark, and the lower parts of the letters are correspondingly wider. That's also seen in S, but it's especially significant in R, where the lower-right corner actually crosses outside the line of the character box. I think this tendency helps the shapes continue to look good in the very expanded square-monospace situation. Matt - 2010-11-28 09:22
Axel
I guess that was a personal aesthetic reaction on my part; J usually has a cross-bar on top. It is an odd animal in that it does not exist in Roman inscriptions which are the model for our capitals, so it is an "invented" character along with capital U and W. Axel - 2010-11-28 11:14
Matt
That's probably related to why we don't know how to pronounce it. Matt - 2010-11-29 08:13
trythil
A suggestion for additional feedback: you may want to take Tsukurimashou to the critique forums at Typophile (http://www.typophile.com/forum/1). As for feedback from me -- well, I don't have any. I know the lingo of typography but am still woefully bad at constructive criticism.

Also, are you planning on incorporating the obsolete kana ゑ and ゐ? No real utility to them, but as a design exercise they might be fun. trythil - 2010-11-30 13:47
trythil
Hey, I'm blind -- you already did ゑ and ゐ. Never mind. trythil - 2010-11-30 13:53
Matt
Typophile: maybe once I have the katakana in. I'm concerned that the Typophilers, if given half a chance, will give me a lot of semi-constructive criticism on the design of the Latin alphabets and ignore the "things to remember" I list above.

Hmm... though maybe I could frame the discussion by making my posting in Japanese and pretending not to understand English responses. That might be fun.

As for ゑ and ゐ - I added those relatively late in the game (after doing the uppercase Latin), mostly just so that I could put the Iroha poem in my demo file. It was especially tricky doing ゑ because of all the direction-reversals (four of them, each requiring a numerical workaround), and I ended up making the brush stroke thinner to make it look less busy. With ゐ I was able to copy a big chunk of the curve from み. Matt - 2010-11-30 14:50
trythil
A suggestion for the type specimen: as a complement to the English alphabet, it might be useful to show the kana arranged in the Fifty Sounds table. Iroha's useful, but I think the table is a newer way of presenting the kana -- or at least it's how I've seen it done in Kanji & Kana and the Nakama textbooks.

On Typophilers: maybe. I lurk around there and read the occasional critique thread, so am not quite sure what the community as a whole would do with a typeface intended for typesetting Japanese, but I _do_ know that when Raph Levien took Inconsolata there, people did take into account that it was specifically designed for typesetting source code on paper. (Then again, Inconsolata sticks to the Latin.) trythil - 2010-12-02 08:20
Matt
That's a good idea. Another thing a sample really should contain is some nontrivial chunks of text, as opposed to just alphabets/syllabaries. But there's not much nontrivial text I can cut'and'paste in hiragana-only Japanese. Guess I'd better go make the other 3000 characters. Matt - 2010-12-02 21:12


(optional field)
(optional field)
Answer "bonobo" here to fight spam. ここに「bonobo」を答えてください。SPAMを退治しましょう!
I reserve the right to delete or edit comments in any way and for any reason.