If you are going to use in5 to export the file, there is no need to ‘crop the images to the size of the boxes’ or to lower the resolution. in5 take care of all of this for you at export time, automatically.

I recommend leguptools.com

Works well. Pay per page, no up-front cost.

A couple of small free scripts for manipulating layers here that you can assign keyboard shortcuts to: https://github.com/certainlyakey/Indesign-scripts

See also https://corullon.com.br/scripts/?s=layer

If you really want to “encode” an answer in a book, you could use the “Rotate selected characters” script at https://gilbertconsulting.com/scripts which will rotate each character in the selection 180°, making the text really hard to decipher!

Justin,

When thinking about having ID search for a Pstyle in a style group, you should also consider what if it is in a style group within a style group, or nested even further? Here is a function that calls another function that takes care of this. I didn’t write this…I got it from another scripter (probably the very-smart Kris Coppieters years ago). But have used it in many, many scripts and it works great.

// Here is an example of how to call the function
app.changeGrepPreferences.appliedParagraphStyle = app.activeDocument.paragraphStyles.itemByID(locateParagraphStyle(“Table body, cond, center”));

// Function to find a paragraph style possibly contained inside a style group. Return id of the paragraph style.
function locateParagraphStyle(styleNameToLocate, pathSeparator) {
var myDoc = app.activeDocument;
var rootPath = “”;
if (pathSeparator !== undefined) {
rootPath = pathSeparator;
}
var retVal = locateParagraphStyleRecursive(myDoc, styleNameToLocate, pathSeparator, rootPath);
if (! retVal) {
return “not found”;
}
return retVal.id;
}
// Function to find paragraph styles that are in style groups. Returns the paragraph style or null if not found.
function locateParagraphStyleRecursive(paragraphStyleContainer, styleNameToLocate, pathSeparator, parentPath) {
var retVal = null;
do {
try {
var paragraphStyles = paragraphStyleContainer.paragraphStyles;
var numParagraphStyles = paragraphStyles.length;
for (
var paragraphStyleIdx = 0;
retVal == null && paragraphStyleIdx < numParagraphStyles; paragraphStyleIdx++) { var paragraphStyle = paragraphStyles.item(paragraphStyleIdx); if (paragraphStyle.isValid) { var paragraphStyleName = paragraphStyle.name; if (pathSeparator) { paragraphStyleName = parentPath + paragraphStyleName; } if (paragraphStyleName == styleNameToLocate) { retVal = paragraphStyle; } } } if (retVal) { break; } var paragraphStyleGroups = paragraphStyleContainer.paragraphStyleGroups; var numParagraphStyleGroups = paragraphStyleGroups.length; for ( var paragraphStyleGroupIdx = 0; retVal == null && paragraphStyleGroupIdx < numParagraphStyleGroups; paragraphStyleGroupIdx++) { var paragraphStyleGroup = paragraphStyleGroups.item(paragraphStyleGroupIdx); if (paragraphStyleGroup.isValid) { var path = parentPath; if (pathSeparator) { var paragraphStyleGroupName = paragraphStyleGroup.name; path += paragraphStyleGroupName + pathSeparator; } retVal = locateParagraphStyleRecursive(paragraphStyleGroup, styleNameToLocate, pathSeparator, path); } } } catch (err) { } } while (false); return retVal; }

Jarrod, first of all, DON’T try to create links between separate PDF files, instead, put it all in a single PDF if you can. Links between PDF files are problematic depending on how the PDF is distributed and used.

You should be able to use hyperlinks or buttons to do this. If you hyperlink to a text anchor, the anchor will move with the text as the document is updated. If you hyperlink to a specific page, yes, that hyperlink will go to the wrong location if you reorder pages.

Gah! I was afraid that pasting the code in might chew it up! David, where do I insert the tags? I don’t see anything in the interface. Or do I just put the tags in like this?

@Peter, I’m pretty sure that Marcin is referring to the bounding box “handles” of the text frame, not the frame anchor. As you probably know, double-clicking a side handle shrinks the frame to fit the text horizontally, double-clicking a bottom handle shrinks the frame to fit the text vertically, and double-clicking a corner handle does both.

@Marcin, I’ve encountered situations where the FitOptions.FRAME_TO_CONTENT method refuses to work on a frame, even when that frame can be shrunk just fine by double-clicking on the handles. I’ve had to resort to strange work-arounds on occasion.