thetasig Posted April 23, 2019 Share Posted April 23, 2019 Looking at the "default" style/formatting for the index entries (inside a text frame) I would like to see the following: 1. Page numbers always starting on the same line as the indexed item. This has the advantage of saving space (extra lines) in the index. 2. Page numbers that wrap around to the second and subsequent lines, should be indented from the indexed item itself. Also helps the viewer to scan for index items easily. Example (ignore empty lines - they are an artifact of this forum's format): P Parts 11, 12, 16, 21, 22 Photo 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 100 Plano 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 200, 201, 202, 203, 204, 250, 251, 300 I could not find a way to do any of this with the existing UI. Are there some specific settings that would accomplish it? Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted April 23, 2019 Share Posted April 23, 2019 For #2, I'm a bit confused, as the continuation lines you show are indented from the indexed term. If you want them indented further, I would suggest looking at the text style Index Entry 1. If you edit that style, in the Paragraph section, you'll see a First Line Indent of .25 inches, and a Left Indent of .25 inches. Increasing the Left Indent should do what you want (but I don't have time to test that right now). afdojo 1 Quote -- 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.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
thetasig Posted April 23, 2019 Author Share Posted April 23, 2019 Walt - thanks for your help. I tried your suggestions. And it worked. Many thanks. Now if Serif will just fix the splitting of single page numbers across two lines, line-leading commas and spaces, then it will be nearly ideal. (Separate bugs have been submitted already.) walt.farrell 1 Quote Link to comment Share on other sites More sharing options...
thetasig Posted September 28, 2019 Author Share Posted September 28, 2019 I am unable to find the "separate bugs" that I originally opened. I'd like to repeat some of the content here. @Pauls originally found the problem. The spaces between the page numbers in the index are automatically generated non-breaking spaces - so they wrap around in very non-standard ways. To get non-breaking spaces, you have to select the index, then show special characters and copy one of the non-breaking spaces. Using find/replace you can replace the non-breaking spaces with a standard "space bar" space. This corrects the non-breaking problem of page numbers in the index. After making those changes, you will always get a warning when you attempt to save or export, print, etc. I would hope that the developers will look at this and decide that a standard space is more desirable in the index creation process. Anyone else agree? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.