MikeTO Posted January 1, 2023 Share Posted January 1, 2023 This is a repeatable issue and has been bugging me for months, I just hadn't written it up yet. Publisher doesn't remove all of a character style's attributes when removing the style or there are some hidden character attributes lurking waiting to cause issues when a style is removed. Create a paragraph with paragraph and character styles applied to a paragraph - in my test doc, I applied Heading 2 (para) and Date (char) Press Return at the end of the paragraph - Heading 2 has Next Style set to Subtitle so the new paragraph is set to Subtitle (para) and Date (char). Good. Change Date (char) to No Style. Now the Text Styles panel shows just Subtitle with no overrides. Good. Type a character of text - now the Text Styles panel shows Subtitle + font weight overrides, and sometimes I get size, too. Here's a test doc and a screen recording. Style Test.afpub Screen Recording 2023-01-01 at 4.12.01 PM.mov Quote Download a free PDF manual for Affinity Publisher 2.5 Download a quick reference chart for Affinity's Special Characters Affinity 2.5 for macOS Sequoia 15.0.1, MacBook Pro 14" (M1 Pro) Link to comment Share on other sites More sharing options...
Old Bruce Posted January 2, 2023 Share Posted January 2, 2023 I think this is because the Paragraph and Character style of [No Change] won't really change the attributes for the text to some sort of neutral set of attributes. If you change the Character style to [No Style] before you hit the return key (when it is at the closing parentheses of the (date)) then the new line has no text overrides inherited from the Date Character style. Quote Mac Pro (Late 2013) Mac OS 12.7.6 Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
MikeTO Posted January 2, 2023 Author Share Posted January 2, 2023 Correct, the bug won't happen with this particular test document if you change to No Style before pressing Return. But this is most definitely a bug. Publisher shows that there are no individual character attributes applied but then applies two attributes on its own when you type a character - an app should never do this. Here's something else you can try with this test document. Press Return after (date), type one character - Subtitle (para) + Date (char) are properly applied. Backspace, change the character style to No Style, and then type the character again - it works properly, no stray individual character attributes are applied. I made this particular test document because it demonstrates the problem so well. Look carefully at the two character attributes that Publisher is mistakenly applying in my original test - Font Weight: Normal and Font Size: 12. Heading 2 was Avenir Next Condensed Demi Bold 10 while Date was Avenir Next Condensed Regular 9. At first glance the Font Weight: Normal looks spurious because there was no Normal to pick up from anywhere but Publisher refers to Regular as Regular in the Font Weight controls and as Normal in the Text Styles summary control so that's just a minor bug. But where did the 12pt come from? There isn't any 12pt text anywhere in my project document where I copied these styles from, and there isn't any 12pt text in this test document. Here's another version of the test document with all of the default styles removed. But more importantly, I redefined Base as 36 and created the text frame as 36, not as 12, so there should be no 12pt control code lurking anywhere in the frame. Style Test 2.afpub But if you repeat the original test with this version of the document, it still applies 12pt after removing No Style. This is frustrating. sfriedberg 1 Quote Download a free PDF manual for Affinity Publisher 2.5 Download a quick reference chart for Affinity's Special Characters Affinity 2.5 for macOS Sequoia 15.0.1, MacBook Pro 14" (M1 Pro) Link to comment Share on other sites More sharing options...
Staff stokerg Posted February 6, 2023 Staff Share Posted February 6, 2023 Hi @MikeTO, Thanks for reporting this. I've just got this logged with the Dev team Quote Link to comment Share on other sites More sharing options...
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.