The slash through the zero isn't consistent in all panes

[n4hnhradio-ai]

I appreciate the option to choose a zero with a slash, so those of us with cataracts can discern the difference between a zero, an 8, or an O. However, I'm only noticing the slash in the pane that shows DE temperature. Those numbers are larger, so they are a little easier to read anyway. But the zero in the DX Cluster and SOTA/POTA panes still have the dot in the middle of the zero.

73, de N4HNH

[accius]

Good catch — thanks for the report.

The reason the slash showed up on the DE temperature pane specifically is that the temperature reading uses Orbitron, which always renders a slashed zero by design. The DX Cluster and SOTA/POTA panes use the user-selectable monospace font (defaults to JetBrains Mono), which ships with a dotted zero by default — even though the font does support a slashed zero via an OpenType feature, it's not on out of the box.

Fixed on Staging in cc92a7f by enabling font-variant-numeric: slashed-zero at the document root, which activates the OpenType zero feature on every font that supports it (JetBrains Mono, Fira Code, IBM Plex Mono, and most modern UI fonts). Fonts without a slashed-zero variant silently ignore it, so there's no risk of regressions elsewhere.

Will ship with the next production release.

73 de K0CJH (and thanks again, N4HNH — exactly the kind of accessibility feedback we want to hear).

[n4hnhradio-ai]

I appreciate what you are doing.  There is a segment in my next YouTube video that shows the OpenHamClock providing a VOACAP analysis.  The video releases this coming Friday.  I appreciate that the VOACAP accuracy has improved.  Today, it showed that I had propagation to a European station. The Inovato HamClock showed no propagation.  OpenHamClock proved to be correct.73,de N4HNHDoug McAlexanderN4HNH Radio on YouTubeOn May 18, 2026, at 10:05 PM, accius ***@***.***> wrote:accius left a comment (accius/openhamclock#994) Good catch — thanks for the report. The reason the slash showed up on the DE temperature pane specifically is that the temperature reading uses Orbitron, which always renders a slashed zero by design. The DX Cluster and SOTA/POTA panes use the user-selectable monospace font (defaults to JetBrains Mono), which ships with a dotted zero by default — even though the font does support a slashed zero via an OpenType feature, it's not on out of the box. Fixed on Staging in cc92a7f by enabling font-variant-numeric: slashed-zero at the document root, which activates the OpenType zero feature on every font that supports it (JetBrains Mono, Fira Code, IBM Plex Mono, and most modern UI fonts). Fonts without a slashed-zero variant silently ignore it, so there's no risk of regressions elsewhere. Will ship with the next production release. 73 de KE0OOJ (and thanks again, N4HNH — exactly the kind of accessibility feedback we want to hear). —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: ***@***.***>

[n4hnhradio-ai]

I’m still noticing inconsistency regarding the slashed zero. I can set it and return only to see dotted zero again. I check settings and it is still set for slashed. I change it to another option and then back to slashed and the slashes return. But the next time I start OpenHamClock, the dotted zeroes are back, even though settings are still configured for slashed. 73, de N4HNH From: accius ***@***.***> Sent: Monday, May 18, 2026 10:06 PM To: accius/openhamclock ***@***.***> Cc: n4hnhradio-ai ***@***.***>; Author ***@***.***> Subject: Re: [accius/openhamclock] The slash through the zero isn't consistent in all panes (Issue #994) <https://avatars.githubusercontent.com/u/22334237?s=20&v=4> accius left a comment (accius/openhamclock#994) <#994 (comment)> Good catch — thanks for the report. The reason the slash showed up on the DE temperature pane specifically is that the temperature reading uses Orbitron, which always renders a slashed zero by design. The DX Cluster and SOTA/POTA panes use the user-selectable monospace font (defaults to JetBrains Mono), which ships with a dotted zero by default — even though the font does support a slashed zero via an OpenType feature, it's not on out of the box. Fixed on Staging in <cc92a7f> cc92a7f by enabling font-variant-numeric: slashed-zero at the document root, which activates the OpenType zero feature on every font that supports it (JetBrains Mono, Fira Code, IBM Plex Mono, and most modern UI fonts). Fonts without a slashed-zero variant silently ignore it, so there's no risk of regressions elsewhere. Will ship with the next production release. 73 de KE0OOJ (and thanks again, N4HNH — exactly the kind of accessibility feedback we want to hear). — Reply to this email directly, view it on GitHub <#994?email_source=notifications&email_token=CBLMADZ5ND4TLTJBH3OXTZL43O6QHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINBYGM4DANZWGQZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4483807643> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/CBLMAD53LR22T2BYIBQA7TD43O6QHAVCNFSM6AAAAACZDS2C22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIOBTHAYDONRUGM> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/CBLMAD4WN6UBVGTB2WW466D43O6QHBFCNFSM6AAAAACZDS2C22WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTYAAAAACC2BPGN2M4TFMFZW63VGMF2XI2DPOI.gif> Message ID: ***@***.*** ***@***.***> >