How the new open-source typeface used by GitHub and Mozilla came to be
1–10 of 38 posts
Re: How the new open-source typeface used by GitHub and Mozilla came to be
#2I realize that not all web fonts support all languages but picking between the best ones and then supporting all the languages seems like a pain.
Re: How the new open-source typeface used by GitHub and Mozilla came to be
#3Re: How the new open-source typeface used by GitHub and Mozilla came to be
#4What's the best way to use web fonts on a site that needs to be internationalized. I realize that not all web fonts support all languages but picking between the best ones and then supporting all the languages seems like a pain.
Re: How the new open-source typeface used by GitHub and Mozilla came to be
#5Is it just me or does Inter look like a clone of Helvetica?
Re: How the new open-source typeface used by GitHub and Mozilla came to be
#6I've seen multiple websites (What The Font being one of them) which analyses a picture with text. They then try to guess the font being used. If you could automate this process, you might be able to scrape content and figure out who's using your typeface. I guess that is mostly interesting for a commercial typeface looking for software piracy, though.
Re: How the new open-source typeface used by GitHub and Mozilla came to be
#7What's the best way to use web fonts on a site that needs to be internationalized. I realize that not all web fonts support all languages but picking between the best ones and then supporting all the languages seems like a pain.
In general, it's hard to break browser fallback to system fonts for languages/glyphs that aren't available. (Though people will sometimes try, or make crazy bad accidents happen.)
But, you mostly only have to worry about languages your webpage is outputting anyway. If you aren't localizing to a particular language and you don't allow user content, you don't have to worry about a web font covering those glyphs. Which is why most web fonts only worry about the top few languages for download speed optimization.
Google Fonts has tools to be smarter about which subsets are downloaded in a browser. It has a subset hint where you can tell it languages you think you will need. Google Fonts also supports the use of the unicode-range CSS feature [0] to tell a browser to download subsets only if the browser encounters characters in the associated Unicode ranges.
Re: How the new open-source typeface used by GitHub and Mozilla came to be
#8Re: How the new open-source typeface used by GitHub and Mozilla came to be
#9Am I the only one that wishes the article about the font "made for screens" went into more detail about what makes this specific font better for screens?
> We'd used Roboto as our main font, and we were running up against its limitations. It was originally built to work as both a display typeface for things like titles and text typeface for longer blocks of text like paragraphs. But it was difficult to read Roboto when it was small
Emphasis mine
Re: How the new open-source typeface used by GitHub and Mozilla came to be
#10Is it just me or does Inter look like a clone of Helvetica?