-
Notifications
You must be signed in to change notification settings - Fork 126
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
Changes to build-toc to address issue #628 #629
Conversation
To clarify, which ones had "unrelated issues"? I know many of those always required manual fixes, but are there some now that have some kinds of issues? |
I’ll spell them all out later today, but one source of difference is just changes in our practice since the book was originally produced, such as using z998:name-title in abbreviation tags.
There’s a couple I want to check my code for, but they don’t seem at all related to the changes I made in the PR. Still, I should have checked that first! I’ll have time later today to do that.
…On 29 Dec 2023 at 3:09 AM +1100, Alex Cabal ***@***.***>, wrote:
To clarify, which ones had "unrelated issues"? I know many of those always required manual fixes, but are there some now that have some kinds of issues?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
To clarify my clarification (!) I have been comparing ToCs created by my new code to the ToCs in the released productions because I wanted to pick up the ones I knew had manual alterations.
…On 29 Dec 2023 at 9:38 AM +1100, ***@***.***, wrote:
I’ll spell them all out later today, but one source of difference is just changes in our practice since the book was originally produced, such as using z998:name-title in abbreviation tags.
There’s a couple I want to check my code for, but they don’t seem at all related to the changes I made in the PR. Still, I should have checked that first! I’ll have time later today to do that.
On 29 Dec 2023 at 3:09 AM +1100, Alex Cabal ***@***.***>, wrote:
> To clarify, which ones had "unrelated issues"? I know many of those always required manual fixes, but are there some now that have some kinds of issues?
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you authored the thread.Message ID: ***@***.***>
|
OK, first point: there are zero differences in the ToCs generated with the old master branch build-toc and those generated with the new code in the fixtoc branch. So I think that's OK to merge. The ToCs in the released versions which differ are as follows:
So, to sum up, I think the changes in the pull request should be applied, but there are several new issues thrown up by my comparison between the released ToCs and what build-toc is generating. But I think these should be the subject of new Issues, which I'll create. |
OK great, thanks. Some of those can't be fixed as the ebooks are exceptions, like Phantastes. If you have time though you can look at the ones that aren't to see if we can get things into shape. |
I've altered where we check for a language tag in build-toc which seems to fix the problem in issue #628.
I've run a comparison between the results of new and old tocs and the only productions which don't match are either ones that always required a manual adjustment to the ToC or a handful of others which have unrelated issues (though some of these mean I should recheck my code in other areas.
For reference, the non-matching ToCs after this change to build-toc are as follows. The line numbers are in the ToC for each production.