Back

If your email is not recognized and you believe it should be, please contact us.

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • in reply to: Hidden keyboard shortcuts for spell check? #65076
    kidpub
    Member

    Ding! Most recent issue it was. Thanks!

    Perry
    KidPub Press | Bookility

    in reply to: Will IND CS 5.5, version 7.5.2 work in Mountain Lion? #62858
    kidpub
    Member

    7.5.3 works just fine, so I would presume that 7.5.2 does, too.

    Perry

    KidPub Press

    in reply to: Magic Mouse Cause Unbearable Document Scrolling #61117
    kidpub
    Member

    I solved the lightning-scroll problem by installing Better Touch Tool. It's insanely useful if you have a Magic Mouse or Touchpad. Available at https://blog.boastr.net/

    Perry

    in reply to: Jump to page.paragraph #61089
    kidpub
    Member

    One small tweak. I modified the paragraph code so that if no paragraph was input in the dialog (ie 42 rather than 42.6) it jumps to the page, just like Command-J. That way the script can just replace the built-in jump-to-page and I don't have to think about which to use.

    //Get the paragraph in the frame

    //
    if (selectedParagraph != null) {
    if (theFrame.paragraphs.length > selectedParagraph){
    var theParagraph = theFrame.paragraphs[selectedParagraph – 1];
    //Set the condition
    theParagraph.applyConditions([], true);
    theParagraph.applyConditions(highlightCondition);
    }
    else {
    alert(“The page does not have that many paragraphs”);
    return;
    }
    }

    in reply to: Jump to page.paragraph #61084
    kidpub
    Member

    By the way, please feel free to enhance this…it does only simple bounds checking, for example, and doesn't understand the difference between a chapter title and a body paragraph…they are all just paragraphs to this script.

    Perry

    in reply to: Jump to page.paragraph #61083
    kidpub
    Member

    Since no one replied, I reinvented it. :^)

    The motivation for the the script is that we receive review comments from our authors as a list or spreadsheet with page and paragraph references (p12, para4, change this to that) and it save a lot of time to be able to jump directly to that specific page when applying the edits. The paragraph is highlighted to make it easy to find on the page. Thanks to Peter Kahrel for a snippet that creates a new text condition.

    //DESCRIPTION: Jumps to a specified paragraph on a page. The location is specified in a dialog box in the form page.paragraph
    //For example, to jump to the fourth paragraph on page 16, use 16.4
    //The specified paragraph is highligthed using conditional text. Tested in InDesign CS5.5.
    //
    //AUTHOR: Perry Donham, pd@kidpub.com, books.kidpub.com
    //Version: 1.0.0

    main();
    function main(){
    var kAppVersion = parseFloat(app.version);

    //This is the color we'll use (it's light green)
    //
    var highlightColor = [200,255,200];

    //Set up the condition
    //
    var highlightCondition = add_condition(app.documents[0], 'Edits', highlightColor);

    //Display the dialog
    //
    var d=app.dialogs.add({name:”Jump To Page.Paragraph:”});
    //Changed from integerEditBoxes to textEditBoxes

    with (d.dialogColumns.add()) {
    var numberBox = textEditboxes.add({minWidth:60});
    }
    var userInteract = app.scriptPreferences.userInteractionLevel;
    app.scriptPreferences.userInteractionLevel = UserInteractionLevels.INTERACT_WITH_ALL;
    var result = d.show();
    app.scriptPreferences.userInteractionLevel = userInteract;
    if(!result){d.destroy();return}

    //Parse out the paragraph and page numbers using split. The form is page.paragraph
    //
    var pagepara = numberBox.editContents;
    var mySplitResult = pagepara.split('.');
    var selectedParagraph = mySplitResult[1];
    var selectedPage = mySplitResult[0];

    //Jump to the page
    //
    if (app.activeDocument.pages.length > selectedPage) {
    var thePage=app.activeDocument.pages[selectedPage – 1];
    app.activeWindow.activePage=thePage;
    }
    else {
    alert(“The document does not have that many pages”);
    return;
    }

    //Get the text frame on the page
    //
    var theFrame = thePage.textFrames[0]; //should be only one

    //Get the paragraph in the frame
    //
    if (theFrame.paragraphs.length > selectedParagraph) {
    var theParagraph = theFrame.paragraphs[selectedParagraph – 1];
    }
    else {
    alert(“The page does not have that many paragraphs”);
    return;
    }

    //Set the condition
    theParagraph.applyConditions([], true);
    theParagraph.applyConditions(highlightCondition);

    //We'll use conditional text to highlight the paragraph, which is only visible in Normal mode
    //
    app.documents[0].layoutWindows[0].screenMode = ScreenModeOptions.previewOff;

    //Drop the dialog
    //
    d.destroy();

    //This is from Peter Kahrel's 'deviations' script at https://www.kahrel.plus.com
    //
    function add_condition (doc, n, c)
    {
    if (doc.conditions.item (n) == null)
    doc.conditions.add ({
    name: n,
    indicatorColor: c,
    indicatorMethod: ConditionIndicatorMethod.useHighlight});
    return doc.conditions.item (n)
    }
    }

    kidpub
    Member

    In our workflow, once a book is in ID it never goes back to Word; all of our updates and other maintenance are done in ID. If it's just you working on the material, you'll just need to pick which tool you think you are most productive in for writing. Since your project is a manual, page layout is going to be more important than it would be for something like fiction…I'd be tempted to author in ID, especially if you have a lot of graphics to place, callouts, sidebars, and the like. A disadvantage is that you can't just send off a Word file for someeone to edit…they'd need to edit in ID, or, as we sometimes do, annotate a PDF.

    Regarding styles, it almost doesn't matter what the styles are in Word, since you'll be mapping them to styles in ID. During edit we just use the Word styles to tag elements of the text, not caring what the Word file looks like. You also have the option when you import the file into ID to leave the Word styles in place and import them rather than mapping them to ID styles, so if you use logical Word styles such as Chapter Title, Caption, and so on, they would appear as new styles in ID, which you could edit. I think a common error that folks using both Word and ID make is to spend tons of time trying to get the pages to look right in Word…they aren't going to look that way in ID without a lot of effort.

    If you are committed to keeping the Word and ID content in sync, my advice would be to treat the Word file as unformatted but styled source, and do double edits, especially if the layout is complex.

    Perry
    KidPub Press

    kidpub
    Member

    You can save yourself buckets of time by properly formatting your Word file with styles. Heading1 for chapter titles, Heading2 for subtitles, Emphasis for italicized text, and so on. If you find yourself clicking on the font box in Word, choose a style instead. That way when you import your Word file into ID the styles will map to ID styles and you can automate things like starting chapters on right-hand pages. Click Show Import Options on the import dialog to get to the import optionspanel, then click the Customize Style Import / Style Mapping button at the bottom to open the mapping dialog.

    If you don't have any styles in your ID document, you'll see New Paragraph Style or New Character Style listed next to all of the styles that ID found in the Word document. That's fine, ID will create the styles for you, and you can go back and edit them later if you wish.

    In our shop our workflow uses Word for copyedit, then we import to ID for layout, and further proofreading edits are done in ID. There's a standard set of Word styles that we use to tag the Word docs. We publish 200 or so books each year, so process efficiency is high on our list of priorities.

    Perry
    KidPub Press

    in reply to: how to grep ID5 #60745
    kidpub
    Member

    One great thing about grep in ID is that you don't need to know that much about the syntax. You can construct fairly powerful grep matches using just the menu in the grep find/change dialog.

    Perry

    KidPub Press

Viewing 9 posts - 1 through 9 (of 9 total)