skyzyx Posted November 19, 2021 Posted November 19, 2021 Currently, the Table of Contents (ToC) are generated literally. That is, whatever is written in the headings on the pages is what ends up in the ToC. I agree that usually, this is the right thing to do. I'm typesetting a book with lots and lots (and lots and lots) of U.S. Case references. The headings in the book are the full case references, but in the ToC, I'm truncating them to just the most essential parts. Here's an example: Heading “United States v. Richardson, 245, No. 1:97-CR-012 (D. Ida, Apr. 23, 2021)” → ToC item “v. Richardson (2021)” Presently, I'm having to make hundreds of these adjustments by hand. In addition to this, I think that being able to generate the ToC (or part of the ToC) by regex would be extremely helpful. Quote
sfriedberg Posted November 19, 2021 Posted November 19, 2021 This is something that should be supported, and it illustrates a basic weakness in the Affinity suite across a whole range of features. What I'm referring to is, first, a general lack of support for user-supplied field contents on various sorts of objects (e.g., captions on picture frames, or TOC/short/summary version of text, as in this particular situation), and second and closely related, the inability to specify which field, attribute or property of a referenced object should be substituted at the point of reference. Ideally, this is something that would be fixed across the whole range of possible references and not just specifically for TOC entries. And by "fixed" I mean "substantial new functionality added in a major feature update". But I am not holding my breath. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.