-
Notifications
You must be signed in to change notification settings - Fork 120
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
Font does not work in XeTeX #21
Comments
Hello, Thanks for your report! Cheers, Eric |
I didn't filed a big yet just searched throughout mailing lists and forums. They say it's a limitation, because TeX interprets the period like the start of the font extension, thus it's not expected to find versions, as they usually have periods, in the font name. |
I would like to add there is no reason to include version number as a part of the font’s name. Almost nobody does that, and for a good reason. Version is indicated in the font metadata anyway. @bleemayer:
You might want to know Junicode supports all kinds of ligatures and OpenType features (see this specimen) and IMHO it looks great. |
You're right @rwmpelstilzchen! Thanks for the suggestion, will be taking a look at it. |
Did you take a look at it? |
Great work, gorgeous fonts, and specially, thanks for including the long s glyph, its ligatures and ct and st ligatures, no one ever did so. But one problem: Including especial characters or numbers on the font name makes it not work in XeTeX, so could you remove it please? It will be great to see "Open Baskerville" only on the font name. Thanks.
The text was updated successfully, but these errors were encountered: