Forum Replies Created
-
AuthorPosts
-
Theunis De Jong
Member.. GREP is case-sensitive
True
and whole word by default. ..
False :-D
Massey, are you using hotkeys for “Find Next” and “Find Next Grep”? I don't (well, only for regular “Find next”) and never have had this problem.
MemberThey also have unbeatable prices and good quality work. And right now cost is a huge factor.
That sounds they have a fixed way of processing others' documents. Hard to argue with, indeed. Can you ask them (nicely) why they won't accept PDFs? IDML only has been around for, what, 18 months? And it's not likely to be going “the document format of the future”, Adobe has always reserved that particular phrase for PDFs.
Alternatively, always do the best job you can and let someone else make a mess — so you can point out that you've been warning everyone, like, forever!
MemberThat's … cumbersome. (It is! Honestly!)
1. You might have used the regular search & replace. (Unless you did need one of the more advanced GREP-only functions to do more — you don't mention it, though, so I think you didn't need to.)
2. The parentheses are 'special' inside GREP. They “mark” a group, and do not take part in the searching/replacing. This is an important feature of GREP — perhaps you replaced a few “Swim4life” without parentheses as well, as these will also have been found!
3. Heh — and in the third round, you could also have used regular search & replace to remove those parentheses … You certainly didn't have to replace them with a space — you can also search for something and replace with nothing.
The proper way to search for parentheses in a GREP expression is to un-make them special. As it happens, putting them inside square brackets is a way (and you could even have removed both open and close at once, using “[()]” — a sidenote), but the recommended way to search for a character that's normally “special” is to precede it with a backslash. That's the magic marker you were looking for. So
(Swim4life)
would have found only the phrases including their parentheses.
(Edit because the lil' backslash gremlin ate my backslashes! I'll feed him a few more, just to humour him: and a 6th, for good measure: )
Member… If my printer didn't want the orginal Indesign files …
Sorry to break in, but that's really a bad way of working. We're in the 21st century now, and have been for some time …
It's time to face your boss and list the number of things that can go wrong in such a workflow … If he has a couple of hours, that is.
MemberThey also have unbeatable prices and good quality work. And right now cost is a huge factor.
That sounds they have a fixed way of processing others' documents. Hard to argue with, indeed. Can you ask them (nicely) why they won't accept PDFs? IDML only has been around for, what, 18 months? And it's not likely to be going “the document format of the future”, Adobe has always reserved that particular phrase for PDFs.
Alternatively, always do the best job you can and let someone else make a mess — so you can point out that you've been warning everyone, like, forever!
MemberThat's … cumbersome. (It is! Honestly!)
1. You might have used the regular search & replace. (Unless you did need one of the more advanced GREP-only functions to do more — you don't mention it, though, so I think you didn't need to.)
2. The parentheses are 'special' inside GREP. They “mark” a group, and do not take part in the searching/replacing. This is an important feature of GREP — perhaps you replaced a few “Swim4life” without parentheses as well, as these will also have been found!
3. Heh — and in the third round, you could also have used regular search & replace to remove those parentheses … You certainly didn't have to replace them with a space — you can also search for something and replace with nothing.
The proper way to search for parentheses in a GREP expression is to un-make them special. As it happens, putting them inside square brackets is a way (and you could even have removed both open and close at once, using “[()]” — a sidenote), but the recommended way to search for a character that's normally “special” is to precede it with a backslash. That's the magic marker you were looking for. So
\(Swim4life\)
would have found only the phrases including their parentheses.
(Edit because the lil' backslash gremlin ate my backslashes! I'll feed him a few more, just to humour him: \ and a 6th, for good measure: \)
Member… If my printer didn't want the orginal Indesign files …
Sorry to break in, but that's really a bad way of working. We're in the 21st century now, and have been for some time …
It's time to face your boss and list the number of things that can go wrong in such a workflow … If he has a couple of hours, that is.
MemberI was hoping someone else would come up with some brite idea. … Both Index and Table of Contents are firmly based on the concept of “page numbers”, and you can't really blame Adobe for this ;-)
Did you try the Table of Contents Advanced options? It is possible to sort entries alphabetically, and it's also possible to not insert page numbers. However, that leaves the issue of your hymn numbers — best would be if you could insert a flush right tab right away. You do need them on the right of your titles (so you can insert flush tabs manually), and that might need some trickery in setting up your styles, etc., etc.
TOC trickery is not really my fortay …
MemberI was hoping someone else would come up with some brite idea. … Both Index and Table of Contents are firmly based on the concept of “page numbers”, and you can't really blame Adobe for this ;-)
Did you try the Table of Contents Advanced options? It is possible to sort entries alphabetically, and it's also possible to not insert page numbers. However, that leaves the issue of your hymn numbers — best would be if you could insert a flush right tab right away. You do need them on the right of your titles (so you can insert flush tabs manually), and that might need some trickery in setting up your styles, etc., etc.
TOC trickery is not really my fortay …
MemberCopy the image, then search for your text and replace with “contents of clipboard”. That's in the little menu to the right of the Change To field, “Other” category.
It's available in both GREP and the regular sort of Text searching — if the search text allows it, using the regular text find is the easiest way.
March 26, 2010 at 3:19 am in reply to: How to get white letters on a black background in a paragraph style? #55322MemberDepending on your exact needs, you can or you can't do that with InDesign.
InDesign does not support “setting a background color” for text. Fortunately, there are a few tricks that do work in some circumstances. The most popular is the Paragraph Rule.
This only works with single line stuff (like your heading!). In your heading style, define a Paragraph Rule Below. Make it thick enough for your text plus some more — about the height of the leading. Set the Offset to about minus half that value. Enable “Preview” so you can tinker with it until you are satisfied.
Unfortunately, if you run into the odd multi-line heading, the Paragraph Rule thing will not seem to work. Actually, it does but exclusively with a fixed number of lines, so you have to define separate styles for 1-line headings, 2-line headings, etc., each with a different line thickness and vertical offset.
MemberCopy the image, then search for your text and replace with “contents of clipboard”. That's in the little menu to the right of the Change To field, “Other” category.
It's available in both GREP and the regular sort of Text searching — if the search text allows it, using the regular text find is the easiest way.
March 25, 2010 at 8:19 pm in reply to: How to get white letters on a black background in a paragraph style? #52325MemberDepending on your exact needs, you can or you can't do that with InDesign.
InDesign does not support “setting a background color” for text. Fortunately, there are a few tricks that do work in some circumstances. The most popular is the Paragraph Rule.
This only works with single line stuff (like your heading!). In your heading style, define a Paragraph Rule Below. Make it thick enough for your text plus some more — about the height of the leading. Set the Offset to about minus half that value. Enable “Preview” so you can tinker with it until you are satisfied.
Unfortunately, if you run into the odd multi-line heading, the Paragraph Rule thing will not seem to work. Actually, it does but exclusively with a fixed number of lines, so you have to define separate styles for 1-line headings, 2-line headings, etc., each with a different line thickness and vertical offset.
MemberCalvin:
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)
Ehm… That's what this GREP does
.~_
I admit it's a tiny one, so perhaps that's why you didn't notice it. It's “any character followed by an em dash”. As you noticed, it's not necessary to apply it to the next character as well. It's therefore also not necessary to include it in the GREP style.
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?
That can be done in two ways. The first way only works with find-and-replace, and to use it you have to “mark” groups of characters to find with parentheses, (like) (this) — two groups. In the Replace With field, you refer to the found groups using $1, $2, $3 etc. (“$0″ is a special code for the entire found expression). So you can switch these two words around by putting “$2 $1″ into the Replace field. It's especially handy if you need to find “abc” and change only the “b” part. But —
The other way to do it, is with Lookahead and Lookbehind. They are pretty cool features, with some amazing capabilities. What they do is look for text before and/or after what you want to find, but without marking them — they do not get highlighted when you press “Find Next”. Hence, they are not touched by anything you put in the Replace With field. Subscripting the “2″ in “H2O” is a good example, as you cannot do that with one regular Find/Replace. However, when Looking Behind for an “H”, searching for a “2″, and Looking Ahead for an “O”, you can do it in one go! This particular example would look like this:
(?<=H)2(?=O)
with this full explanation, provided by something I am (or should be) working on:
(?<= Lookbehind Group
H Literal text ‘H’
) End Lookbehind Group
2 Literal text ‘2’
(?= Lookahead Group
O Literal text ‘O’
) End Lookahead Group
MemberThe slash doesn't :D Backslashes do, but the forward slash seems to be one of the handful non-alphanumerics that doesn't do anything. As far as I can tell, none of the characters in your sample need escaping.
As with your “200 words” thingy, some of the spaces may have been entered as hard (non-breaking) spaces. Select “Show invisible characters” and check for these.
You can also copy one of the lines and paste it into the Find what field of GREP — ID will convert any special characters to its GREP notation. It will not help if sometimes one space is entered as a hard space and on another occasion another space is, though.
You can always change every single space in the string to s, which is a catch-all for “any sort of space at all”.
-
AuthorPosts