Back

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

Forum Replies Created

Viewing 15 posts - 1,261 through 1,275 (of 1,338 total)
  • Author
    Posts
  • in reply to: Help with page numbering please! #54529

    Aha. Opinions — with a capital “O”!

    Here's mine: A blank page is professional; a blank page with only a header or footer is not professional (typically, printed Word documents are littered with these).

    A blank page that says “Intentionally left blank” is a logical contradiction which I cannot process. It must be something American — afraid of being sued for having a blank page for no apparent reason at all.

    A left hand side blank page is extremely normal. A right hand side blank page is plain weird, and should be avoided in “a professional book”.

    A blank page is not meant to do anything. It's sole reason of being is to allow the next chapter to start on an odd page again. If you don't want blank pages at all, drop the requirement of starting chapters on odd pages. They are mutually exclusive!

    in reply to: Help with page numbering please! #51508

    Aha. Opinions — with a capital “O”!

    Here's mine: A blank page is professional; a blank page with only a header or footer is not professional (typically, printed Word documents are littered with these).

    A blank page that says “Intentionally left blank” is a logical contradiction which I cannot process. It must be something American — afraid of being sued for having a blank page for no apparent reason at all.

    A left hand side blank page is extremely normal. A right hand side blank page is plain weird, and should be avoided in “a professional book”.

    A blank page is not meant to do anything. It's sole reason of being is to allow the next chapter to start on an odd page again. If you don't want blank pages at all, drop the requirement of starting chapters on odd pages. They are mutually exclusive!

    in reply to: Save As script for archiving #54407

    … all I really need is a macro/action that simply sends the four commands Shift-Cmd-S, Enter, Cmd-R, Cmd-W that I can run over and over until all the windows are closed. I can probably figure out how to do that myself sometime.

    InDesign doesn't support macros and/or actions. And boy! is that high on my wish-list! Exactly for doing stuff like this. Now it needs a script.

    The scripting language does not 'record' actions — it works the other way around, you have to supply the commands that are performed inside ID when you press 'Shift+Cmd+S'. So you would send a 'save as', then a 'close' command to the active window, repeating until no windows are left.

    What happens when you have an untitled document? In the javascript below, I check for that and don't do nuffin' with these.

    list = app.documents.everyItem().getElements();
    while (list.length > 0)
    {
    doc = list.pop();
    if (doc.saved)
    {
    doc.save (doc.fullName,false,undefined,true);
    doc.close();
    }
    }
    in reply to: Save As script for archiving #51382

    … all I really need is a macro/action that simply sends the four commands Shift-Cmd-S, Enter, Cmd-R, Cmd-W that I can run over and over until all the windows are closed. I can probably figure out how to do that myself sometime.

    InDesign doesn't support macros and/or actions. And boy! is that high on my wish-list! Exactly for doing stuff like this. Now it needs a script.

    The scripting language does not 'record' actions — it works the other way around, you have to supply the commands that are performed inside ID when you press 'Shift+Cmd+S'. So you would send a 'save as', then a 'close' command to the active window, repeating until no windows are left.

    What happens when you have an untitled document? In the javascript below, I check for that and don't do nuffin' with these.

    list = app.documents.everyItem().getElements();
    while (list.length > 0)
    {
    	doc = list.pop();
    	if (doc.saved)
    	{
    		doc.save (doc.fullName,false,undefined,true);
    		doc.close();
    	}
    }

    in reply to: A way to change the size of the multi inline graphics #54396

    Ah – a script! Sure, this one ought to do it. Replace the “14” in the 6th line with the size you want, vertically. Then have the text cursor somewhere in the text containing the inline graphics, and double-click the script. It'll rescale all inline graphics to “14” (or whatever you enter) units in the current measurement system.

    With a minor adjustment it can also change the width to a constant value.

    Warning: it'll try to resize all images, but it will fail on non-image stuff (such as inline placed textboxes and line art).


    if (app.selection[0].hasOwnProperty ("baseline"))


    {


    for (g=0; g<app.selection[0].parentStory.allGraphics.length; g++)


    {


    if (app.selection[0].parentStory.allGraphics[g].hasOwnProperty("absoluteHorizontalScale"))


    {


    b = app.selection[0].parentStory.allGraphics[g].parent.geometricBounds;


    scale = 14/(b[2]-b[0]);


    app.selection[0].parentStory.allGraphics[g].parent.absoluteHorizontalScale *= scale;


    app.selection[0].parentStory.allGraphics[g].parent.absoluteVerticalScale *= scale;


    }


    }


    }


    in reply to: A way to change the size of the multi inline graphics #51392

    Ah – a script! Sure, this one ought to do it. Replace the “14” in the 6th line with the size you want, vertically. Then have the text cursor somewhere in the text containing the inline graphics, and double-click the script. It'll rescale all inline graphics to “14” (or whatever you enter) units in the current measurement system.

    With a minor adjustment it can also change the width to a constant value.

    Warning: it'll try to resize all images, but it will fail on non-image stuff (such as inline placed textboxes and line art).

    if (app.selection[0].hasOwnProperty ("baseline"))

    {

    for (g=0; g<app.selection[0].parentStory.allGraphics.length; g++)

    {

    if (app.selection[0].parentStory.allGraphics[g].hasOwnProperty("absoluteHorizontalScale"))

    {

    b = app.selection[0].parentStory.allGraphics[g].parent.geometricBounds;

    scale = 14/(b[2]-b[0]);

    app.selection[0].parentStory.allGraphics[g].parent.absoluteHorizontalScale *= scale;

    app.selection[0].parentStory.allGraphics[g].parent.absoluteVerticalScale *= scale;

    }

    }

    }

    in reply to: paragraph numbering #54362

    You are correct in that you simply cannot have “Restart Numbering” and “Continue Numbering” in one and the same paragraph style. They are mutually exclusive. Eating vs. having cake, I think it's called.

    * the check-box within the paragraph style: 'mode' doesn't give the desired result

    Ah — that's called a drop down list. Yeah, that's where you choose either mode. You can (a) create a new paragraph style, based on the old one, with the sole difference that it restarts the list, or (b) manually select “Restart Numbering” in the paragraph panel menu.

    Hope it helped. (And from the Netherlands as well!)

    in reply to: paragraph numbering #51363

    You are correct in that you simply cannot have “Restart Numbering” and “Continue Numbering” in one and the same paragraph style. They are mutually exclusive. Eating vs. having cake, I think it's called.

    * the check-box within the paragraph style: 'mode' doesn't give the desired result

    Ah — that's called a drop down list. Yeah, that's where you choose either mode. You can (a) create a new paragraph style, based on the old one, with the sole difference that it restarts the list, or (b) manually select “Restart Numbering” in the paragraph panel menu.

    Hope it helped. (And from the Netherlands as well!)

    in reply to: InDesign/Prepress Myths #54344

    Raphael,

    The only reason I'd scan at 1200 dpi would be if I had to enlarge the image considerably (±400%), OR … if I'm going to convert it to a pure black-and-white bitmap [*]. These can be printed at the output resolution — 2400 dpi, if you really really want super quality. 1200 dpi is usually “good enough”. What David said: grayscale and full colour images will be downsampled, for the sole reason there is no point in sending more than 300 dpi to an imagesetter. Even if you force ID to include the full resolution into the PDF, the imagesetter itself will sample only at intervals defined by its halftone interval. (Ignoring any of the RIP oddities David encountered LaughLaugh)

    The black-and-white 'trick' works because these images do not go through the halftone machinery.

    [*] I should probably add that if you see only black-and-white pixels, it's not “by definition” a black-and-white image. It could be anywhere, up to 64 bit RGB plus alpha. Link Info shows what color model it really is.

    in reply to: InDesign/Prepress Myths #50961

    Raphael,

    The only reason I'd scan at 1200 dpi would be if I had to enlarge the image considerably (±400%), OR … if I'm going to convert it to a pure black-and-white bitmap [*]. These can be printed at the output resolution — 2400 dpi, if you really really want super quality. 1200 dpi is usually “good enough”. What David said: grayscale and full colour images will be downsampled, for the sole reason there is no point in sending more than 300 dpi to an imagesetter. Even if you force ID to include the full resolution into the PDF, the imagesetter itself will sample only at intervals defined by its halftone interval. (Ignoring any of the RIP oddities David encountered LaughLaugh)

    The black-and-white 'trick' works because these images do not go through the halftone machinery.

    [*] I should probably add that if you see only black-and-white pixels, it's not “by definition” a black-and-white image. It could be anywhere, up to 64 bit RGB plus alpha. Link Info shows what color model it really is.

    in reply to: Ruling Lines #54329

    Not automatically.

    If you want to try a hack, do this: create a new layer on top of your current one(s). Then put a white rectangle in this layer on your master page, positioned just below your text frame so it will hide the rule if it pops out of the frame.

    This will not work if the paragraph ends with a rule before the end of the text frame …

    in reply to: Ruling Lines #51310

    Not automatically.

    If you want to try a hack, do this: create a new layer on top of your current one(s). Then put a white rectangle in this layer on your master page, positioned just below your text frame so it will hide the rule if it pops out of the frame.

    This will not work if the paragraph ends with a rule before the end of the text frame …

    in reply to: Removing End of Line Underlines #54306

    Ouch! Fortunately, you copied the error message exactly, so I can tell you right away what's wrong. (I hope.)

    Since this forum is brand new, there isn't as yet an option to format code. I gave it a manual try in my first post, underhandedly editing the raw HTML for the message, so the script would show up as plain code. And one of the things that happen automatically is that double quotes do not get translated into the curly ones that show up in text! (Let me show. I type “Hey, Emily, cheer up! Almost there!” with straight quotes in the message editor. You'll see them as curly ones on your screen.)

    As it was a sort of hacking David's otherwise very pretty new forum, and it also was a bit of trouble (and not really worth that either), I plainly copied the new script out of my editor into the message editor. And, well, there's when it went wrong. Both single quotes (which I didn't use) and double quotes in a script need to be of the straight up kind. If you use Adobe's own ESTK to edit the script, you'll see it recognizes the text strings and will change its colour when changed to the correct quotes.

    Let's say I'm fairly confident it ought to work now.

    in reply to: Removing End of Line Underlines #51257

    Ouch! Fortunately, you copied the error message exactly, so I can tell you right away what's wrong. (I hope.)

    Since this forum is brand new, there isn't as yet an option to format code. I gave it a manual try in my first post, underhandedly editing the raw HTML for the message, so the script would show up as plain code. And one of the things that happen automatically is that double quotes do not get translated into the curly ones that show up in text! (Let me show. I type “Hey, Emily, cheer up! Almost there!” with straight quotes in the message editor. You'll see them as curly ones on your screen.)

    As it was a sort of hacking David's otherwise very pretty new forum, and it also was a bit of trouble (and not really worth that either), I plainly copied the new script out of my editor into the message editor. And, well, there's when it went wrong. Both single quotes (which I didn't use) and double quotes in a script need to be of the straight up kind. If you use Adobe's own ESTK to edit the script, you'll see it recognizes the text strings and will change its colour when changed to the correct quotes.

    Let's say I'm fairly confident it ought to work now.

    in reply to: Script for finished artwork #54300

    Can't really think of other ways I'd go about it?

    A custom Preflight (CS4) comes to mind. One-click access to all suspect items.

Viewing 15 posts - 1,261 through 1,275 (of 1,338 total)