Jump to content

Affinity Publisher: Comments on the table of contents


Recommended Posts

v2.2.0.1931

Hello to the Affinity team and the community,

When I structure a document with a line break between the chapter number and its title, the generated table of contents shows the number and title pasted in, with no intermediate space.

Ideally, not only should a space be inserted to guarantee better legibility, but you should also be able to write out the sequence to be inserted.

In the meantime, a workaround is to add this space just before the line break when creating the title style.

toc.png.3aa2f2baf1cbe02de3bfd04a5feb8995.png

Thank you for your attention to this malfunction and for your ongoing work.

Best regards,

6 cœurs, 12 processus - Windows 11 pro - 4K - DirectX 12 - Suite universelle Affinity (Affinity  Publisher, Affinity Designer, Affinity Photo).

Mais je vous le demande, peut-on imaginer une police sans sérifs ?

Link to comment
Share on other sites

  • Staff

Hi @Pyanepsion,

I’m not sure I completely follow what the issue is, In 2.1.1 On a brand new document If I create a new paragraph style and then use the standard numbering type, the ‘Text’ content box already has a ‘Current Level’ and ‘Tabtop’ already inserted in, If I wanted to optionally add a line break between my text and number, I could also insert this within the ‘Text’ box at the end like in your example screenshot.

If I then create a TOC using this numbered style as the basis, both the tabstop and line break is present (So long as ‘Remove Line Breaks’ is unticked in the TOC panel) as expected.

Could you perhaps provide a little more detail/screenshots and a sample file which may help better explain what the issue is initially?

Many thanks!

Link to comment
Share on other sites

Hello @NathanC

I'm writing to share with you an example of a table of contents and an accompanying illustrative video. As you'll notice, line breaks are not being converted to spaces.

In this specific instance, we've added a prefix (a number in this case) followed by a line break, all within a style meant for section titles. However, in the table of contents, this added text appears directly adjacent to the section title, without any intervening space. It would be more appropriate if a space were automatically inserted at this juncture.

Moreover, I'd like to propose that users have the option to select the replacement character for converting line breaks, whether it be a particular space or a tab. This would allow for a more polished and professional presentation.

Yours respectfully,

toc-numbering.afpub

6 cœurs, 12 processus - Windows 11 pro - 4K - DirectX 12 - Suite universelle Affinity (Affinity  Publisher, Affinity Designer, Affinity Photo).

Mais je vous le demande, peut-on imaginer une police sans sérifs ?

Link to comment
Share on other sites

15 minutes ago, Pyanepsion said:

In this specific instance, we've added a prefix (a number in this case) followed by a line break, all within a style meant for section titles. However, in the table of contents, this added text appears directly adjacent to the section title, without any intervening space. It would be more appropriate if a space were automatically inserted at this juncture.

In this specific case, you could avoid the problem by adding a space after the number (\#) in the Text Style definition, as I show here:

image.png.fe1d275f506d7c866137a25dfd2e9523.png

In general, though, I would agree that when Publisher removes the line-break, it should probably insert a space. Or allow you to specify what should be inserted.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

@walt.farrell

2 hours ago, walt.farrell said:

In this specific case, you could avoid the problem by adding a space after the number (\#) in the Text Style definition, as I show here:

This is what I explained in the first message and what I show in the video.

Note that the problem persists with version 2.2.0.1954.

6 cœurs, 12 processus - Windows 11 pro - 4K - DirectX 12 - Suite universelle Affinity (Affinity  Publisher, Affinity Designer, Affinity Photo).

Mais je vous le demande, peut-on imaginer une police sans sérifs ?

Link to comment
Share on other sites

3 hours ago, walt.farrell said:

In general, though, I would agree that when Publisher removes the line-break, it should probably insert a space.

This is indeed what happens when you insert manually a line-break in the header (e.g. between two words): line-break WILL BE replaced by a space in the table content, if you tick the ad hoc option. 

But when, as discussed in this topic, a line-break is inserted through the Bullets & numbering paragraph section, line-break is NOT replaced by a space (or whatever) in the TOC. [Edit: The same occurs wether it's with a bullet or a numbered item.]

This is not very coherent… 

 

In other words: if you want to break a header like Hello·world! on two lines and keep a perfect TOC, you should replace the space by a line-break, like this: Helloworld! 
—Not adding it: both Hello·⏎world! or  Hello⏎·world! would give two spaces in the TOC: Hello··world!

But if you want to insert a line-break in a header, you have to add in the Bullet & numbering format text field an extra space to the line-break, for the TOC to look correct with a space between number and header text… 

 

Here, both situations – automatic style defined  line-break after the bullet and manual line-break between words – are illustrated.

First with bad results for each situation:

PNG50-Capturedcran2023-08-1523_36_18.png.09883a48afb3d1dbae50a0a8832619e9.png

PNG50-Capturedcran2023-08-1523_21_05.png.e30a17eb146651c063e4526b2e945023.png

PNG50-Capturedcran2023-08-1523_21_33.png.bb89f6fce79c498de135f43b2055f447.png

 

And for a correct result, we have to set something like this:

CopiedeCapturedcran2023-08-1523_40_20.png.71d1e0b43578778ddc2d3a85073204d6.png

 

CopiedeCapturedcran2023-08-1523_41_13.png.87a00c3c47e34081b2a58d9e0a60e1f7.png

(For clarity of the picture, I used a n-space in the text field but result is equivalent with a space.)

— BTW this bug, or incoherence, is not Windows only. I'm on a Mac.

Affinity Suite 2.5 – Monterey 12.7.5 – MacBookPro 14" 2021 M1 Pro 16Go/1To

I apologise for any approximations in my English. It is not my mother tongue.

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.