nerd-fonts icon indicating copy to clipboard operation
nerd-fonts copied to clipboard

Incorrect vue icon

Open epszaw opened this issue 4 years ago • 36 comments

🎯 Subject of the issue

Incorrect vue icon rendering. Other icons work fine.

🔧 Your Setup

  • Pragmata Pro Mono Liga Nerd Font.ttf, JetBrains Mono Nerd Font.ttf
  • kitty, gnome
  • Ubuntu 20.04

★ Optional

image

epszaw avatar Sep 03 '20 07:09 epszaw

@ryanoasis, any info here?

epszaw avatar Sep 25 '20 19:09 epszaw

I meet the same problem here, the vue icon just cannot show properly. Are there any solutions?

corporal9736 avatar Dec 03 '21 11:12 corporal9736

do other glyphs show up for you? If so you may have an older Nerd Font. Try from the latest release.

Can you try this from your terminal and provide a screenshot: echo -e "\ufd42".

ryanoasis avatar Dec 15 '21 00:12 ryanoasis

Hello @ryanoasis, I also have this issue. Should I continue in this thread or create new?

Just in case here is information about font and terminal:

Terminal: Termux v0.118.0 (F-Droid version) with Termux:Styling v0.29 (also from F-Droid). Both are at LATEST STABLE versions at the time of writing.

Font: Fira Code Regular Nerd Font Complete.ttf. Latest file at the time of writing in repository, meaning commit df6d602440f06695d3db372b45465632de264cc2 (https://github.com/ryanoasis/nerd-fonts/blob/df6d602440f06695d3db372b45465632de264cc2/patched-fonts/FiraCode/Regular/complete/Fira%20Code%20Regular%20Nerd%20Font%20Complete.ttf)

Here is how it should look: IMG_20220605_160134

And how it looks: Screenshot_2022-06-05-16-02-33-656_com termux

USLTD avatar Jun 05 '22 12:06 USLTD

The font you linked to (great!) does have the glyph:

image

and at least with tilix it does show up:

image

Maybe it is a terminal problem. Or a font problem, because the terminal does believe the meta information embedded into the font:

image

See, VUE is FD42 which is in Arab Presentation Forms A, which the font claims to not include (not highlighted). Which is a lie but most terminals just do not care. Can you see any other of the glyphs in Form A? What about Form B (i.e. FEFF which should be displayed as blank)?

Finii avatar Jun 07 '22 16:06 Finii

Hmm, original reporter's terminals (kitty and gnome-terminal) seem to find the glyph, as does

$ fc-list ':charset=fd42'
/home/fini/.local/share/fonts/Fira Code Regular Nerd Font Complete Mono.ttf: FiraCode Nerd Font Mono:style=Regular

Finii avatar Jun 07 '22 17:06 Finii

This is how it looks when checking with font viewer (UnicodePad). Marked place is where glyph is supposed to be

IMG_20220607_212208

USLTD avatar Jun 07 '22 17:06 USLTD

What's more strange is that when viewing specific glyph (not previewing it on list but holding on it) it shows it correctly

Screenshot_2022-06-07-21-22-12-927_jp ddo hotmist unicodepad

USLTD avatar Jun 07 '22 17:06 USLTD

I tried to copy-pasting it: IMG_20220607_212231 But it shows same invalid glyph (question mark in diamond or whatever it is) as shown on terminal

USLTD avatar Jun 07 '22 17:06 USLTD

FEFF is blank in both viewer and terminal

USLTD avatar Jun 07 '22 17:06 USLTD

Also off topic question but ...

The font you linked to (great!) does have the glyph:

What do you mean by to (great!) ?

USLTD avatar Jun 07 '22 17:06 USLTD

The font you linked to (great!) does have the glyph:

What do you mean by to (great!) ?

That I appreciate people that link to concrete stuff where I can check and not just let me poke around with 100 possible other versions of fonts with the same name :-) Read it as 'Great report, thank you!'

Finii avatar Jun 07 '22 17:06 Finii

Also I am curious about one thing — why do patched fonts overlap with for example arabic glyps? There are tons of free space in Private Area and if I am not wrong there is also second Private Area

USLTD avatar Jun 07 '22 17:06 USLTD

why do patched fonts overlap with for example arabic glyps?

:sob:

Yes, that was a mistake long long ago, that is very hard to fix (because people rely on that codepoints now). Compare https://github.com/ryanoasis/nerd-fonts/discussions/716 (Remap Glyphs) and a lot of Issues :unamused:

Finii avatar Jun 07 '22 17:06 Finii

Regarding this screenshot

image

Interesting that the first 7 missing glyphs are one-slashed-out, while the following are crossed-out. The first 7 should be filled, while the others are indeed empty. Maybe the glyphs could not be rendered for some reason? I had that with other glyphs too, where they show up correct in one renderer but not in another.

Hmm, but the glyph looks trivial:

image

Can the terminal show that HDMI plug FD3F thing?

Edit: Add 'missing'

Finii avatar Jun 07 '22 17:06 Finii

Let's see...

Edit: Yep. IMG_20220607_220128

USLTD avatar Jun 07 '22 18:06 USLTD

I tried on my phone

  • downloaded same file you linked to above
  • show in font viewer
  • Because my keyboard does not allow to enter codepoints, send X ctrl + shift + U F D 4 2 enter X via signal desktop to phone
  • Copy and paste text from signal to font viewer
  • (Ok, that is not the font installed, so probably rendered by font viewer)

signal-2022-06-08-062059

Finii avatar Jun 08 '22 04:06 Finii

Hmm,

Termux doesn't implement own font renderer, it uses an instance of android.graphics.Paint with typeface being set.

https://github.com/termux/termux-styling/issues/105#issuecomment-689523214

Strange. I checked the font in the repo, and it contains the FD42 thing.

Finii avatar Jun 08 '22 06:06 Finii

Well, installed this termux-style thing, and it is the same for all fonts (that I tried): FD3F is visible, FD42 is unknown:

image

Finii avatar Jun 08 '22 06:06 Finii

All those glyphs, FD40 and upward, they are originally only ligatures. FD3F and below are normal glyphs. Not that the ligatures table is filled, but the codepoints are intended to be for ligatures. Maybe the font renderer thinks it smarter then the font data.

Finii avatar Jun 08 '22 06:06 Finii

@lamartire Tried a lot with kitty and I can not reproduce the problem.

See details here: https://github.com/kovidgoyal/kitty/issues/5156

Maybe you can do/show us a fc-list ':charset=fd42' and/or start kitty like this: kitty --debug-font-fallback

Finii avatar Jun 08 '22 09:06 Finii

... and/or start kitty like this: kitty --debug-font-fallback

I don't use kitty or GUI in general (except Termux).

Maybe you can do/show us a fc-list ':charset=fd42' ...

Here is output of fc-list ':charset=fd42':

❯ fc-list ':charset=fd42'
/data/data/com.termux/files/usr/share/fonts/TTF/IosevkaTermNerdFontComplete-Regular.ttf: Iosevka Term,Iosevka Nerd Font:style=Regular
/data/data/com.termux/files/usr/share/fonts/TTF/FiraCodeNerdFontComplete-Regular.ttf: FiraCode Nerd Font Mono:style=Regular

USLTD avatar Jun 08 '22 11:06 USLTD

I don't use kitty or GUI in general (except Termux).

Yes. The question was for @lamartire who uses kitty (original Issue author).

Finii avatar Jun 08 '22 12:06 Finii

All those glyphs, FD40 and upward, they are originally only ligatures. FD3F and below are normal glyphs. Not that the ligatures table is filled, but the codepoints are intended to be for ligatures. Maybe the font renderer thinks it smarter then the font data.

Same here. Also using kitty. Is there any possible workaround already?

willchao612 avatar Aug 10 '22 10:08 willchao612

Also using kitty. Is there any possible workaround already?

Hmm, for me it works with kitty: image

(Bottom windows shows shift-ctrl-f2 settings)

Finii avatar Aug 15 '22 11:08 Finii

Weird. The glyph can show correctly when searched with ctrl + shift + u in kitty, but not with echo -e "\ufd42".

willchao612 avatar Aug 15 '22 12:08 willchao612

My echo is the zsh builtin...

Finii avatar Aug 15 '22 12:08 Finii

I am using zsh too. The problem is that fd40 and upwards cannot show correctly with echo, but with kitty's own unicode searcher it is fine.

willchao612 avatar Aug 15 '22 12:08 willchao612

What system are you using? shift-ctrl-u is the normal linux keyboard thing and has nothing to do with the shell or terminal, in my case. And as you can see, the echo works on my system.

I have kitty 0.21.2 created by Kovid Goyal

$ kitty --debug-font-fallback
[227 14:59:56.397158] Preloaded font faces:
[227 14:59:56.397197] normal face: /home/fini/.local/share/fonts/JetBrains Mono Regular Nerd Font Complete Mono.ttf:0
[227 14:59:56.397213] bold face: /home/fini/.local/share/fonts/JetBrains Mono Regular Nerd Font Complete Mono.ttf:0
[227 14:59:56.397227] italic face: /home/fini/.local/share/fonts/JetBrains Mono Regular Nerd Font Complete Mono.ttf:0
[227 14:59:56.397242] bi face: /home/fini/.local/share/fonts/JetBrains Mono Regular Nerd Font Complete Mono.ttf:0

Check this output while/after running echo in the started kitty.

Hmm, kitty --debug-config seems to be not there anymore?

Here it did work... https://github.com/ryanoasis/nerd-fonts/issues/268#issuecomment-1110870830

Edit: Add link to old kitty issue

Finii avatar Aug 15 '22 13:08 Finii

Thanks for your response. Ubuntu 20.04 is what I am using. Here is the output of kitty --debug-font-fallback.

[227 22:06:31.694397] Preloaded font faces:
[227 22:06:31.694436] normal face: /usr/local/share/fonts/OperatorMono-Medium.otf:0
[227 22:06:31.694451] bold face: /usr/local/share/fonts/OperatorMono-Bold.otf:0
[227 22:06:31.694463] italic face: /usr/local/share/fonts/OperatorMono-MediumItalic.otf:0
[227 22:06:31.694481] bi face: /usr/local/share/fonts/OperatorMono-BoldItalic.otf:0
U+279c bold Face(family=DejaVu Sans Mono, style=Bold, ps_name=DejaVuSansMono-Bold, path=/usr/share/fonts/truetype/dejavu/DejaVuSansMono-Bold.ttf, index=0, is_scalable=True, has_color=False, ascender=1901, descender=-483, height=2384, underline_position=-175, underline_thickness=90, strikethrough_position=530, strikethrough_thickness=102) (new face)

I have kitty 0.25.2 created by Kovid Goyal.

willchao612 avatar Aug 15 '22 14:08 willchao612