[Bug 275758] x11-fonts/noto-basic and x11-fonts/fontconfig together enable ligatures in "monospace" font

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275758

            Bug ID: 275758
           Summary: x11-fonts/noto-basic and x11-fonts/fontconfig together
                    enable ligatures in "monospace" font
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: shurd@FreeBSD.org
                CC: desktop@FreeBSD.org, sunpoet@FreeBSD.org
                CC: desktop@FreeBSD.org, sunpoet@FreeBSD.org

Created attachment 247041
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=247041&action=edit
Local override for monospace

The Noto Sans Mono has ligatures for fi, ffl, and a few others. When used for
monospace text, these ligatures take a single space instead of the expected two
(or three).

The first monospace font listed in /usr/local/etc/fonts/conf.d/60-latin.conf is
Noto Sans Mono.

As a result, if both x11-fonts/noto-basic and x11-fonts/fontconfig are
installed, programs that use fontconfig for monospace (at least by default
irc/hexchat and devel/geany) will combine two characters into a single cell
when a ligature is used.

This is highly distracting, and can mess up alignment.

My ideal solution would be for either x11-fonts/noto-basic to be patched to fix
the ligatures, or x11-fonts/fontconfig be patched to move Noto Sans Mono to the
bottom of the list instead of the top.  It seems unreasonable that if
noto-basic is installed, all programs using monospace need to be configured to
use a different font to actually get monospace behaviour.

Overriding this is not obvious for someone unfamiliar with fontconfig
configuration.  I've attached my /usr/local/etc/fonts/local.conf file where I
moved Noto Sans Mono to the bottom of the list.

-- 
You are receiving this mail because:
You are on the CC list for the bug.