Affinity Publisheur: Index page number separator

[Pyanepsion]

v 2.0.3.1688.

Hello everyone.

The comma separating the referenced page numbers does not respect the usual typographical standard and the referenced sequence is then put on 2 lines instead of one. There should be a space after each comma.

Of course, the bug can be easily worked around by adding a space at the end with a Regex. The index is then no longer compliant.

It would be nice if we could choose the separation sequence ourselves (here comma space), especially as this can sometimes be another separator depending on the point standards.

 

[walt.farrell]

I get spaces, so I'm not sure why you don't.

In fact, that looks like it may be an en-space followed by a thin (fifth) space.

My first thought is that you've made the frame narrow, and you may have some kind of justification going on that is shrinking them visually, and perhaps they've shrunk enough that they aren't visible even though you have Special Characters showing.

[Pyanepsion]

So I haven’t figured out how to put ‘comma space’ between the two numbers. If I do it by hand once the index is done, it makes the index invalid.

[walt.farrell]

I don't have anything for separator.

The Separator is between the term and the first page number. The separators between the page numbers are automatically , + en-space + Fifth-space.

What happens if you make that text frame (with the index) a bit wider?

Can you share a sample document that ends up this way?

[Pyanepsion]

We cannot change either of the two separators (hyphen ‘ — ’ and comma ‘,’), p. 65.

index-separator.afpub

[Pauls]

It is currently fixed - I've added some comments relating to this into an improvement issue

[walt.farrell]

2 hours ago, Pauls said:

It is currently fixed - I've added some comments relating to this into an improvement issue

Thanks.

It's also puzzling, though, why @Pyanepsion is not getting a space after each comma in the index. I've tried the file posted above, and as far as I can see there are indeed no commas, but I cannot see why. I always get a space after each comma in the index. And we're both on Windows.

[MikeTO]

It's odd. It opens without spaces between the references but when I put my cursor in Index > Separator and press Return without making any changes, then the document refreshes with a correctly spaced list of index references. There's also a minor issue of the separator from the previous document appearing in the panel until the new document is loaded. Here's a screen recording.

 

 

[Pyanepsion]

If I refresh the index to version 2.0.3.1670 (betas), I find the En spaces followed by a thin space. If I take this modified version and switch back to version 2.0.3.1688, the spaces disappear again when I refresh the index.

 

[walt.farrell]

10 minutes ago, Pyanepsion said:

If I refresh the index to version 2.0.3.1670 (betas), I find the En spaces followed by a thin space. If I take this modified version and switch back to version 2.0.3.1688, the spaces disappear again when I refresh the index.

 

Did you try Mike's fix, just above your post?

[Pyanepsion]

The reappearance of spaces does not work on my Windows 11 Affinity Publisher v2.0.3.1688.
It works on:
Windows 11 Affinity Publisher v2.0.3.1670 (same computer).
Windows 10 Affinity Publisher v2.0.3.1670.
Windows 10 Affinity Publisher v2.0.0.1640.

[Pyanepsion]

Unfixed bug on Affinity Publisher v2.0.4.1701.

[Pyanepsion]

Unfixed bug on Affinity Publisher v2.1.0.1706.

I may have some news.

• I created a test index on Windows 10 with the beta version v2.1.0.1706. Everything appears correctly.
• I open it on another computer with Windows 11. Everything appears correctly. No error from the preflight.
• I add 3 lines from the index of another file that showed no spaces. Error. Fixing. The spaces are removed.
• I go back to the previous programmer. It wants to put the missing spaces back.

Is there a setting in Affinity Publisher (or a file of preference) where the characters after the comma between two index page numbers are shown?

[Pauls]

I think the spaces are coded into the software do you have the exact same version on both machines ?

[Pyanepsion]

Yes. Affinity Publisher Bêta 2.1.0.1706

Windows 10 Professionnel 64 bits 22H2 build 19045.2604 • Windows feature experience Pack 120.2212.4190.0 • Intel Core i3-2100 CPU @3.10Ghz • Geforce 710 • DirectX 12.0 • Screen 1920×1080 • No Hardware acceleration.

Windows 11 Professionnel 64 bits 22H2 build 22621.1265 • Windows feature Experience Pack 1000.22638.1000.0 • AMD Ryzen 5 1600, Six-Core Processor @ 3.20 GHz • Geforce 1660 GTX Super • DirectX 12.0 Screen 3840×2160 HDR 4K • Hardware acceleration.

[walt.farrell]

6 minutes ago, Pyanepsion said:

Affinity Publisher Bêta 2.1.0.1704

.1706?

[Affinity Info Bot]

The issue "Index panel would benefit from having the ability to add formatting to See entries" (REF: APL-857) has been fixed by the developers in internal build "2.2.0.1925".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.