Forum Replies Created
-
AuthorPosts
-
March 14, 2011 at 11:19 pm in reply to: InDesign CS5 Question: Finding a text in locked text frame #53481
Theunis De Jong
MemberGenerally speaking, it's not wise to open an existing file for editing in a newer version. You just might have to edit more than you think.
With every upgrade cycle, I took care not to do this, and I haven't had any of these problems at all.
(Only time I did get problems was when I got weird results with an existing file template; then again, it turned out that particular original file went all the way back to the original CS. So a simple saving as IDML cleansed that one.)
Theunis De Jong
MemberHey, but you are very close!
All it needs is an “ignoreWrap” command, and that's to be applied to a textFramePreferences, which in turn is a part of a text frame proper. So it's “good” to locate where some text frame gets created, and really “best” when you can find a line that does something with the text frame preferences (*). See the first line you copied!
Add this right after that line:
myTextFrame.textFramePreferences.ignoreWrap = true;and you should be alright.
[*] Why do text frames have separate text frame preferences? Nobody knows — it might be because you can, uh, “store” the text frame preferences into an object style. My personal 2nd best guess is the Adobe engineers didn't like the idea to have more than a hundred properties per each text frame.
Theunis De Jong
MemberHey, but you are very close!
All it needs is an “ignoreWrap” command, and that's to be applied to a textFramePreferences, which in turn is a part of a text frame proper. So it's “good” to locate where some text frame gets created, and really “best” when you can find a line that does something with the text frame preferences (*). See the first line you copied!
Add this right after that line:
myTextFrame.textFramePreferences.ignoreWrap = true;and you should be alright.
[*] Why do text frames have separate text frame preferences? Nobody knows — it might be because you can, uh, “store” the text frame preferences into an object style. My personal 2nd best guess is the Adobe engineers didn't like the idea to have more than a hundred properties per each text frame.
Theunis De Jong
MemberBob, change this line
fr = pg.textFrames.add(reportLayer, {geometricBounds: gb, textFramePreferences: {verticalJustification: VerticalJustification.CENTER_ALIGN}});
(12th from the bottom up) to this
fr = pg.textFrames.add(reportLayer, {geometricBounds: gb, textFramePreferences: {verticalJustification: VerticalJustification.CENTER_ALIGN, ignoreWrap:true}});
— I didn't try, but I'm pretty sure that'd do the trick.
I've never used LabelGraphics so I can't recommend something off the top of me head for that.
Theunis De Jong
MemberBob, change this line
fr = pg.textFrames.add(reportLayer, {geometricBounds: gb, textFramePreferences: {verticalJustification: VerticalJustification.CENTER_ALIGN}});
(12th from the bottom up) to this
fr = pg.textFrames.add(reportLayer, {geometricBounds: gb, textFramePreferences: {verticalJustification: VerticalJustification.CENTER_ALIGN, ignoreWrap:true}});
— I didn't try, but I'm pretty sure that'd do the trick.
I've never used LabelGraphics so I can't recommend something off the top of me head for that.
Theunis De Jong
MemberThis is a simple table after all ;) As in: you should see what I (ab)use tables for! Up to block diagrams and even mathematical equations …
It takes some practice to get what you want, but the basics are pretty much what you see in here: rows and columns, lines, fills, and cells, which may be merged horizontally or vertically.
Theunis De Jong
Member1. Do you see the little blue hash mark at the end of each cell? It's the “End of Story” marker, but dubs for End of Cell.
2. Do you see three of them floating in the space, right next to the cells-that-you-think are actual cells?
3. If you press Cmd+Ctrl+H (the default shortcut for “Show/Hide Frame Edges”), do you get to see thin blue lines, outlining the actual table cells?
If you answer all of the above with “Yes”, you will see that the Table Setup is not lying, and in fact your bizarre table is just what it says: two columns, six rows. The fact that not every cell has a visible border is throwing you off guard here.
So all you have to do to make the second column match the first is:
a. Give every cell a stroke. Check the cells in the left column for its width.
b. Remove the grayish fill of the cells.
You realize that it won't make this right column suddenly have six rows of data, right? These suddenly visible “new” cells will be empty.
Theunis De Jong
MemberIt's a well-known problem (well, for me it is ;) ), but everyone seems to run into it every once in a while. See, for example, this recent Adobe Forum thread: https://forums.adobe.com/thread…..?tstart=30
The problem is not the font itself, but it's in the Document Fonts folder — that's the problem! Install this font into your system, and then rename the Document Fonts folder to something else, so ID won't try to use these fonts.
(Adobe knows all about this issue. There were some rumours one of the CS5 updates fixed things, but I really haven't ever checked up on that. Try updating, nevertheless — you never know.)
Theunis De Jong
MemberNot using InDesign. Zip it and add a password?
Theunis De Jong
MemberThe merged cells appear both in the first row and in the next one. It's kinda hard then, for InDesign, to decide what to repeat. Set your repeating rows to the first two, and you'll be fine. (It's also kind of hard to visualize what you'd expected to see, with merged cells to appear at the top of the next page.)
… Hang on. You are talking about vertically merged cells, are you? 'Cause horizontally merged cells never have been a problem for me, header or no header.
Theunis De Jong
MemberIt really sounds to me lparm is inspecting the type on his screen with a magnifier and is worried about the antialiasing …
Theunis De Jong
Member“Gay” is definitely something else than what you probably meant: “guy” :) (no offense, though).
It's possible to find each specific kind of white space — the regular space, the tab character, the fixed spaces (there are two of them), the hard return and the manual line break, and even every single kind of “fixed width” space (en, em, thin, hair, punctuation, digit … did I forget one?).
InDesign comes with a standard set of GREP queries, and one of them is “Multiple Space to Single Space”. This looks for each of the 'normal' spaces I list above, and replace them with a single regular space. This does not include regular Paragraph Returns and Forced Line Breaks. Is that what you are after?
February 24, 2011 at 2:52 am in reply to: problem creating character style from existing text #58784Theunis De Jong
MemberAre you mixing up paragraph styles with character styles?
A paragraph style sets the global formatting of a paragraph. A character style only changes part of the paragraph style, for example, because you want a single word to be italicized or bolded.
If you don't have any 'special' formatting in your paragraph (at least, not at the point you inserted your cursor), there is no “local change”, and so if you create a new character style based on this you get exactly what you asked for: the difference between the current insertion point and the paragraph style, No Change At All.
Try this: set a single word in one of your paragraphs to bold. Click the cursor into it, then create a new char style. Now it should say “Bold”. (If it doesn't, there is something wrong with your computer, your InDesign, your document, or perhaps your monitor.)
Ah — and there is nothing happening in the background when you create a new style based upon current formatting; in particular, this new style is not going to be magically applied to all instances of that particular formatting! (Or possible only once, if you clicked the checkbox “Apply Style to Selection”.) So, yeah sure, you got a new style; but then you'd have to apply it everywhere where needed.
Theunis De Jong
MemberBTW. These “font discs” weren't anything like this one: https://www.flickr.com/photos/s…..217486415/ (I used those 8″ disks later — they stored about 288K of data). No, they were quite literally “a disc with a font on it”: https://www.flickr.com/photos/s…..217486482/
It worked like this: the imagesetter (physically!) moved the disc closer to or further away from the photographic paper to make the image smaller and larger. (Of course there were upper and lower limits to the font size, also in a quite physical sense.) Then it rotated the disc to the correct character and flashed once or possible multiple times (we could do that to mimick Poor Man's Bold).
It went like “ricketytickety” for several minutes (typically, about 15 min. per would-be page), then rewind and beep for the operator's (me) attention, either to swop disks and re-do for the next font, or declare the job finished and develop and fixate the paper.
Theunis De Jong
MemberGosh — it's just one generation of apparatus before I started. At least I got a proper display and could correct “on-screen”!
My first job in the typesetting dept. was to switch the photographic discs that each contained a single font, i.e.,
1. instruct the Compugraphic to image only Times New Roman
2. insert Times Roman disc
3. run job
4. rewind photographic paper
5. Repeat 1-5 for each of Bold, Italics, Bold Italics, and for any other font.
6. Do Not Make Any Mistake in The Above, or You Have To Start All Over.
It was great fun — nevertheless, Thank you Adobe for InDesign!
-
AuthorPosts
