PBREAK in Find and Replace

[MikeTO]

This is trivial, but the page break control code is inconsistent with the other breaks. We only see this in Find and Replace but any searching for a heading 1 or 2 in a complex book that uses breaks will reveal this.

[stokerg]

Hi @MikeTO,

Couple of things, Does this also apply to the Release build?  Just from my understanding, the Scope drop-down for Find and Replace is only in the beta of Publisher.   If you could also give me some more information on 'Page break control code' as its not something I've had experience of dealing with and has a couple of us in Tech Support wondering what it is.  It would also help greatly if you could attach the afpub file you are using, so I can try replicating this again, as so far I've failed but i suspect I'm missing a step somewhere  

 

[walt.farrell]

45 minutes ago, stokerg said:

If you could also give me some more information on 'Page break control code' as its not something I've had experience of dealing with and has a couple of us in Tech Support wondering what it is

Probably Text > Insert > Breaks > Page Break would give you one. But given what Mike showed, he's probably using the Flow options in the Text Styles for headings, which give you the options for starting on the next page, next odd page, next even page, etc.

[MikeTO]

2 hours ago, stokerg said:

Couple of things, Does this also apply to the Release build?  Just from my understanding, the Scope drop-down for Find and Replace is only in the beta of Publisher.   If you could also give me some more information on 'Page break control code' as its not something I've had experience of dealing with and has a couple of us in Tech Support wondering what it is.  It would also help greatly if you could attach the afpub file you are using, so I can try replicating this again, as so far I've failed but i suspect I'm missing a step somewhere  

Sorry, I should have been more clear. Yes, this is also in the release build, I just took the screenshot from the beta.

You may have another term for this but I used control codes because that's what I'm used to. It's just what is when in search results for fields and some special characters that aren't easily shown as plain text. If I search for text that is preceded by a break then the break control code appears in the results, just like it would for a special character like non-breaking space <NBSP>.

All of the breaks were spelled out except for paragraph break which is <PBREAK>. This is so incredibly minor, I just thought it wasn't consistent.

Here's a 2.1.1 test document that shows this, just search for Heading 1. Probably more important than paragraph break which at least shows something is that Zero Width Non Joiner is the only item in the Insert menu that doesn't show anything in the search results. It would be great if that could show <ZWNJ> for consistency.

fields.afpub

[walt.farrell]

Here's another sample document, @stokerg, from 2.1.1, and a somewhat related set of possible bugs.

1. Using a regular expression search, the . regular expression term will not match line breaks or page breaks unless the regular expression option ". matches paragraph break" is turned on. As line and page breaks are not paragraph breaks, they should not be affected by that option.

With the option turned on:

With it turned off:

2. When using Text > Insert > Breaks > Column Break, if there is only a single column in the text frame, the insertion point is put outside the frame, instead of in the next frame. Please see page 1, and where the second "b" ended up.  Sorry; user error there, as explained below by @Hangman.

breaks.afpub

Edited August 29, 2023 by walt.farrell
User error on #2.

[Hangman]

1 hour ago, walt.farrell said:

iI there is only a single column in the text frame, the insertion point is put outside the frame, instead of in the next frame. Please see page 1, and where the second "b" ended up.

Is that not to be expected when the frame on page 1 isn't linked to the frame on page 2?

[MikeTO]

3 hours ago, walt.farrell said:

As line and page breaks are not paragraph breaks, they should not be affected by that option.

I don't know whether or not they should be affected, but in Publisher all breaks are actually paragraph breaks. This is different than MS Word were a break does not terminate the paragraph.

In Word, setting the text before the break to Heading 1 changes the text after the break to Heading 1. In Publisher, it has no effect because a break also ends the paragraph. I prefer the way Publisher does it.

[walt.farrell]

2 hours ago, Hangman said:

Is that not to be expected when the frame on page 1 isn't linked to the frame on page 2?

Thanks. I thought I had them linked, but clearly was wrong.

[stokerg]

18 hours ago, MikeTO said:

You may have another term for this but I used control codes because that's what I'm used to. It's just what is when in search results for fields and some special characters that aren't easily shown as plain text. If I search for text that is preceded by a break then the break control code appears in the results, just like it would for a special character like non-breaking space <NBSP>.

 

Thanks for that Mike, I've just always called them breaks, so wanted to make sure I wasn't missing something  

I've replicated the issue and i'm just getting this logged with the Developers.  I'll get one logged for the Zero Width Non Joiner as well