Forum Replies Created
-
AuthorPosts
-
Theunis De Jong
MemberHi mate!
That can be done in several ways; pick any.
1. Use a nested style. Either use “through 2 Words” (or how much you need), or “up to 1 :” (just type in the “:” in the last field).
2. Use a GREP style (straightforward): “^.+?:”
3. Use a GREP style (exact): “^Figuresd+:”
The latter will only and exclusively pick up a starting 'Figure' text, so it'll automatically ignore lines where this is missing (or misspelled!).
MemberUh-oh. Seems the GREP style ignores paragraph Bullets & Numbering …
It makes some sense, as this type of numbering is something ID “tacks on” to the start of the paragraph. If you check with the Story Editor, you will see the text is not there!
Only two options this time, I'm afraid. First is to adjust your Bullets & Numbering setting — you can automatically have a character style applied to the custom numbering. I'm not sure what happens with cross-references to this same list, though; they might pick up that style as well. I guess you just have ta try it.
Second, you can change your fancy custom numbering to plain text — but then you'll loose the automatic numbering.
MemberHi mate!
That can be done in several ways; pick any.
1. Use a nested style. Either use “through 2 Words” (or how much you need), or “up to 1 :” (just type in the “:” in the last field).
2. Use a GREP style (straightforward): “^.+?:”
3. Use a GREP style (exact): “^Figure\d+:”
The latter will only and exclusively pick up a starting 'Figure' text, so it'll automatically ignore lines where this is missing (or misspelled!).
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.”
-
AuthorPosts