Jump to content

Running Headers Regression in 2.2.0 (1971)


Recommended Posts

I haven't checked previous 2.2.0 Publisher betas but the latest Publisher Beta 2.2.0 (1971) is having problems displaying Character Styles in Running Headers if that text also happens to be a Paragraph Style with a Drop Cap enabled. There may be other reasons for that of course.

I haven't checked it extensively but the below video shows the problem. I'm switching here between 2.1.1 and the latest beta 2.2.0 (1971).

 

I'm also attaching the doc below.

Bible-refs-2.afpub

2017 27” iMac 4.2 GHz Quad-Core Intel Core i7 • Radeon Pr 580 8GB • 64GB • Ventura 13.6.4.

iPad Pro (10.5-inch) • 256GB • Version 16.4

Link to comment
Share on other sites

Just now, NathanC said:

I've now moved the thread for you to the beta bug section

Ups. thank you.

2017 27” iMac 4.2 GHz Quad-Core Intel Core i7 • Radeon Pr 580 8GB • 64GB • Ventura 13.6.4.

iPad Pro (10.5-inch) • 256GB • Version 16.4

Link to comment
Share on other sites

This caught my attention because I was playing with running headers today and it looked like a weird bug at first. This is unrelated to drop caps, the bug happens if the running header's style is applied to a single character. It doesn't matter whether it's a character or paragraph style, if the text formatted with the style is a single character than the current beta will show blank. Here's a quick recording showing the issue with Heading 1.

The uploaded document shows John :10–:50 instead of John 1:1–1:50. The chapter is missing in both the from and to sections because the chapter style was applied to a single digit. For the from verse it's showing 10 instead of 1 because verses 1-9 are too short given the bug. The 50 is correct in both from and to.

If it was going to take a long time to get this fixed there's a workaround - insert a zero width space after all single-digit chapter and verse numbers and then they'll be two characters and the running header will work. You'd have to do some fancy grep work or that would take forever. I suggest just waiting for the bug to be fixed.

 

 

Link to comment
Share on other sites

8 hours ago, MikeTO said:

For the from verse it's showing 10 instead of 1 because verses 1-9 are too short given the bug.

I wasn't quite sure what you meant by that but weirdly in addition to the one-character bug, removing the space between the Chapter Number and the Verse Number corrects the verse number...

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

@Hangman, I believe you just made it two characters by typing a character where the space was. The bug occurs when a RH is applied with a character style to a single character, or when the first word of the running header is a single character.

Just try it in a fresh document. Create a RH and using heading 1, type a 1 in another frame - it won't appear in the RH. Type 12 and it will appear. Type 1+space+2 and it won't appear.

Most people use paragraph styles for running headers so unless the first word starts with a space they'd never notice this. Seneca's RH setup is quite complex and is a great test case.

Link to comment
Share on other sites

34 minutes ago, MikeTO said:

I believe you just made it two characters by typing a character where the space was.

@MikeTO, except the two text styles are maintained, i.e., when you have a two-digit Chapter Number, this 'rectifies' the one-character bug (see 20-second mark in the screen recording).

When deleting the space between the Chapter Number and the Verse Number, the Verse Number still maintains its Text Style and appears 'after' the colon. If it were making a two-character Chapter Number you'd expect to see the Chapter Number before the colon update to reflect this which it doesn't (see 36-second mark in the screen recording).

44 minutes ago, MikeTO said:

Most people use paragraph styles for running headers

In Seneca's example, you couldn't use paragraph styles for the running headers since multiple running headers are applied so you have to use Character styles to accommodate the different text styles.

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

4 minutes ago, Hangman said:

@MikeTO, except the two text styles are maintained, i.e., when you have a two-digit Chapter Number, this 'rectifies' the one-character bug

That's right. If it's 2 digits then the bug won't happen. That's why in the original document the first verse that is captured is 10 because verses 1-9 are ignored.

Link to comment
Share on other sites

22 hours ago, MikeTO said:

That's right. If it's 2 digits then the bug won't happen. That's why in the original document the first verse that is captured is 10 because verses 1-9 are ignored.

That all makes sense now, I've just realised the logic, i.e., the character styles don't matter...

 

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
Affinity Designer Beta 2.6.0.2861 | Affinity Photo Beta 2.6.0.2861 | Affinity Publisher Beta 2.6.0.2861

MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

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.