Tim Cole
Forum Replies Created
-
Check to see if, for some reason, ID thinks it’s a hyperlink. That’s a situation in which ID might put a visible box around a text string.
-
Liz, what you’ve probably got is a carriage return or a space character at the end of a para that has a larger leading applied than the rest of the para.
If you click to select the entire paragraph, check the leading field on the control palette. If it’s empty, then that means you’ve got mixed leading values in the para. Just reapply your desired leading value, and that should fix it.
Also, you can also modify ID’s prefs so that leading is always applied to the entire paragraph…this will help prevent a variation in the last line.
-
Does this file have transparency? What version of PDF are you saving to? Where do the stroked boxes appear? In print, on screen?
-
Hi Cindy, you might want to check out https://www.foldfactory.com. They’ve got both an online service and a plug-in that enables the creation of correctly constructed templates for folded jobs like you describe.
-
Basically: if I make a pdf via export on Mac at my big fancy printing company, who exactly in the world is not going to be able to view and print that pdf properly?
The short version is that InDesign and Distiller do it the same way. The only issues of which I’m aware are a) CID encoded fonts, and b) a relatively obscure bug in an earlier version of InDesign where a the fonts in a placed PDF file might not make it into a PDF made of the parent document. There could also be issues with corrupt fonts or font conflicts on an OS level, but that’s not an ID or Distiller problem.
CID encoding is used for non-ASCII character sets, and Distiller will use CID as well as ID’s native export, so there’s no difference there. No one using even a relatively recent version of Acrobat or Reader should ever have a problem seeing those fonts.
Problems would occur if you try to hand off a PDF with CID encoded fonts to an old or dodgy system that doesn’t recognize CID encoding…which would be very bad form given that CID has been a part of the PDF spec for years, and years.
There should be no problems going Mac to Windows or vice versa using Acrobat and Reader.
If you (or your IT guy) have problem files that seem to defy what I’ve written above, we’d love to see them.
-
Your IT guy is about as mistaken as someone could be. Creating and EPS and then distilling it creates a much, much less intelligent PDF than what InDesign can do via its own native export function, and is now a rather archaic way of doing things.
InDesign actually uses Acrobat’s own libraries to do its PDF export. Any problems with a PDF exported directly from InDesign will have much more to do with user error than with anything else.
InDesign’s native PDF export enables the PDF to be optimized in a way that dumping out flattened PostScript to EPS does not. You lose many, many things (like color management, editability, etc.) when you produce a PostScript version of the file. Adobe recommends using the native export function and configuring the settings in a manner appropriate to your workflow.
-
There’s not a way to make InDesign autoflow PDF pages…but you can add pages to a doc, and then load an entire, multi-page PDF into your place cursor to drop the PDF pages on your doc pages.
-
Did you create page number text frames using the Current Page Number marker? That character is in the text contextual menu under Insert Special Characters > Markers. Inserting that character gives you automatic page numbering. You can put that marker on a document page or a master page.
-
All you need to do is create a new Section on page 2, and set the starting page number to “1”. To do this cntrl/right click on the page in question in the Pages Panel, and select the Numbering and Section Options command. Creating a new sections enables you to restart page numbering using whatever page number and numbering styles you want.
-
Raymond, check out my InDesign Backchannel blog on https://blogs.adobe.com/indesignchannel/.
CS3 supports Leopard, but there can be issues, especially if you’re on a PPC machine. There’s a problem with Leopard’s Nav Svcs code that can cause crashes on some systems when using dialogs that access the file system. It’s far more common on PPC’s than on Mactel boxes. If you’re shutting down in a dialog box, that’s probably the explanation.
~ Tim Cole