Bug 8166 - Space Mono font has inappropriate ligatures
Summary: Space Mono font has inappropriate ligatures
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Other (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.15.0
Assignee: Tobias
URL:
Keywords: prosaic
Depends on:
Blocks:
 
Reported: 2023-06-08 15:38 CEST by Pierre Ossman
Modified: 2023-07-07 12:52 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:
Must: * Font ligatures are disabled for instances of Space Mono in tlwebadm and tlwebaccess * Font ligature behavior is retained for fonts other than Space Mono, in tlwebadm and tlwebaccess


Attachments

Description Pierre Ossman cendio 2023-06-08 15:38:34 CEST
Our chosen monospace font unfortunately has a big functional problem; it has ligatures enabled by default. That means it fails to uphold the principle of all characters having the same width, as sometimes characters will get merged.

The issue has been discussed several times upstream, but without a released fix:

https://github.com/googlefonts/spacemono/pull/2
https://github.com/googlefonts/spacemono/issues/3
https://github.com/googlefonts/spacemono/issues/4

Fortunately, there is a workaround for CSS at least, in that we can disable ligatures using:

> font-variant-ligatures: none;

This needs to be done wherever we use Space Mono.
Comment 2 Tobias cendio 2023-07-03 15:53:30 CEST
Font ligatures have been disabled in places we use Space Mono, in both tlwebadm and tlwebaccess. In tlwebaccess, Space Mono occurs in javascript error dialogs.

Acceptance criteria
Must:
-----------
✅ Font ligatures are disabled for instances of Space Mono in tlwebadm and tlwebaccess

Confirmed for all instances of Space Mono in both web services.

✅ Font ligature behavior is retained for fonts other than Space Mono, in tlwebadm and tlwebaccess

The other two fonts, Mulish and Poppins, don't seem to exhibit any font ligatures.

Resolved.
Comment 3 Alexander Zeijlon cendio 2023-07-07 12:29:17 CEST
I agree with the conclusions in comment 2.

Closing.

Note You need to log in before you can comment on or make changes to this bug.