I noticed, in my first week here, that the font is lacking Armenian. Today I also noticed it has no support for Vietnamese. Is that, uhm, deliberate?
One thing that might be considered an advantage is, that it is made really hard to mistake, say, a greek Alpha for an A (yes, no Greek either). But is that really the reason?
2
Comments
ẴẵẶặẸẹẺẻẼẽẾếỀềỂểỄễỆệỈỉỊịỌọỎỏỐốỒồỔổỖỗỘộỚớỜờỞởỠỡỢợỤụỦủỨứỪừỬửỮữỰựỲỳỴỵỶỷỸỹ
It limits the conversation. I'd prefer to see a system font so more languages can be supported. Yes, this is an English forum but we're often discussing characters which aren't.
Here's what I see in Edge on Windows 10:
Looks like it's probably the browser's font fallback.
When the site started, custom web fonts were still kind of a novelty and, since the site was created for type designers, it was cool to be able to feature the work of one of our members. If we want to support more languages, a custom webfont starts to make less sense as the file size could get pretty big. It would probably make more sense to use a system font, even if it's aesthetically less ideal.
Personally, I don’t mind the Lucida Grande fallback. But that’s on Mac. Those Windows/Edge Times Roman and Windows/Chrome decomposed Lucida Sans Unicode fallbacks would probably drive me crazy. ;-)
If the forum keeps using an @font-face webfont (whether Alright or something new), it seems to me that you could just specify a single generic fallback of 'sans-serif' afterward, so the user can get their preferred system fallback in these extended Unicode situations, and not cascade through a bunch of potentially weak options.
How is Noto the answer, when the Armenian, among other scripts, is not still incorporated into the main files, instead residing in a separate file? Do we make a custom version?
Btw that's the most hilarious thing about Noto, which was intended as short for "no tofu".