-
Notifications
You must be signed in to change notification settings - Fork 43
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
900_gregorio.xml should not use the luainputenc package #1087
Comments
Looking at the file, it appears that the use of However, given the use of Times, I suspect that "reasonable" was originally defined as matching the default font that scribus uses for the rest of the document. If that is the case, and we want to preserve that, then I'm not sure what the best way to go is. As for testing if a package is loaded see here. |
I think the original intent was to translate the things in main-lualatex.tex for use with Scribus. If you recall, the old main-lualatex.tex had these exact settings: On the package testing front, is there equivalent when not using LaTeX? Perhaps we use the "safer" set of special characters if the user is not using LaTeX? |
no inputenc, no fontenc, but fontspec and libertine would be best indeed. I don't think we have to change anything for non-LaTeX users, they usually know what they're doing and can debug easily |
Quashed special characters that emit spurious text under luainputenc. Fixes gregorio-project#1087.
Quashed special characters that emit spurious text under luainputenc. Fixes gregorio-project#1087.
This means removing
\usepackage[utf8]{luainputenc}
, which actually breaks the new gregorio, causing it to emitoe? ae?
above the score. Is there a way to check for this package and not generate the special character commands that cause problems with it, or is there a better way to encode things so that luainputenc doesn't break gregorio?Should we also switch from times to libertine, which would also remove
\usepackage[T1]{fontenc}
?(This bug was reported directly to me by Gerry Davila).
The text was updated successfully, but these errors were encountered: