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
[grammar index] Fix warnings; prefer listing bold page locators. #2013
base: main
Are you sure you want to change the base?
Conversation
Well, we should definitely get latexmk going. Looks like the "latexmkrc" file needs a setting for "makeindex", pointing to xindy instead. And yes, that will be used for all indexes, not just the grammar index. |
I've updated the I'm currently fixing up the index cross-references. xindy treats cross-references as first-class objects and will report an error if you refer to a nonexistent index entry. As a consequence of this, the argument to the There are a few other odds and ends I'm going to check up on, too. I'll post progress updates as I go and will tidy up the git commit history before the final merge. |
I've added a "needs rebase" tag, repurposing it as a general "needs more work" thing. |
d5b55f2
to
2f0e0b5
Compare
e3dbfe2
to
1a21a65
Compare
WORK IN PROGRESS — DO NOT MERGE YET
Fixes issue #1917.
For this PR I used xindy only for the grammar terms index. But we could use it for the other indices as well.
I think latexmk may still use makeindex for all the indices. I don't know if it can be configured to use xindy for just the grammar index or not. (I don't use latexmk much. I'll have to check the docs.)