Publisher duplicating line on next page

[awmore]

Publisher 2.5.7, Windows 11

Hardware acceleration enabled

A reader discovered a line that's repeated from the bottom of one page to the top of the following page. I corrected it and saved. But each time I reopen it does it again. As far as I can tell, it's the only instance in the book that this is happening. I was able to correct it and export to pdf but when I open it, the line repeats again. 

In the screenshot it's 283-284.

 

[Hangman]

Hi @awmore,

1. Can you show us a screenshot that includes the Flow Options section of the Paragraph panel...
2. What happens when you delete the repeated line on Page 284?

[awmore]

I only need to delete a single letter from the repeated line on 284 for the line on 283 to disappear. I should mention when I open first open the file (screenshot attached), it's fine. After a few seconds the line is added to the bottom of 283.

[Hangman]

1 minute ago, awmore said:

I only need to delete a single letter from the repeated line on 284 for the line on 283 to disappear. I should mention when I open first open the file (screenshot attached), it's fine. After a few seconds the line is added to the bottom of 283.

Can you upload the file so we can take a look at why it's doing this?

[awmore]

I'll DM you.

[MikeTO]

I believe this might be logged as AF-4928. The user in the original report had leading override set and when it was cleared the problem was resolved. That might not have been the issue but it's worth checking leading override.

https://forum.affinity.serif.com/index.php?/search/&tags=AF-4928

[awmore]

2 hours ago, MikeTO said:

I believe this might be logged as AF-4928. The user in the original report had leading override set and when it was cleared the problem was resolved. That might not have been the issue but it's worth checking leading override.

https://forum.affinity.serif.com/index.php?/search/&tags=AF-4928

Changing the leading override didn't affect the duplicated line. But, I'm not sure if changing it to auto was applied to the paragraph. When I selected auto in the characters panel, the history window indicated the leading override was changed (from 14.9) to auto but the character panel still displayed 14.9. 

 

 

[MikeTO]

Note that Leading Override is a character attribute so if you change it without selecting text you are only changing it at the text cursor position. You'd need to select all the text that has this override and make the change. Typically, leading override is used for a single line of text but it's possible it's applied to paragraphs. Ensure it's not defined as on in the paragraph style, too.

Good luck

[awmore]

Mike, I tried changing the leading override for each line, the sentence, and the paragraph but the fix was only temporary. When I reopened the file, the line duplicated. Even though selecting auto removes the duplication, the override doesn't show it's auto. It's still 14.9.

[Old Bruce]

1 hour ago, awmore said:

... the override doesn't show it's auto. It's still 14.9.

Is it showing 14.9 or (14.9)? Without brackets it's showing an override of 14.9 points. With brackets means it is set to no override and is showing the leading as set for the paragraph.

[MikeTO]

That's correct, when you choose Auto, the paragraph leading value will be shown in (). That's okay.

It sounds like you really have encountered AF-4928 which is a known bug. There isn't a workaround other than to fiddle with the text so that it doesn't happen. For example, you could enter a line break and format the next line manually. This is a hack but you should be able to avoid the issue.

Good luck

[awmore]

Yes, it is in brackets. I sent Hangman the file. Hopefully he can figure out what's going on. A manual workaround isn't good enough. At some point after the proofread, the duplicate line was introduced. Books were printed and distributed with the error. At this point it's not uncommon to have a few typos here and there but I'll make those edits within the pdf because I can't trust Affinity won't glitch again. I like using the program. Crossing my fingers the bug will be fixed.

[Hangman]

Hi @awmore,

@MikeTO is right, this is another instance of AF-4928 which is currently logged to be fixed... It is really quite a bizarre bug but hopefully we'll see a quick fix...