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

Fix Noto too wide #830

Merged
merged 1 commit into from
Aug 18, 2022
Merged

Fix Noto too wide #830

merged 1 commit into from
Aug 18, 2022

Conversation

Finii
Copy link
Collaborator

@Finii Finii commented May 14, 2022

Description

[why]
The 'monospace' width is determined by examining all the 'normal' glyphs
and taking the widest one.

'Normal' means 0x00-0x17f: the Latin Extended-A range.

Unfortunately Noto has the '1/2', '1/4', '3/4' that are all wider then the
normal (i.e. letter) glyphs.

[how]
Exclude a small sub-range from the 'find the widest glyph' that contain
no glyphs one would call 'letter'.

Requirements / Checklist

What does this Pull Request (PR) do?

Fix Noto * Nerd Font Mono variants.

How should this be manually tested?

Any background context you can provide?

What are the relevant tickets (if any)?

Screenshots (if appropriate or helpful)

[why]
The 'monospace' width is determined by examining all the 'normal' glyphs
and taking the widest one.

'Normal' means 0x00-0x17f: the Latin Extended-A range.

Unfortunately Noto has the '1/2', '1/4', '3/4' that are all wider then the
normal (i.e. letter) glyphs.

[how]
Exclude a small sub-range from the 'find the widest glyph' that contain
no glyphs one would call 'letter'.

Fixes: #610

Signed-off-by: Fini Jastrow <[email protected]>
@Finii
Copy link
Collaborator Author

Finii commented May 14, 2022

Highligthed are the glyphs that are excluded from width-determination with the PR.

image

@Finii Finii added the Bug fix label Aug 18, 2022
@Finii Finii added this to the v2.2.0 milestone Aug 18, 2022
@Finii Finii merged commit fbe07b8 into master Aug 18, 2022
@Finii Finii deleted the bugfix/monospaced-width branch August 18, 2022 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant