Jump to content
You must now use your email address to sign in [click for more info] ×

Small \n\r issue with regular expression Find/Replace


Recommended Posts

First, thanks for the regular expression support for Find/Replace. In my first simple tests it has worked well.

However, I noticed a small small anomaly. Here's the text in my document:
image.png.9123713355b844ac6cc3c2816df9d4fb.png

I did a regular-expression Find and got these results:

image.png.3cad9878888f44c75dcb73e30570e32e.png

As it always has in Find results, Publisher shows that paragraph character at the end of the first list of text as \n\r. That gave me the idea to try finding the \n\r, which got this result:
image.png.b586c5df6605d64f545c9774bc658175.png

Seems odd, as the \n\r sequence was supposedly there :)

I can find either \n or \r and I get this result which shows the \n\r as what was found, but I cannot find the pair together:

image.png.3de5a31cbb0f6e8bc50acec59074e92f.png

Of course, I could always search for a Paragraph Break as a special character via the search pulldown, so it's not a big problem, but it's a bit surprising given that Publisher is showing the \n\r which will lead users to naturally try to use that in constructing their regular expression searches.

 

 

 

 

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

Also, I was a bit surprised to find that \n will not match a line-break. One must insert the Line Break character via the pull-down to get a match for it, apparently. That is different from my experiences in other programs that offer regular expression searching.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

These commands you see, seem to be internal. Kind of commands like ##b## for rotating the text. I think you have to insert break, new line etc from the pulldown.

------
Windows 10 | i5-8500 CPU | Intel UHD 630 Graphics | 32 GB RAM | Latest Retail and Beta versions of complete Affinity range installed

Link to comment
Share on other sites

  • 4 weeks later...
1 hour ago, GabrielM said:

This seems to be fixed in the latest beta.

Well, it's certainly different in the latest beta (.270). I'll do some more checking. But I will be reporting two new errors

Thanks for responding, Gabe, which prompted me to look at how it works now.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

Definitely working better. Thanks!

One can do a regex search for either \n or a Paragraph Break, and the results list show it as a Paragraph Break character.

One can do a regex search for a Line Break and it shows up in the results list properly.

 

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

×
×
  • 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.