Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backtick '`' doesn't behave correctly with 'Red Hat Mono' font #165453

Closed
N-Onorato opened this issue Nov 4, 2022 · 3 comments
Closed

Backtick '`' doesn't behave correctly with 'Red Hat Mono' font #165453

N-Onorato opened this issue Nov 4, 2022 · 3 comments
Assignees
Labels
font-rendering Font rendering issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@N-Onorato
Copy link

Type: Bug

To Reproduce

  1. Install Red Hat Mono font
  2. Set VSCode to use 'Red Hat Mono'
  3. Type some text using a backtick such as example text
  4. Observe the first backtick of 'example text' merge with the e as a ligature even if they are disabled.

Expected

Other editors using this font keep the backtick seperate and visible. However on MacOS the ending backtick becomes invisible which is another issue.

VS Code version: Code - Insiders 1.74.0-insider (e8eb39b, 2022-11-03T18:43:35.409Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes

System Info
Item Value
CPUs Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 1498)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Load (avg) undefined
Memory (System) 15.60GB (4.77GB free)
Process Argv --crash-reporter-id 7211467c-3902-4862-a136-5932f43e29fb
Screen Reader no
VM 0%
Extensions: none
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805cf:30301675
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30404738
cppdebug:30492333
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
pylantcb52:30590116
vsccc:30564266
pyindex848:30577858
nodejswelcome1:30587009
gswce1:30602633
34cci188:30599831
iaj6b796:30602301
pyind779cf:30600160

@alexdima alexdima added the font-rendering Font rendering issues label Nov 14, 2022
@alexdima
Copy link
Member

VS Code is built with Electron, which is built with Chromium. The font rendering in the editor is delegated to Chromium, so the font lookup is unfortunately not directly under control. If you are able to reproduce this problem in a Chromium-based browser such as Edge or Chrome, then please report the issue directly against Chromium at https://bugs.chromium.org/p/chromium/issues/list

You can try with opening a page like the following in Chrome: https://jsfiddle.net/rjuk3tvy/

@alexdima alexdima added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Nov 14, 2022
@N-Onorato
Copy link
Author

Thank you @alexdima that makes sense. The behavior can be replicated on Chromium and Firefox browsers, so this might be a font feature I'm unaware of. I will dig into it a bit more and report the issue to chromium if needed.

@N-Onorato
Copy link
Author

For posterity, this was an issue from the font-end of things and has been addressed. However, Google and other sources of the font don't seem to have been updated. RedHatOfficial/RedHatFont#43

@github-actions github-actions bot locked and limited conversation to collaborators Dec 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
font-rendering Font rendering issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants