Skip to content
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

Footnote Check Results #608

Open
okrick opened this issue Dec 26, 2024 · 7 comments
Open

Footnote Check Results #608

okrick opened this issue Dec 26, 2024 · 7 comments
Labels
future feature New feature or request, but not core

Comments

@okrick
Copy link

okrick commented Dec 26, 2024

See Anchor and See Footnote buttons would be helpful.

@srjfoo
Copy link
Member

srjfoo commented Dec 27, 2024

What would you expect from such buttons? Is this something that would be for locating the footnotes and anchors after the footnotes have been moved to the landing zones, and cleanup has been done?

I ask because in testing, before I do the cleanup following moving footnotes to landing zones, they're available in the footnote fixup list, and pretty easy to tell which is footnote and which is anchor.

@windymilla
Copy link
Collaborator

Is this something that would be for locating the footnotes and anchors after the footnotes have been moved to the landing zones, and cleanup has been done?

It's not possible in GG1 or GG2 to "see anchor" or "see footnote" once LZ movement and cleanup has been done.

@windymilla
Copy link
Collaborator

See Anchor and See Footnote buttons would be helpful.

Thanks Rick - as you know, the footnote fixup box is already very busy, and in my opinion the GG1 equivalent is far too busy, not obvious, and intimidating for new PPers.
I'd like to leave this request on hold for a little while to give you a chance to get used to the new footnote fixup layout. If you still think these buttons are required after that, or if there is a specific circumstance that you think justifies adding them, please comment again so we can look at the best way forward.

@windymilla windymilla added the future feature New feature or request, but not core label Dec 27, 2024
@okrick
Copy link
Author

okrick commented Dec 27, 2024

When I selected the option to move footnotes (FNs) to the end of paragraphs in previous versions of [software name, likely Google Docs or a similar word processor], I encountered an issue. The FNs would sometimes not move to the end of the paragraph but instead remain just above the page break for paragraphs that spanned across pages.

Was this issue resolved in [software name] version 2 (GG2)? Specifically, does the fix ensure that FNs are correctly placed at the end of the paragraph, even when the paragraph continues after an intervening illustration page?

If this issue was resolved in GG2, I'm happy to wait until I have a project where I can test this functionality.

@windymilla
Copy link
Collaborator

Quentin put a lot of work into making the FNs go to the correct place, particularly around page breaks. He noted "Unlike GG1 it correctly handles 'mid-paragraph' footnotes; that is, footnotes at the bottom of the page that are anchored in the paragraph above which continues on to the following page(s)."
That sounds similar to what you're describing, but of course, it will be interesting to hear the results of testing it in one of your projects.

@srjfoo
Copy link
Member

srjfoo commented Dec 27, 2024

Correct me if I'm wrong, but until you use the "Tidy Footnotes" button, the Footnote Fixup dialog will display the list of anchors and footnotes.

In my testing, I've always gone through using the list after moving the footnotes. It's very easy to tell when the placement is following paragraphs, because most paragraphs are short enough to see both the anchor(s) and the footnotes following the paragraph, if not on one page, then at least in very quick succession. I highly recommend scrolling through the list one last time before tidying the footnotes into their final form.

@windymilla
Copy link
Collaborator

I think that's accurate, yes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future feature New feature or request, but not core
Projects
None yet
Development

No branches or pull requests

3 participants