←back to thread

Is my vision that bad? No, it's just a bug in Apple's Calculator

(martin.wojtczyk.de)
631 points wojtczyk | 3 comments | 31 Aug 24 04:29 UTC | HN request time: 0.711s | source
Show context
DavidPiper ◴[31 Aug 24 09:25 UTC] No.41407570[source]▶
Comically, I didn't even notice those wobbly numbers in the first screenshot, I was too busy noticing:

- "Unicode" button label way off center

- The 8/10/16 selector being off center in its own position

- The indicators for bits 31 and 63 are not aligned with each other

- x and + not being horizontally aligned (I believe this is an icon-font issue, seen on HN before so knew to look for it)

replies(6): >>41407613 #>>41408138 #>>41408374 #>>41410147 #>>41410322 #>>41418597 #
furyofantares ◴[31 Aug 24 12:25 UTC] No.41408374[source]▶
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.
replies(1): >>41409695 #
1. DavidPiper ◴[31 Aug 24 15:48 UTC] No.41409695[source]▶
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".

replies(1): >>41412225 #
2. IIsi50MHz ◴[31 Aug 24 21:41 UTC] No.41412225[source]▶
> 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.

replies(1): >>41415667 #
3. maskros ◴[01 Sep 24 10:15 UTC] No.41415667[source]▶
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.