Note: fonts do not need to be included with Windows or Mac to be usable, as long as we can either get a licensed copy for free or use them from somewhere like Google Fonts.

In addition, the days of "support Windows and Mac and ignore the rest" are gone. 3 significant other systems to support are Android, iOs and Chromebooks.

@manassehkatz This post was itself sort of a draft, thanks for reminding me of those systems.

@manassehkatz Android is weird. Apparently, there are only a few fonts installed system-wide: Droid Sans, Droid Serif, and Droid Sans Mono, and Roboto (Android 4+). However, applications (including browsers) can install their own fonts (for their own use, not system-wide). Which means we can't really target Android, since individual browser apps will have a different set of fonts installed.

Which goes back to @ArtOfCode 's idea of getting the fonts (i.e., telling the browser to load them) ourselves.

@manassehktz works fine with me, I'm just concerned about server load since, yn, we'll be serving moe stuff. Might not be too bad though if we @font-face it and make sure to only load fonts used on the page since most questions won't be more than one other language. If we decide to do that for a script, I'll just edit it into the post to let people know.

Sorry for a very basic question. What would go wrong if we simply used Noto Sans as is? I'm just trying to understand where the challenges are.

@JirkaHanika Not everyone has Noto Sans installed.

@Moshi - OK, that makes sense. Thank you.