Forum Replies Created
-
AuthorPosts
-
Theunis De Jong
MemberSo converting variables to text yields the name of the variable?
Ah — I needed this today. Fortunately, I remembered it wrong, and it does what you'd think!
Still a small consolation. Adobe should buy PowerHeaders!
MemberSo converting variables to text yields the name of the variable?
Ah — I needed this today. Fortunately, I remembered it wrong, and it does what you'd think!
Still a small consolation. Adobe should buy PowerHeaders!
MemberYou can override the text frame (I'm assuming it's on a master page now), but if you convert to text, you'll not get what you'd expect (the text that's shown now), but rather the name of the variable. Not quite useful, eh?
Local formatting in variable text is an option I sorely miss as well. Only one work-around, really: make a new master page (or spread) for that chapter only. It's not worth the trouble of overriding the header frame on each of your spreads, as that surely will bite you back some day.
MemberSelect the entire table by clicking the top left corner (the cursor will change to a fat bottom right pointing arrow). Then you can remove all strokes by changing their color to [None], and — safest — also setting the stroke width to 0 pt.
It's 'safer' to do both, because even with a 0 pt stroke width InDesign will think the color is still in use.
MemberYou can override the text frame (I'm assuming it's on a master page now), but if you convert to text, you'll not get what you'd expect (the text that's shown now), but rather the name of the variable. Not quite useful, eh?
Local formatting in variable text is an option I sorely miss as well. Only one work-around, really: make a new master page (or spread) for that chapter only. It's not worth the trouble of overriding the header frame on each of your spreads, as that surely will bite you back some day.
MemberSelect the entire table by clicking the top left corner (the cursor will change to a fat bottom right pointing arrow). Then you can remove all strokes by changing their color to [None], and — safest — also setting the stroke width to 0 pt.
It's 'safer' to do both, because even with a 0 pt stroke width InDesign will think the color is still in use.
MemberOops. Gremlins Ate My Backslash! :-(
(^s*l)|(<(?!(the|an?|in|to|o[rfn]|for)>)l)
(It was the one right before '>' that went missing … this time.)
The Ye-Shall-Not-Find-This list is a bit obfuscated because of my shorthand notations:
an? = 'a', optionally followed by one 'n'
o[rfn] = 'o', followed by one of 'r', 'f', or 'n'
After that the word should end (A-M thought of that), which is done by the last > code (End Word). If none of the above applies, the first lowercase character is matched.
The stuff at the start is “Beginning of line, any amount of whitespace (including zero), then a lowercase character. This ensures the first word is always capitalized — try it with “iPads are expensive toys” … (You'll see ID toggle between lowercase and uppercase while entering this.)
MemberDon't forget: a GREP style can only change lowercase to uppercase, since that's all that is possible with a character style. So a GREP style cannot convert an uppercase to a lowercase character to 'correct' from “InDesign Is A Rather Good Program” to “InDesign is a Rather Good Program”.
The same goes for the first word of a title — this would typically already be entered as a capital.
(Harbs' tool does not have these limitations.)
That said, A-M's GREP can be adjusted to this to change the first character as well (and it shows where the backslashes go):
(^s*l)|(<(?!(the|an?|in|to|o[rfn]|for)>)l)
MemberSomeone who doesn't know what he's talking about?
“Composite”, that makes sense in a color workflow — i.e., don't send a color separated file. “PDF” speaks for itself. But “PC”!? PDF files have always been platform independent. There are a few other file formats that claim platform independence, such as InDesign (its files still contain a marker for Intel/Motorola byte order), but for PDFs it never has been an issue.
“PC” might stand for something entirely different, though. “Politically Correct” comes to mind — that would make sense, in a media environment :-D “Please ensure your advert is p.c.”
MemberOops. Gremlins Ate My Backslash! :-(
(^*)|(\<(?!(the|an?|in|to|o[rfn]|for)\>))
(It was the one right before '>' that went missing … this time.)
The Ye-Shall-Not-Find-This list is a bit obfuscated because of my shorthand notations:
an? = 'a', optionally followed by one 'n'
o[rfn] = 'o', followed by one of 'r', 'f', or 'n'
After that the word should end (A-M thought of that), which is done by the last \> code (End Word). If none of the above applies, the first lowercase character is matched.
The stuff at the start is “Beginning of line, any amount of whitespace (including zero), then a lowercase character. This ensures the first word is always capitalized — try it with “iPads are expensive toys” … (You'll see ID toggle between lowercase and uppercase while entering this.)
MemberDon't forget: a GREP style can only change lowercase to uppercase, since that's all that is possible with a character style. So a GREP style cannot convert an uppercase to a lowercase character to 'correct' from “InDesign Is A Rather Good Program” to “InDesign is a Rather Good Program”.
The same goes for the first word of a title — this would typically already be entered as a capital.
(Harbs' tool does not have these limitations.)
That said, A-M's GREP can be adjusted to this to change the first character as well (and it shows where the backslashes go):
(^*)|(\<(?!(the|an?|in|to|o[rfn]|for)>))
MemberSomeone who doesn't know what he's talking about?
“Composite”, that makes sense in a color workflow — i.e., don't send a color separated file. “PDF” speaks for itself. But “PC”!? PDF files have always been platform independent. There are a few other file formats that claim platform independence, such as InDesign (its files still contain a marker for Intel/Motorola byte order), but for PDFs it never has been an issue.
“PC” might stand for something entirely different, though. “Politically Correct” comes to mind — that would make sense, in a media environment :-D “Please ensure your advert is p.c.”
MemberPerhaps it's the PostScript Level — InDesign sets this to Level 3 in the Graphics section of the Print dialog. Tone it down to 2 and it might work (if your printer age is in the double digits, it might even need a '1' there).
It seems the default settings for your system are fine, and ID is just overriding them with 'bad' stuff.
MemberPerhaps it's the PostScript Level — InDesign sets this to Level 3 in the Graphics section of the Print dialog. Tone it down to 2 and it might work (if your printer age is in the double digits, it might even need a '1' there).
It seems the default settings for your system are fine, and ID is just overriding them with 'bad' stuff.
MemberColly, no need to despair (yet). It seems the buggy Index is strongly linked to the Book function — InDesign “just” forgets to update the index per each file, it seems. I read on another forum it should be possible to manually update the index in each file, to force all index entries to be current when the Index Book function gets activated.
I don't have my 50 MB/53 files with me — it's a weekend! — but I'll try that for sure. Shame about the work day I spend writing scripts … Perhaps I can send Adobe a bill for the hours spend debugging.
The Javascript Help lists “update” under “Index”, but with this rather puzzling note:
Updates the index preview pane. Note: Does not update the index.
— so it might be scriptable to semi-automatically update all, or it might not.
-
AuthorPosts