Edit Text Style section names cut off in list

[garrettm30]

Edit: The problem was already reported here previously.

---------

Here you see part of the Edit Text Style window (for a Paragraph style). Notice that two of the section titles are cut off:

 

This is with the UI Font set to Large, whereas Default does not have this problem. I suggest some better way to handle longer text, which surely effects not only UI Font size but other languages. For a start, it looks like there would actually be plenty of space for the missing words in English at this font size.

By the way, there is a little niggle along the same lines that is not worth making a separate report over, but it just “bugs” me. Why the inconsistency here:

• Color & Decorations
• Position & Transform
• Bullets and Numbering

Edited December 14, 2022 by garrettm30
Linked to prior bug report

[MikeTO]

FYI, somebody else reported the issue with the labels being truncated with the large UI font and it's on Serif's list.

I've also previously reported the "and" vs. "&" issue in this dialog. It bugs me because it's "Position & Transform" here but "Positioning and Transform" in the Character panel, so doubly inconsistent.

[garrettm30]

23 minutes ago, MikeTO said:

FYI, somebody else reported the issue with the labels being truncated with the large UI font and it's on Serif's list.

 

Thanks. I couldn’t find that report when I searched (I even tried visually scanning all post titles in the Publisher 2 Mac bugs, while it is still just a few pages). I tried to search again based on the terminology you used. I clearly overlooked this one, of which my post is but a duplicate:

 

[Sean P]

Hi garretm30,

Thanks for letting us know - I've passed your comments on and bumped the issue with development.

[Grum]

It's now 6 months since this was first reported and it still hasn't been fixed (Publisher/Designer/Photo 2.1.0, MacOS 13.4)

[Affinity Info Bot]

The issue "Bullet and Numbering heading gets truncated using Large Fonts" (REF: AF-144) has been fixed by the developers in internal build "2.3.0.2150".
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.