The problem seems to be that when you create a document preset by script, createPrimaryTextFrame is always set to true. Create a preset manually and apply it to a document when the document is created it works fine. ... View more

The only way to split a cell/row is to do it manually. Join the crowds at https://indesign.uservoice.com and request this feature. ... View more

> How is your code working when the 1st argument is to be a boolean?    showingWindow and documentPreset are optional parameters. In my code there's just one parameter, withProperties:Object ... View more

> So do you mean to say that once the preset is created we can't change the createPrimaryTextFrame attribute value?   That's the thing with creation properties. You can't change them once they exist. There's a hack to change a primary frame to a non-primary one: type any character in it then remove that character. I'm not aware of a hack to change a frame to a primary one. ... View more

primaryTextFrame is a creation property, you have to do it when you create the document. Something along these lines:   app.documents.add ({ documentPreferences: { createPrimaryTextFrame: true, // Any other properties } }); ... View more

The character class is tested against single characters, which can only be one OR the other. ... View more

Oops! Of course! But in your "|"~S it means 'quotation mark OR quotation mark, followed by ~S', which doesn't make much sense and explains why the closing quote isn't found. Your [~S"]|["] says '~S or quote followed by quote'. Remember that [~S"] and ~S|" are equivalent. ... View more

It would. It's a character class, saying 'a string consisting of digits and/or dots'. ... View more

I don't understand your "|" at all. The expression works, but I've no idea why and how.   To match the number, instead of (\d+.+?) it feels safer to use [\d.]+  Also, you need parentheses for grouping only if you reference the groups. Leaving them out when they're not needed makes the expression more readable. Here's a simpler version of your expression:   "~S[\d.]+ .+?~S"   >  I have a lot to learn.   It's worth all your trouble. There are various web sites with training material. For a comprehensive guide, see https://creativepro.com/now-available-grep-in-indesign-3rd-edition/     ... View more

It's true that an InDesign document can have just one index, but you can get around that. For instance, mark up the index as normal, then mark up the table of cases as a single topic in the index and split it off after generating it. Or prefix all table-of-cases entries with a certain symbol, then extract it after generating it (and remove that symbol). That's in a single document. In a book  (indb) you could use Eugene's suggestion of doing the index and the tables in separate documents.   In this way you can create other tables as well. I've used this method in several legal texts to do tables of cases, authority, and citations, and an index. Using text anchors isn't really an option, much too cumbersome.   InDesign's index is very limited, but you can do a lot with scripting (as Eugene mentioned) so that it becomes even useful. See https://creativepro.com/files/kahrel/indesign/lists_indexes.html and https://creativepro.com/files/kahrel/indesign/index-fixes.html for examples. See also https://www.kerntiff.co.uk/products-4-indesign/indexutilities for various index scripts.   You say that you started using InDesign only recently and don't know (yet) how to script. Your options are to do the job manually -- which, as you said, is very tedious -- or have a script written for you. It's not trivial so be prepared to pay a fee. ... View more

Text anchors are single characters (as you can see in the story editor) underlyingly, their names are enclosed, so to speak, inside them. Text anchors therefore don't apply to a range of text, but to a single character.   So yes, you can have those two text anchors, they'll sit next to each other (probably). ... View more

That code finds blocks of paragraphs using the same style.   To get individual paragraphs add this line: app.findGrepPreferences.findWhat = '^.*'; ... View more

In both code samples you have one variable, instantiated to a window, w1.   w1.ckbx1 is not a variable (global or otherwise), it's a property of window w1. Just like w1.pnl1.ckbx1: pnl1 is a property of window w1, and w1.pnl1.ckbx1 is a property of panel pnl1.   > if I happened to have two different windows named w1   Always a recipe for trouble!     ... View more

I'm afraid you are (misinterpreting). w1.pnl1.ckbx and w1.ckbx are similar in nature, the only difference is that in w1.pnl1.ckbx, ckbx is embedded one level deeper.     ... View more

id-extras do a translator for InDesign: https://www.id-extras.com/products/translate/ ... View more

There is a grep modifier to find matching characters (brackets, quotation marks) but they won't help you here I don't think.So you'd probably need a script for things like "1.1 This is "another" example" ... View more

That can be done in various ways: set some kerning or tracking between the first and second characters, or insert one of the various space characters. And maybe something else.   If you can't figure it out, please post a small sample document. ... View more

They're properties. w = new Window(. . .) creates an object w, and w.ckbx = . . . creates an object as a property ckbx in w.   w1.ckbx and w2.ckbx are two distinct objects. ... View more

https://creativepro.com/files/kahrel/indesign/table_merge.html ... View more

There's no GREP expression to match the end of a line of text in InDesign, only to match the end of a paragraph. You'll need a script for that. That script can undo undo any existing instances of the hiding character style before applying the style (again).   Then select a text frame or click somewhere in the text. The script targets the selected story only.   style = app.activeDocument.characterStyles.item ('nocolor'); story = app.selection[0].parentStory; // Remove any existing instances of the style in the selected story app.findGrepPreferences = app.changeGrepPreferences = null; app.findGrepPreferences.findWhat = ','; app.findGrepPreferences.appliedCharacterStyle = style; app.changeGrepPreferences.appliedCharacterStyle = app.activeDocument.characterStyles[0]; story.changeGrep(); // Apply the style to line-final commas ch = story.lines.everyItem().characters[-2].getElements(); for (i = ch.length-2; i >= 0; i--) { if (ch[i].contents === ',') { ch[i].appliedCharacterStyle = style; } }   ... View more

In that case you use a lookbehind: (?<=~_)   ... View more

There is some documentation on ES > UXP migration, e.g.:   https://developer.adobe.com/indesign/uxp/resources/migration-guides/extendscript/ ... View more

Peter Spier's method has always been the one I used too, but just now it occurred to me that there is another way. Not sure whether it'll always work though.   1. In the chapters, separate the title and the subtitle with a forced line break. 3. In the chapters, insert the character you would use in the TOC as a separator between the title and the subtitle (en- or em-rule, a tab, whatever) at the end of the title. 3. In the chapters, instead of formatting the subtitle with a paragraph style, use a characters style. 4. In the TOC, remove all formatting of the character style used for the subtitle. 5. In the TOC window, check the 'Remove forced Line breaks' box.   Now the generated TOC should be as desired.     ... View more

The problem seems to be that you replace chunks of text while all you want to do ir insert some text.   In your case, you can insert the discr hyphen at the insertion point before the em rule: Find: (?=~_) Change: ~k The Find string is just the lookahead, in other words, the insertion point before what's matched by the lookahead. ... View more

You should look in a frame's parent story, not just the text visible in a frame. So change this: var hits = currentFrame.findGrep() to this: var hits = currentFrame.parentStory.findGrep()  Why do you use JavaScript's regex for the replacements? It's safer to use InDesign's changeTo to avoid problems with formatting going all over the place. ... View more

Thanks for that link, Josh, I didn't know that one (lost my way after Typophile disappeared) and I joined it. Interesting post you had there, I'll reply there later.   P. ... View more