You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set "Cascadia Code SemiLight" as Text Font in the Preferences (General > Appearance > Colors and Fonts: Basic)
Create a Java Project
I tried
Open a Java source file, f.e. Open Type (Ctrl+Shift+T): String - java.lang
I expected: The Bold syntax elements (f.e. keywords) rendered with "Cascadia Code Bold"
But got: The Bold syntax elements appear rendered as "faux bold", and the character spacing is not monospace
If I set "Cascadia Code Regular" as the (normal) Text Font, then bold elements are rendered as expected:
"Cascadia Code Regular" is too bold for my preference and it is harder to distinguish from the Bold variant for me.
Tested under this environment:
OS & version: Windows 10 22H2 19045.4046
Eclipse IDE/Platform version (as shown in Help > About): Eclipse SDK, Version: 2024-06 (4.32), Build id: I20240304-0610
Community
I understand reporting an issue to this OSS project does not mandate anyone to fix it. Other contributors may consider the issue, or not, at their own convenience. The most efficient way to get it fixed is that I fix it myself and contribute it back as a good quality patch to the project.
The text was updated successfully, but these errors were encountered:
I verified I can reproduce this issue against latest Integration Build of Eclipse SDK
eclipse-SDK-I20240304-0610-win32-x86_64.zip
Steps to reproduce
From a fresh installation and clean workspace:
I tried
I expected: The Bold syntax elements (f.e. keywords) rendered with "Cascadia Code Bold"
But got: The Bold syntax elements appear rendered as "faux bold", and the character spacing is not monospace
If I set "Cascadia Code Regular" as the (normal) Text Font, then bold elements are rendered as expected:
"Cascadia Code Regular" is too bold for my preference and it is harder to distinguish from the Bold variant for me.
Tested under this environment:
Community
The text was updated successfully, but these errors were encountered: