Re:Is my vision that bad? No, it's just a bug in Apple's Cal...
by furyofantares on Saturday August 31, 2024 @08:25AM
(#41408374)
Interesting. I saw the wobbly numbers instantly, but I didn't see any of that, and can't even see the 31/63 issue now.
[ Parent
| on HN ]
Re:Is my vision that bad? No, it's just a bug in Apple's Cal...
by DavidPiper on Saturday August 31, 2024 @11:48AM
(#41409695)
The 31/63 issue for me is that they appear to be aligned differently to the 0s directly above them. The left-edge of the 6 seems to be further left than the left edge of the 3. The 3 in 31 at least looks vertically aligned with the 0 above it.
However, I suspect they both have the same ("Incorrect" seems too harsh a word... "Visually imprecise"?) layout constraints and they look different in practice because "63" is a wider number than "31".
Re:Is my vision that bad? No, it's just a bug in Apple's Cal...
by IIsi50MHz on Saturday August 31, 2024 @05:41PM
(#41412225)
> and they look different in practice because "63" is a wider number than "31".
Gah, I was just noticing this again today, in Finder! No sane font has Roman numerals that are not monospaced.
Re:Is my vision that bad? No, it's just a bug in Apple's Cal...
by maskros on Sunday September 01, 2024 @06:15AM
(#41415667)
Lots of fonts have monospaced numbers, they just need to be enabled! Look for OpenType (TTF and/or OTF) fonts with feature "tnum", and enable it.
For CSS, use font-variant-numeric: tabular-nums.