If you're using absolute leading (not auto), then you could make the subheads 36 pts or 2 pts (iow any measure you want) and it shouldn't affect your baseline alignments at all.

Triple-click the subhead to make sure you include the ending carriage return in the selection, and then look at your leading field. There should be one number in there. If it's blank, or if it has a number in parentheses (meaning autoleading), that's the problem.

If leading is not the problem, then it might help to post a screen shot or something, and link to that screenshot here.

AM

Did you try rebuilding preferences?

Sure … you can do it completely manually, or you can save some time if you have CS4 by using the Move Pages command. Create starting INDD files first w/the right page dimensions, one per chapter, and open them. Then select a chapter's worth of pages you want to move in the Pages panel and have Move Pages move them “At Start of Document” to the appropriate chapter doc. Rinse and repeat for each chapter.

Make sure though that your text frames are completely self-contained within each chapter before you move them. There are some scripts that can help you with that if that's not the case.

AM

Sure … you can do it completely manually, or you can save some time if you have CS4 by using the Move Pages command. Create starting INDD files first w/the right page dimensions, one per chapter, and open them. Then select a chapter's worth of pages you want to move in the Pages panel and have Move Pages move them “At Start of Document” to the appropriate chapter doc. Rinse and repeat for each chapter.

Make sure though that your text frames are completely self-contained within each chapter before you move them.  There are some scripts that can help you with that if that's not the case.

AM

“(awakes) wot, wot? a script?” LOL

Just have to say that I really appreciate how the two of you are always right on the case helping users with the thorniest problems. Other users help out a lot too of course (don't mean to dis anyone) but this post is typical. I mean, a user posts an impossible issue at 3:57 a.m., Eugene posts solution at 4:06 a.m., and Jongware (only because he was sleeping) posts a custom solution at 9:05 a.m.

;-)

Personally I don't see it as that big a deal … I just press Command-F enough times until I see the dang thing. ;-)

“there should be shortcuts to 'text' 'grep' 'glyph' and 'object search'.”

When Find/Change is in focus, Command-1, Command-2, Command-3 etc. will jump you around the panes.

Also in addition to the “Load Selected as Find” blah blah commands that Hank brought up, there are a bunch of them for GREP searches too, in the same section of Keyboard Shortcuts.

hope this helps a bit

AM

Jong and David, I'm fairly certain that Raphael is NOT talking about placing/printing a 1200 ppi scan for final output! He specifically said he'd *scan* it at 1200 ppi. That would make it much easier to clean up/sharpen fine text in Photoshop. Then from that point he could convert to whatever format/rez is suitable.

Raphael also said:

As far as how low the resolution can go really depends on the image in question, what size it's going to actually print at (a physically small image isn't going to make much of a difference), the kind of paper being used etc.

This is important too, and a great point. If you've got an architectural image with lots of sharp diagonals and high contrast colors, it'd be better to err toward the high end of the res range (go with 280 rather than 220 ppi, for instance). And if it's going to print on glossy stock at a large size and be the focal point of the spread, then ramp it up to 300.

But if you've got a small head shot, or a medium landscape, 220 ppi is going to serve just as well as 300 on the same kind of paper.

AM