-
Notifications
You must be signed in to change notification settings - Fork 4
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
No range version of unicharchart does not work #29
Comments
Not off the top of my head, but it sounds like an ICU or SILE problem more than it does something in fontproof itself. Unless perchance there is invalid data being passed somewhere. |
Noobie, trying similar.
(after multiple similar)
Cheers, Ian |
Definitely a bug in here somewhere. We're getting tripped up at U+0941 or in the 8 thereafter, which should be valid inputs, but flushing them to the word breaker kills SILE. |
An issue opened for 2+ years, about something "probably broken for a while"... Doh, probably no one really cares or uses this feature... Anyway, here is a hint of what might be going on... See: fontproof/classes/fontproof.lua Lines 355 to 357 in f8cf9be
Eventually this code will hit things such as U+D800 (start of high surrogates)... The Yet, ICU doesn't like that standalone U+D800 when it comes to typesetting it... Which indeed seems legit. Proof of concept: Save the following snippet as "poc.lua":
Then run:
As far as I can tell, this likely depends on the font e.g. replacing "Gentium Plus" by "Nimbus Sans" above, then But in brief, just looping from 0 to FFFF and expecting Harfbuzz to report whether a glyph exists is probably a very bogus way. |
When using Font Proof with
\unicharchart[type=all]
or\unicharchart[type="all",columns="12",rows="16"]
an error is generatedThis line looks like it was added two years ago. Using
\unicharchart[type=range, ...]
works. Any idea @alerque ? My group is not usingtype=all
(well, of course not, since it does not seem to work) but might if it works. However, nothing is being blocked so this is a low priority for us. Looks like it has been broken for a while, since the test file for this has thetype=all
test commented out.The text was updated successfully, but these errors were encountered: