ShureTechMono "fi" text overlap.

[Markov-Komarov]

🗹 Requirements

-🗹 I have searched the issues for my issue and found nothing related and/or helpful
-🗹 I have searched the FAQ for help
-🗹 I have searched the Wiki for help

🎯 Subject of the issue

Experienced behavior:

st terminal firefox and pcmanfm-gkt3 show overlapping text when displaying "fi" followed by any letter. Similar to #784

Expected behavior:

writing the word "config" or "find" " displays the word with no overlap between "i" and the following letter.

Example symbols:

no symbol. text "fi"+any letter.

🔧 Your Setup

• Which font are you using ?
  • ShureTechMono Nerd Font
• Where did you get the file from (download link, self patched, source downloaded from link...)
  • pacman (ttf-sharetech-mono-nerd 3.2.1-1 package) Also tried direct download from this repo.
• Which terminal emulator are you using (e.g. iterm2, urxvt, gnome, konsole)?
  • st terminal 0.9.2 patched enough to properly show nerd fonts (confirmed with Terminess and CaskaydiaCove)
• Are you using OS X, Linux or Windows? And which specific version or distribution?
  • Arch Linux 6.8.9

★ Screenshots (Optional)

st with Terminess

st with ShureTech

The issue is resolved in gtk apps setting the font type to propo

unfortunately st even when specifying propo font type it continues to show overlaping text

I would blame it on my poor C knowledge (like missconfiguring st) but when using CaskaydiaCove or Terminess fonts there is no overlapping

[Finii]

Waaah!!! 😱

Sorry to hear this, thanks for reporting. Investigating immediately.

[Finii]

I guess you use the Nerd Font Mono variant?

[Finii]

Fixed it via special rule.

a) Was my impression right that you use the Nerd Font Mono?
b) Would you like fixed version here in a comment or is next release (whenever that will be) soon enough?

[Finii]

@allcontributors please add @Markov-Komarov for bug

[allcontributors]

@Finii

I've put up a pull request to add @Markov-Komarov! 🎉

[Finii]

Ah, I could not see the original error with writer, but scribus could of course show it. Just for future reference if someone wants to reproduce the error/fix.

[Finii]

Fixed via 3043085

[Finii]

Nerd Fonts Patcher v3.2.1-37 (4.14.3) (ff 20230101)
INFO: Adding config commandline options: --removeligatures
DEBUG: Naming mode 1
DEBUG: Monospace check: Panose says "monospaced"; glyph-width-mono True
INFO: Removing ligatures from configfile `Subtables` section
DEBUG: Removing subtable: 'liga' Standard Ligatures lookup 5 subtable
DEBUG: Successfully removed subtable: 'liga' Standard Ligatures lookup 5 subtable
DEBUG: Removing subtable: 'dlig' Discretionary Ligatures lookup 4 subtable
DEBUG: Successfully removed subtable: 'dlig' Discretionary Ligatures lookup 4 subtable
DEBUG: Final font cell dimensions 540 w x 1127 h
Done with Patch Sets, generating font...
DEBUG: Weight approximations: OS2/PS/Name: 400/400/400 (from 400/'Book'/'')
DEBUG: =====> Family (ID 1)      ok       (23 <=31): ShureTechMono Nerd Font
DEBUG: =====> SubFamily (ID 2)   ok       ( 7 <=31): Regular
DEBUG: =====> Fullname (ID 4)    ok       (23 <=63): ShureTechMono Nerd Font
DEBUG: =====> PSN (ID 6)         ok       (15 <=63): ShureTechMonoNF
DEBUG: Tweaking 1/1
DEBUG: Changing flags from 0x1F to 0x17
DEBUG: Changing lowestRecPPEM from 8 to 7
   ShureTechMono Nerd Font
   \===> '/home/fini/extra/git/nerd-fonts/patched-fonts/ShareTechMono/ShureTechMonoNerdFont-Regular.ttf'

As there is no real plan when the next Nerd Fonts release will be, please find the fixed fonts attached:

ShareTechMono.zip 3.4MB

[Finii]

unfortunately st even when specifying propo font type it continues to show overlaping text

The font itself is ok, but that is some kind of compromise that st does on its end. It does allow ligatures but expects them to not-change the character width. That is not true in general, just a lot of terminal fonts do it that way (keep the advance width constant) for various reasons, not the least being that is is hard(er) to work with the classical ligatures.
For that reason Nerd Fonts generally removes the two-letter ligatures because in programming contexts they are almost always unwanted and are just there because 'fonts do have fi ligatures' from a typographer's perspective ;)

[Markov-Komarov]

Thank you so much for the clarification and the fix itself :DD