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

2.301 OTF: right backtick (U+0060) higher than left backtick #567

Open
Firestar-Reimu opened this issue Oct 11, 2022 · 7 comments
Open

2.301 OTF: right backtick (U+0060) higher than left backtick #567

Firestar-Reimu opened this issue Oct 11, 2022 · 7 comments

Comments

@Firestar-Reimu
Copy link

Firestar-Reimu commented Oct 11, 2022

Screenshot_20221012_002942

right ` higher than left `

This O can be changed to any capital English letters

I use OTF v2.301 and tried on and off ligatures, do not work.

2.242 JB Mono NL is fine

@Firestar-Reimu Firestar-Reimu changed the title 2.301 OTF O right higher than left 2.301 OTF: right higher than left Nov 7, 2022
@Firestar-Reimu Firestar-Reimu changed the title 2.301 OTF: right higher than left 2.301 OTF: right \ higher than left \ Nov 7, 2022
@Firestar-Reimu Firestar-Reimu changed the title 2.301 OTF: right \ higher than left \ 2.301 OTF: right backtick (U+0060) higher than left backtick Nov 7, 2022
@Firestar-Reimu
Copy link
Author

Firestar-Reimu commented Nov 28, 2022

2.302 the same.

Only the NL version is good.

@atauzki
Copy link

atauzki commented Dec 22, 2022

and it still can be reproduced in v2.303, and ttf version.
image

@Firestar-Reimu
Copy link
Author

@philippnurullin seems like a ligature issue

@philippnurullin
Copy link
Member

This issue is introduced by script that changes the mark from a default version (grave in this particular case) to special for capital letters version - grave.case.
This is needed when the symbol is combined with the mark and exact letter.

For now, I don't see a more elegant solution as to remove the grave from that rule. I believe it's the only symbol creating problems when working with code.

@Firestar-Reimu
Copy link
Author

Yes, I think one rule is enough

@stlee42
Copy link

stlee42 commented Jul 25, 2023

This bug no longer exists in v2.304 "Fixed the backquotes placement #411"

@3olkin
Copy link

3olkin commented Mar 5, 2024

still be reproducible in v2.304. Main problem is single capitalised letters. Also, NL version doesn't have this bug.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants