Forum Replies Created
-
AuthorPosts
-
August 19, 2017 at 7:45 am in reply to: How to use Keep Options for Directory Listing Formatting #96922
Dwayne Harris
MemberFrom looking at your examples, I’d say you want style B to keep with previous lines. In your keep together options, there is an area to say keep with previous.
Also have style C keep with next lines.
What is the “/t”?
Dwayne Harris
MemberNot that I know of. You’re at the mercy of the speed of your computer.
Dwayne Harris
MemberForgot to add: Base master pages on another whenever you can. It saves a lot of time when the publishers decides the trim size has changed and there is no need to change 20 different master pages. And make master pages for everything whenever possible.
Dwayne Harris
MemberThat’s a pretty good list, Justin. Some of those don’t apply to where I work. But they look good. I know that we (and many publishers) don’t use style groups. The main reason is because when we (and they ) import tagged text files. xTags and ID-tagged files aren’t smart enough to search within style group folders, so we keep all style sheets on the main level.
A few things you may be interested in:
1) If a chapter title, head, or runningheads (or anything) has to be in ALL CAPS, make them all caps, and don’t just use the “K” in the palette. We’ve had issues with some fonts where they will appear Upper/Lower Case (and weirdly-spaced) in the eBook. By making them actually all caps, there is no problem.
2) Use the keep together options in the paragraph styles:
a) For body text use 1 for start, and 2 for end.
b) For elements with space above it (i.e., extracts, bulleted lists, numbered lists, etc.) make it 2 and 2
c) For heads (ie., HA, HB, etc.) be sure to select “keep with” and select 2 lines and also change keep with to all lines in the paragraph.3) Set the grid for the leading of the job to be sure everything aligns at top and bottom of the page). Also, if your your job is 14 point leading, and you need a line space above, use 14 points above (not 10 or 12). Absolute leading.
4) Use a nobreak character style whenever you can, instead of using soft returns. Soft returns should only be used as a last resort (i.e., practically never) within text. For heads or the copyright page, it’s acceptable. Be sure to create “nobreak italic” “nobreakbold” as needed.
5) Do not allow hyphenation for chapter titles, heads, part titles, etc. If you have a style you don’t want to hyphenate, make sure to turn off hyphenation.
6) For text hyphenation, in book publishing no more than two hyphens in a row are allowed, and a minimum of 3 character down. I usually set mine 6, 3, 3, 2. Depending upon the client I may allow the last word to hyphenate or not.
7) All art goes on a separate layer (unless it’s anchored—which is self-explanatory so far as anchored art).
8) All elements must use space above or below. No extra hard returns allowed for space above/below (except for spacebreaks—where the hard return for that should be centered).
9) To sink heads at the top of a page, there is no need for a separate master page or manually moving the top of the text box down. Use a one point rule (color none), and select keep in frame. Adjust until it everything aligns properly.
10) Don’t use next column or next page characters/keystroke. The style should indicate what should start a new page or column.
11) Local formatting allowed for kerning/tracking to avoid a bad break. Also allowed for things like fractions. Or to tell a paragraph to start in the next column.
12) Don’t go crazy with style sheets. There is no need for a separate style sheet for the a “prologue” text paragraph and a regular text paragraph. Or an “introduction” text paragraph and a regular text paragraph. No need for an extra half-dozen style sheets that do the same exact thing as the regular text style.
13) Very important—do not manually hyphenate a word and use a soft return to make a line break. In fact—don’t use soft returns at all, unless it’s an emergency (such as in notes sections when you’ve wasted 10 minutes to get the paragraph to break right because of the stupid URL).
That’s my input for now.
Oh—Do a search and replace for any characte/any character/apostrophe/any character and replace with a no break (not the character style). ID still insists on allowing something like er’s to start a line.
Dwayne Harris
MemberThanks. What’s what I thought.
Dwayne Harris
MemberLooks like the art won’t export with the RTF. I think I had to export and file, and then go into the ID file and copy and paste the art to where it had to go.
Dwayne Harris
MemberThis is very odd. I’ve been doing it that way for years, and even copying and pasting an image from InDesign to Word for years and years. Now it’s not working.
I can’t test with CS6 as I don’t have that on my system any longer, but it definitely seems I can’t do it from CC and above (at least on my home machine).
I will check my work machine tomorrow as that’s the machine I’ve always done it on.
Dwayne Harris
MemberYou are welcome.
Dwayne Harris
MemberI believe ID won’t export the images to RTF unless the images are anchored.
If they are not anchored, you will have to copy and paste from the ID file into the RTF file.
Dwayne Harris
MemberAh–they turn into hard returns?
I think you may need to go into the original PageMaker file and delete the forced line breaks there.
What version are the PageMaker files? InDesign CS6 and later is supposed to open and convert PageMarker files simply by opening and the files are converted. I don’t know how well. Maybe no need to copy and paste? I think ID CS6 (and later) can only open PageMaker 6 or 7 files.
https://helpx.adobe.com/indesign/using/converting-quarkxpress-pagemaker-documents.html
Dwayne Harris
MemberSo was it the leading on the return?
August 11, 2017 at 2:44 pm in reply to: Index implies overset text, preflight doesn't find it #96717Dwayne Harris
MemberIs there actual overset text or is it just a question that InDesign asks? (i.e., ID asks just in case there is overset text)
Dwayne Harris
MemberGlad to be of help.
Dwayne Harris
MemberDo you mean how? In the find field, click on the arrow next to the @ sign on the right. Scroll down (2 spots I think) to forced line breaks. Leave the change field blank. Replace all.
The search code for soft returns/forced line breaks is ^n
EDIT: I should mention that the majority of people have a space band before the soft return/forced line breaks. That makes life easier. If that was not done in the original file, you may have to replace the ^n with a space band and then search for two spaces and make into one. Watch out for words that were hyphenated manually and use a forced line break. You may have to search for -^n first and fix them manually to take out the hard hyphen.
Dwayne Harris
MemberI take it the bulleted lists are done via InDesign’s automatic bullets feature?
If so, you need to convert those to text.
To do so, I usually select all the text (hopefully your file is threaded from beginning to end. If not, you may have to select the bulleted lists individually.
Anyway, select all, then go to your paragraph palette (not the paragraph style palette).
Click the fly out menu and scroll down to “Convert Bullets and Numbering to Text.” Then export to RTF.
Basically when you export to RTF, automatic things like bulleted lists and numbered lists don’t export unless they are converted to text.
-
AuthorPosts
