[edwintorok]

Fira Sans is also one of the 3 free fonts (along with Charter and Source Code Pro) recommended by Butterick's Practical Typography: http://practicaltypography.com/

It is also used in Racket's documentation: http://typographica.org/typeface-reviews/fira-sans/

And here is how I use it in LaTeX:

  % Font settings
  \usepackage[T1]{fontenc}
  % Serif body font
  \usepackage{charter}
  % Math font
  \usepackage[charter]{mathdesign}
  % Monospaced font
  \usepackage{sourcecodepro}
  % Sans-serif font
  \usepackage[lf]{FiraSans}

[r0muald]

The comments on that review at typographica point out that Fira's quality for non-Latin scripts is less than perfect. Butterick generally ignores this part of the Unicode spectrum, to the point where his own fonts completely miss non-Latin scripts.

[sho_hn]

As a recent student of Korean, the state of Hangul typography makes me sad. There are a few quite food typefaces for Hangul, but nowhere near as many as for the Latin script.

Now, Latin's had much longer to develop today's movable type design tradition with gusto (with many typefaces popular today tracing back directly to designs developed before Hangul saw mass real adoption - Hangul was originally developed on metal letterpress, but still heavily informed by Chinese calligraphy), so this isn't necessarily surprising - but I wish it'd tempt more designers to bring their knowledge and experience to bear on the script, given the opportunity to make critical contributions.

[meepmorp]

> I wish it'd tempt more designers to bring their knowledge and experience to bear on the script, given the opportunity to make critical contributions.

I wonder if non-Korean type designers are hesitant to work on Hangul fonts because they're illiterate in Korean. I could imagine that it would be hard to have good intuitions about readability and appearance for a writing scheme one doesn't understand.

[sho_hn]

You need to separate writing systems and language there, though. Unlike the Chinese writing system that it bears superficial resemblance to, Hangul is an alphabet, and it's more purely and consistently phonographic than most writing systems in widespread use. Many of the letter shapes are actually based on things like tongue position and mouth shape when making a particular sound - and there's only roughly as many of them as there are Latin letters. It was specifically designed to be fast and easy to learn, to promote mass literacy. (Both the scientific rigor and the noble motivation that went into it, and the resulting elegance, give it a lot of geeky appeal really.)

So it's actually quite easy to pick up and be able to read it fluently (you can have your first successes within 15 minutes, and have it pretty much down within days). Here, have a comic: http://www.ryanestrada.com/learntoreadkoreanin15minutes/inde...

Actually learning Korean OTOH is another matter entirely, though :) (don't I know it ...).

Anyway, I think even without the ability to understand the words, type designers have experience and knowledge they could usefully apply to the Hangul script. I recently read this nice series by William Berkson on a new revival of Caslon's designs he's been making:

http://ilovetypography.com/2010/11/02/reviving-caslon-part-2...

All that stuff he touches on there - rhythm, visualizations of regularity, avoiding the picket fence effect, etc. - should apply equally to making a good Hangul typeface. Or if not that, then the same sort of thinking and methodology could lead to new truths about what makes a good Hangul typeface.

I think what might actually be keeping designers from it though is the awareness that Hangul design is embedded into a very different typographic lineage, i.e. Chinese calligraphy and such. Their own Latin designs frequently pay homage to the past - reviving Caslon is a good example - and it must be a stark naked feeling to lack the same sort of historical and cultural awareness when trying to navigate Hangul typography. It definitely takes a lot of ego for someone from the West to show up and say they can just make a better Hangul font, I suppose - but I still wish more would be that ballsy.

After all, eyeballs and computer screens work the same everywhere.

[neltnerb]

I mean, yes this is true, but I think the point was that if someone isn't fluent in Korean, and isn't familiar enough with the alphabet, they'll not feel qualified to say if to a native Korean it would look good.

I studied Japanese for many years, and know the two phonographic alphabets quite well, yet I'd still defer to my native Japanese speaking friends when it came to determining if something was legible. I've found that things that are legible to me are sometimes not to them, and vice versa enough that I suspect a font designer with any humility would be quite uncomfortable designing a font with characters they weren't very familiar with.

[DanBC]

But wouldn't being illiterate in Hangul be the most effective "Lorem Ipsum"?

[meepmorp]

Not really.

Have you ever seen type in print that you find difficult to read because some of the characters are so stylized that they're difficult to make out? That'd be my concern as a non-Korean speaking/reading person developing a typeface. I believe that Hangul is an alphabetic system, but that the parts of a character block are somehow grouped according to syllabic units. I'd be very wary of developing a typeface for such a system because I'd be more likely to design a typeface that doesn't present the necessary information in a readable way.

[bane]

There's probably more than you think, but the local market tends to use their own software. There also aren't necessarily lots of "look a-like" analogs to Western fonts.

http://cfile8.uf.tistory.com/image/1140E9385148183C101BC8

For example, the equivalent of maybe a "Time Roman" font for Hangul looks like calligraphy.

http://www.hancom.co.kr/group.eng_main.main.do

http://cfs14.tistory.com/image/21/tistory/2009/10/05/09/29/4...

Try this link to get started https://www.google.com/search?q=%22%ED%95%9C%EA%B8%80+%ED%8F...

[panzi]

OMG, Chrome completely fails to render the characters on that Google result page. http://i.imgur.com/fY8ZhZH.png

[mlkmt]

This makes me wish there was a SCM of sorts for fonts so that collaborating on them would be easier.

[edwintorok]

There is, but it is not clear to me which variant is the "master" font, is it the OTF? https://github.com/mozilla/Fira

[mlkmt]

Nice, but I didn't mean putting the binary files on git. It's not easy to see changes since the file format is not text based.

[edwintorok]

Yeah it'd be nice if they used something like UFO ( http://unifiedfontobject.org/), or even Fontforge's SFD. It should be possible to take each binary OTF, export it with fontforge, and create a "mirror" repository where you can see the changes in a more human-readable format.

[grayclhn]

I like

    \usepackage[osf]{sourcecodepro}

It might be idiosyncratic preferences, but I like the height variation in monospace letters.

You might also want to use

    \DisableLigatures{family = tt*}

from the microtype package. It doesn't normally matter, but the sourcecodepro package has an "fl" ligature that's usually unwelcome.

[edwintorok]

Thanks, I'll use the \DisableLigatures. I actually don't like old-style numbers (see the [lf] option for Fira), but its a matter of personal preference.

[L_Rahman]

I didn't know that Butterick updates the book as new typefaces get released. Given that it's web based, this makes a ton of sense.

[xux]

What page does it recommend that? I skimmed through the typography section and didn't see it.

[spne]

It's at the end of this page, as exceptions to Butterick’s argument that most free fonts are not very good: http://practicaltypography.com/bad-fonts.html