21–30 of 43 posts
Probably cool, but the website disables zooming in phones so I can't tell. I wish pages couldn't disable zooming -- that should be up to me. Does anyone know browsers that always allow zoomi (If any Jane Street blog folks read this, please fix your blog.)
Could this be an potential avenue for some sort of exploit? I had no idea that you could "execute" logic via fonts.
Is there a way to make the font locale sensitive? Half of the planet uses dots instead of commas
Make what locale sensitive? There are no commas in his font. "I realized that instead of inserting commas, I wanted to underline alternating groups of 3 digits so that the font would work in monospace contexts."
Probably cool, but the website disables zooming in phones so I can't tell. I wish pages couldn't disable zooming -- that should be up to me. Does anyone know browsers that always allow zoomi (If any Jane Street blog folks read this, please fix your blog.)
Huh interesting. Zooming works fine for me on IOS. Maybe it's only blocked on Android. If I remember I'll take a look on Monday.
Earlier quoted context omitted.
Make what locale sensitive? There are no commas in his font. "I realized that instead of inserting commas, I wanted to underline alternating groups of 3 digits so that the font would work in monospace contexts."
The author made multiple variants available, including bolding, grouping via squashing, and commas. There are versions of each type published. https://thume.ca/numderline/
It seems like the only reason you'd need a locale-aware one is on a multi-user system where you'd expect users to have different locales and you're installing the font globally.
But that doesn't really seem like a likely use-case for this pretty niche font that is almost exclusively going to installed on single-user machines by the end-user.
Earlier quoted context omitted.
The author made multiple variants available, including bolding, grouping via squashing, and commas. There are versions of each type published. https://thume.ca/numderline/
If you're downloading and installing a custom font, why do you need it to be locale-aware? Just down the variant that uses whatever your locale needs. (Or if there isn't one, fork it and change the commas to periods and the install that.) It seems like the only reason you'd need a locale-aware one is on a multi-user system where you'd expect users to have different locales and you're installing the font globally. But…
Generally the issue should not be handled at the font level, it lacks sufficient context to make intelligent decisions and can never handle all possible cases. The font should just provide the required glyph variants and means to use them.
Could this be an potential avenue for some sort of exploit? I had no idea that you could "execute" logic via fonts.