-
Notifications
You must be signed in to change notification settings - Fork 6
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
tlig em dash ligature is broken #44
Comments
I can not reproduce the difference in behaviour depending on the hyphen but always get a en-dash. Apart from that, the regression was introduced in c98b44c which only updated the fontloader. Also it can be reproduced using the plain fontloader: \input plainfontloader.tex
\font\test={file:texgyreheros-regular.otf:+tlig;mode=node;}\test
dashes-these % gives dash
dashes--these % gives en-dash
dashes---these % gives en-dash
\bye @u-fischer This seems like an upstream bug. I currently do not have a working ConTeXt install to investigate, so I can't tell why ConTeXt isn't affected. Is ConTeXt using |
Ah, good, not our fault ;-). With mode=node I see the problem too. I sent a message to the context list, but I don't want to wait until this is fixed, but will try to upload new version anyway. |
@zauguin it looks as if we should put |
I think the default value of |
@zauguin I agree, \XeTeXdashbreakstate is set in the format, and so the luatex setting should there be too. I'm just discussing it on the team list. |
(moved from dev-luatex)
---
doesn't give an em-dash if there are no spaces around it (but curriously a hyphen before change this).context doesn't have a problem. The problem is still there in the newest branch (v2.9603-...).
It works with texlive2017 (and the same fontloader), which seems to imply some engine change but older cache content could play a role here too.
The text was updated successfully, but these errors were encountered: