Forum Replies Created
-
AuthorPosts
-
CalvinFold
ParticipantYeah I missed it because it seem too simple…stupid me, and apologies to you. :/
Thanks for your help, very effective! And the tutorial on pattern groups and look-ahead/behind I'll save for the next time I get hung-up on that idea. Will also be handy in MailSmith. :)
CalvinFold
ParticipantYeah I missed it because it seem too simple…stupid me, and apologies to you. :/
Thanks for your help, very effective! And the tutorial on pattern groups and look-ahead/behind I'll save for the next time I get hung-up on that idea. Will also be handy in MailSmith. :)
CalvinFold
Participant1…em-dashes do not have a space on either side, technically. They should be typed glyph+em-dash+glyph. With a good font this works just fine. With lesser-quality fonts, this doesn't work so well, hence my question. In retrospect, switching from Metrics to Optical might work, but this GREP line of thought is still worth pursuing for some fonts.
2…It's a matter of time—specifically, rushing. Solving problems is my job (depending on the hat I have on at the time), and giving them a “just do this in GREP Styles” is one thing. Asking them to remember to do a GREP Search just before the job goes to production (and hope someone down the line doesn't edit or fiddle with it as it passes through multiple other hands on the way) is asking a bit much in our workflow.
“Magic” solutions no one thinks twice about. If they have to do it manually, it'll never happen or will happen wrong. ;)
You'd probably have to work here to understand why “search and replace” tips aren't viable here—solutions have to be automated and survive passing through alot of hands and stay correct at every stage (let's not confuse the proofreaders…). I have to admit even *I* wouldn't remember to do last-minute Search/Replace solutions when someone is breathing down my neck for the printouts…
CalvinFold
ParticipantThese orphan/runt control GREP Styles are clever way around the lack of an actual CS4 option to prevent it (still wishing!). CS4 might be better at controlling the problem, but it isn't perfect and the proofreaders call me on it every time. I've been starting to use GREP styles to just automatically eliminate anything they might catch.
Now I can add this little trick…
CalvinFold
ParticipantYou got it. I understand the dangers of “hiding” or “automagically” making corrections of these kinds. But on the other hand, the only people here who will even touch GREP-anything are the power-users, and what I'm looking at is a power-user solution. ;)
I've been cruising the GREP threads here, but haven't bumped into the one you refer to…can you provide a URL, you have me curious. :)
Your tracking idea is a good one, and I just did a quick test, and what would be needed was a pattern search like this:
find: a glyph followed by an em-dash followed by a glyph
apply: character style to the em-dash and the preceding glyph (since the tracking only applies to the space after a glyph when highlighting a single glyph)
I've not quite wrapped my head around “look for this pattern but only apply the character style to these sub-elements of what you found”…any kind souls willing to point me in the right direction?
CalvinFold
ParticipantI've been meaning to look into this myself, for those times when I make a GREP style to format something, but occassionally want to “undo” the styling for a specific instance.
I just did some experimenting, and it looks like if you manually apply a Character Style it will over-ride one applied by a GREP Style. The trick is, the over-riding character style has to be explicit enough to “blot out” any attributes from the GREP Style.
EXAMPLE:
I have a GREP Style that applies a Character Style named “Computer Code” to e-mail addresses. It changes the font, size, and color. If I manually apply a Character Style onto that e-mail address whose only attribute is “color=red” then the GREP Style's font and size remain, but the overlayed “red” will take precidence.
So in order for the “overlay” to work the Character Style has to explictly state all the attributes to put-back.
The only problem I see, though it could be a biggie, is if you change the Paragraph Style at any point, you'll have to remember to match-up the overlay Character Style to match.
Does that make any sense? I found it hard to describe…
CalvinFold
Participant1…em-dashes do not have a space on either side, technically. They should be typed glyph+em-dash+glyph. With a good font this works just fine. With lesser-quality fonts, this doesn't work so well, hence my question. In retrospect, switching from Metrics to Optical might work, but this GREP line of thought is still worth pursuing for some fonts.
2…It's a matter of time—specifically, rushing. Solving problems is my job (depending on the hat I have on at the time), and giving them a “just do this in GREP Styles” is one thing. Asking them to remember to do a GREP Search just before the job goes to production (and hope someone down the line doesn't edit or fiddle with it as it passes through multiple other hands on the way) is asking a bit much in our workflow.
“Magic” solutions no one thinks twice about. If they have to do it manually, it'll never happen or will happen wrong. ;)
You'd probably have to work here to understand why “search and replace” tips aren't viable here—solutions have to be automated and survive passing through alot of hands and stay correct at every stage (let's not confuse the proofreaders…). I have to admit even *I* wouldn't remember to do last-minute Search/Replace solutions when someone is breathing down my neck for the printouts…
CalvinFold
ParticipantThese orphan/runt control GREP Styles are clever way around the lack of an actual CS4 option to prevent it (still wishing!). CS4 might be better at controlling the problem, but it isn't perfect and the proofreaders call me on it every time. I've been starting to use GREP styles to just automatically eliminate anything they might catch.
Now I can add this little trick…
CalvinFold
ParticipantYou got it. I understand the dangers of “hiding” or “automagically” making corrections of these kinds. But on the other hand, the only people here who will even touch GREP-anything are the power-users, and what I'm looking at is a power-user solution. ;)
I've been cruising the GREP threads here, but haven't bumped into the one you refer to…can you provide a URL, you have me curious. :)
Your tracking idea is a good one, and I just did a quick test, and what would be needed was a pattern search like this:
find: a glyph followed by an em-dash followed by a glyph
apply: character style to the em-dash and the preceding glyph (since the tracking only applies to the space after a glyph when highlighting a single glyph)
I've not quite wrapped my head around “look for this pattern but only apply the character style to these sub-elements of what you found”…any kind souls willing to point me in the right direction?
CalvinFold
ParticipantI've been meaning to look into this myself, for those times when I make a GREP style to format something, but occassionally want to “undo” the styling for a specific instance.
I just did some experimenting, and it looks like if you manually apply a Character Style it will over-ride one applied by a GREP Style. The trick is, the over-riding character style has to be explicit enough to “blot out” any attributes from the GREP Style.
EXAMPLE:
I have a GREP Style that applies a Character Style named “Computer Code” to e-mail addresses. It changes the font, size, and color. If I manually apply a Character Style onto that e-mail address whose only attribute is “color=red” then the GREP Style's font and size remain, but the overlayed “red” will take precidence.
So in order for the “overlay” to work the Character Style has to explictly state all the attributes to put-back.
The only problem I see, though it could be a biggie, is if you change the Paragraph Style at any point, you'll have to remember to match-up the overlay Character Style to match.
Does that make any sense? I found it hard to describe…
-
AuthorPosts
