thetasig Posted April 24, 2020 Posted April 24, 2020 AFPUB 1.8.4.648, OSX 10.15.3 Catalina Please review this old report - @Pauls had indicated the issue had been logged, but the problem remains in the latest beta version: Text and Index Frames split numbers - have danglers By thetasig, July 9, 2019 in Pre 1.8 Publisher Bugs found on MacOS Thank you.
walt.farrell Posted April 24, 2020 Posted April 24, 2020 Rather than pasting in text from your report, it would be more helpful to paste in the URL. You can copy the URL from your browser's location bar, or using the "share" button that each post has on the upper right and copy the URL from that. Then just paste it in. That way we can find the report without laborious 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.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
thetasig Posted April 24, 2020 Author Posted April 24, 2020 Thanks, Walt. You can teach an old dog like me new tricks 🙂 The link to that July 19 topic is: walt.farrell 1
thetasig Posted April 24, 2020 Author Posted April 24, 2020 I'd like to add to this thread something directly related to the topic. Same beta version and Mac OS X. I've posted three images. The first shows a "breaking hyphen" that is followed on the next line by the range of pages: 133. This should not be happening. Instead the indexing update should insert "non-breaking hyphens". The after image shows the desired result. Considering that the word wrapping should continue to happen as expected (if there was no room for 131-133 a decision is made to break the 133 to the next line but only if using a non-breaking character would move the pair past the right margin). See the third image below for that example of a correctly broken page range (67-69) with a hyphen. The upshot of this bug is three-fold. First, the user must replace the "breaking dash" from the Index update with a standard hyphen (the minus key on a Mac). Then the user has to go back through and replace the en-space with a standard "space bar" space. When all of this is done, the index is proper without dangling or split numbers, and no strange line breaks where they are not needed. An unfortunate result of this is that the Pre-Flight will always report that the Index is not proper and has to be updated. But we know that is not true in this case. Please consider making these changes to AFPUB's indexing update to make publishing life quicker, intuitive, and easier to do. Thank you.
Recommended Posts