walt.farrell Posted February 22, 2019 Posted February 22, 2019 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: I did a regular-expression Find and got these results: 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: 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: 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 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4
walt.farrell Posted February 22, 2019 Author Posted February 22, 2019 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 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4
Joachim_L Posted February 22, 2019 Posted February 22, 2019 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
Staff Gabe Posted March 22, 2019 Staff Posted March 22, 2019 Hi both, Sorry for the delayed reply. This seems to be fixed in the latest beta. Thanks, Gabe.
walt.farrell Posted March 22, 2019 Author Posted March 22, 2019 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 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4
walt.farrell Posted March 22, 2019 Author Posted March 22, 2019 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 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4
Recommended Posts