Jump to content
You must now use your email address to sign in [click for more info] ×

Affinity Publisher V2: Cannot create character style(s) for initial words in TOC styles - or did I miss something?


Recommended Posts

I guess this is an oversight by Serif:

I have some headlines which use the Numberpile font to have a marker in front of them (which matches the ones used on a map on another page), which looks like this in the text:

image.png.ad48413ead0949246b38a006fbce92e5.png

This is basically an additional "Headline 2" style which uses the "Initial words" option to use the Numberpile font for the initial word (which in this case is just a "B", which matches the number "1" in a circle in that font, the two colour effect - the character in Numberpile as such would just the white circle with a transparent "1" in the middle - was done by using a 0.8pt border for the character, in case somebody needs to do this, too ;-) ). 

image.png.c5100b794a828459bfdd07b035f73975.png

This worked just fine in the text, but in the TOC, it of course shows up as a "B", since the TOC entry uses the same style for the whole line (besides the number, for which there is an additional TOC character style):

image.png.6847b044298ec7461068d5b956206b2e.png

Not a problem, since I can change the "Initial words" option for that TOC style here, too, right?

Well, actually YES, it is a problem, since you cannot create additional character styles when working on TOC styles, the icon is greyed out and not clickable:

image.png.17dde8d13f8af5b3e54efe5da60a5732.png

So the only character styles available to use in TOC styles are the ones for the different TOC numbers for the TOC levels (or styles to list you turned on). As such, those are the only character styles you can use in the "initial word" option of those TOC styles, too.

Right now, I am using a workaround to get my desired result (I simply changed one of the TOC number styles which don't show up in my TOC, because I'm not using the dark section names in this document, to the Numberpile font with the border and then used that character style for the initial words), but this is of course for obvious reasons not ideal:

image.png.54fa04495454c67038faa099fc1cc285.png

Is this a bug/oversight/missing feature, or did I miss something myself here?

 

Link to comment
Share on other sites

I think you missed a step because it worked fine when I tested it. This test doc has a TOC on the top of the page and the headings in the frame below it. The first and last headings are Heading 1 while the numbered ones in-between, as in your example, are Heading 1 Numbered.

I created it the same way you said you did, Heading 1 Numbered has an Initial Word set to a character style.

numbered.afpub

Download a free manual for Publisher 2.4 from this forum - expanded 300-page PDF

My system: Affinity 2.4.2 for macOS Sonoma 14.4.1, MacBook Pro 14" (M1 Pro)

Link to comment
Share on other sites

6 hours ago, MikeTO said:

I think you missed a step because it worked fine when I tested it. This test doc has a TOC on the top of the page and the headings in the frame below it. The first and last headings are Heading 1 while the numbered ones in-between, as in your example, are Heading 1 Numbered.

I created it the same way you said you did, Heading 1 Numbered has an Initial Word set to a character style.

numbered.afpub 23.67 kB · 0 downloads

Hi MikeTO,

Thank you very much for your example (using a unicode character instead of the Numberpile font might come handy for other projects later on), but I think you might have misunderstood the real issue I encountered.

In your example you're using unicode 2460 for the circled one (and I know there is unicode 2776 for the negative circled one, too), but the first problem is that the fonts I use (Alegreya Sans SC for the headline and Merriweather for TOC level 2, which are both free Google fonts I can use to publish my stuff without having to buy a font license to do so) both don't provide those special characters, so AP uses some standard ones from another font, so I have another font showing up in my document (of which I'm not even sure if I can use it commercially without having to buy another license).

And I could exchange the symbols on the map to use these, too, and could even use the same trick to get the white background in the headline in the text itself, as can be seen in this screenshot (right side shows the decoded unicodes, the first one is using the numberpile font for the circled five as in my original post).

image.png.ced62ae94659d5b8c9c48e173f9b7a1d.png

But the real problem with the TOC is the same, even with the circled numbers using unicode - because there is no "add TOC character style" button available, I cannot add the character style needed for the "Initial word" to have two colors and the 0.8pt "border" to fill out the number instead of having it transparent, as can be seen here:

image.png.82d3361019eb3b191329bbe7edbb022c.png

See what I mean? Your solution to use those unicode characters works fine as long as one doesn't need to have the circled number in exactly the same format (two colored) as it is on the map or in the heading itself (the TOC should help people to find the corresponding page easier when looking at that map, so the symbols should be exactly the same).

But it would be the same problem if I had (for some design reasons) headlines which e.g. have the Initial word(s) in bold (Like "Basement: The first room" and "Basement: The second room" - just a simple bad example to make it more clear ;-) ), and this layout should be mirrored in the TOC as well.

As long as you cannot add "TOC character styles" yourself, every TOC entry is uniform, without being able to use Initial Words at all (unless you want them to use the same format as for the number of the same or another TOC level, that is, since the TOC character style for those gets created automatically by AP - which is what I used as a workaround).

Link to comment
Share on other sites

While the add character style button is disabled when you're viewing a TOC, you don't need to add a TOC character style, any character style will do. Just create a character style as you normally would and then edit your equivalent of "TOC 1: Heading 1 Numbered" and choose that character style as shown in this screenshot.

image.png.a62adf49308ef77951253fb9ce4a3f84.png

Download a free manual for Publisher 2.4 from this forum - expanded 300-page PDF

My system: Affinity 2.4.2 for macOS Sonoma 14.4.1, MacBook Pro 14" (M1 Pro)

Link to comment
Share on other sites

Strange, in my Version, all other defined character styles don't show up when I edit the headline style (please note there is no scroll bar, so it's not that I forgot to scroll):

image.png.2c67feffc1135e643ef3b45cb78956d2.png

And I have a lot of character styles defined in non TOC edit mode:

image.png.e001c4ace52a776aac5f997161d23003.png

Any idea what I might be doing differently? 🤔🤨

 

Link to comment
Share on other sites

As far as I can see, the only Character Text Styles that exist within a TOC are the ones defined by TOC processing for the Number, and the bult-in Emphasis, Strong, and Strong Emphasis. I'm not sure how you got Numbered to show up in your screenshot, @MikeTO.

But I did get it to work with this procedure:

  1. Create a heading style that you ultimately won't use. I called mine Unused.
  2. Actually create a heading somewhere in the document using that text style.
  3. Create or Update your TOC, and specify Unused as one of the text styles to include.
  4. At that point, the Unused style should appear as a choice. Choose it.
  5. Update the TOC again.
  6. At that point, TOC1 Unused and TOC1 Unused Number should appear in the TOC text styles within the Text Styles panel.
  7. Edit TOC1 Unused Number to have the initial word style you want.
  8. Edit the other heading style (that you want to use Initial Words with). You should find that TOC1 Unused Number is available in the Initial Words style list. Select it.
  9. You should now have the TOC1 Unused Number text style applied in the TOC.
  10. Back in the TOC panel, uncheck Unused in the list of included text styles. You can also delete the line of text you added in step 2.

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

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

1 hour ago, walt.farrell said:

As far as I can see, the only Character Text Styles that exist within a TOC are the ones defined by TOC processing for the Number, and the bult-in Emphasis, Strong, and Strong Emphasis. I'm not sure how you got Numbered to show up in your screenshot, @MikeTO.

All character styles in the document are in the Initial Word style list when editing a TOC text style. I didn't have to do anything. I tried it again with a blank doc just now.

Download a free manual for Publisher 2.4 from this forum - expanded 300-page PDF

My system: Affinity 2.4.2 for macOS Sonoma 14.4.1, MacBook Pro 14" (M1 Pro)

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.