In the object browser in the ESTK (or any of the other available object-model overviews) select textFrame. The in textFrame’s properties, look through the list — you’ll see fit at some point. Click it to follow through the properties/arguments of ‘fit’ and eventually you come up with something like this (where

myFrame

is a reference to a text frame):

myFrame.fit (FitOptions.FRAME_TO_CONTENT);

I didn’t know you can fit a frame by clicking twice on an anchor, and it doesn’t work for me. Could you elaborate?

Peter

GREP styles can change form, not substance: they can apply formatting, but can’t change the text itself. You suggested what would seem the most appropriate approach: use a word list to fix case after the change to sentence case. The very rudimentary script below does just that.

To use the script, open the word list that has all words in their correct case (PetSmart, InDesign, NATO, RSPB), each word on a new line. Then open the document that needs to be treated and change its content’s case to sentence case. Make sure that the text and the list are the only two open documents and that the text is the active document. Then run the script.

The script reads the list, then looks in the text for the lower-case instance of each list item, case-insensitive (?i) and whole word only (). Case-insensitive searches are needed because sentence case may have rendered unfindable words at the beginning of sentences, such as Nato and Indesign.

As I said, it’s rudimentary but the basics are there and it can be refined in all kinds of ways.

(function(){
  app.findGrepPreferences = app.changeGrepPreferences = null;
  var list = app.documents[1].pages[0].textFrames[0].parentStory.contents.split('\r');
  for (var i = 0; i < list.length; i++) {
    app.findGrepPreferences.findWhat = '(?i)b' + list[i].toLowerCase() + 'b';
    app.changeGrepPreferences.changeTo = list[i];
    app.documents[0].changeGrep();
  }
}());

Peter

Should be fairly simple, though I haven’t seen your document. Prepare your document as follows: on each master page place a text frame for the page number and name it ‘folio’ (without the quotes) on the Layers panel. Then run this script:

(function () {
  var i, index;
  var frame;
  var n = 1;
  var pages = app.documents[0].pages.everyItem().getElements();
  for (i = pages.length-1; i >= 0; i--) {
    n--;
    if (pages[i].textFrames.item('folio').isValid) {
      pages[i].textFrames.item('folio').remove();
    }
    if (pages[i].appliedMaster !== null) {
      index = pages[i].side === PageSideOptions.LEFT_HAND ? 0 : 1;
      frame = pages[i].appliedMaster.pages[index].textFrames.item('folio');
      if (frame.isValid) {
        frame = frame.duplicate (pages[i]);
        frame.contents = String(n);
      }
    }
  }
}());

When you add and/or delete pages, simply run the script again.

Peter

Delete the script’s configuration file. See the script’s web page for details.

You’re replacing text content, which is dangerous because you may delete index markers, cross-references, etc. etc. And you might make a mess of formatting. It’s safer to let InDesign do the replacements rather than JavaScript. Something like this:

[code]app.documents[0].textPreferences.typographersQuotes = false;
app.findGrepPreferences = app.changeGrepPreferences = null;

app.findGrepPreferences.findWhat = ‘(["’])’;
app.changeGrepPreferences.changeTo = ‘$1’;
imgtext.changeGrep();

app.documents[0].textPreferences.typographersQuotes = true;[/code]

Peter

The string ‘differ’ that you see on screen doesn’t contain any underlying ligature: ‘ff’ is just rendered as a ligature on your screen. You can see that in (at least) two ways: you can place the cursor between the two f’s, and when you select the word, the Info panel reports 6 characters. So I don’t think it’s possible to get the dump you’re after.

The two should prevent finding ‘just’ in ‘adjustment’, etc. matches only at word boundaries.

Probably because in InDesign you enter them in the GREP tab of the Find/Change window, and it’s become a habit to referer to regexes as GREPS.