Forum Replies Created
-
AuthorPosts
-
August 25, 2010 at 1:21 am in reply to: Font viewer for uninstalled fonts from disk inside InDesign #56818
Theunis De Jong
MemberIt's too good — it shows several font types that you cannot use in InDesign: .fon, .fnt are Windows Bitmap formats. Don't know for sure about .mmm, as I haven't seen one of these in over a decade.
Are the fonts installed 'the regular way' into the host OS, or are they added to Common Files/Adobe/Fonts?
August 24, 2010 at 5:05 am in reply to: InDesign CS5, Find/Replace: Find previous option lacking? #56803Theunis De Jong
MemberUndo? That's what I use if I'm replacing manually and think I made a mistake. Pressing Undo returns the cursor back to the last change position, Redo takes you back back.
Find Previous has never been possible in any version of InDesign. (Okay, couldn't remember so I spend some time on the Web … neither had PageMaker!)
It's a curious omission.
Theunis De Jong
MemberOops — you're correct, I was thinking in the wrong direction!
Is it possible these files came from something like a CD- or DVD-archive? Sometimes the read-only attribute gets copied along with the rest.
Theunis De Jong
MemberIt should occur with every CS4 document … It automatically opens as a Copy because the file format is changed.
This has always been the case with opening older version files.
Theunis De Jong
MemberHi Gregor,
I never used it but isn't this what the Number Style Override is for?
(Although you might want to read this: https://forums.adobe.com/thread…..?tstart=-1)
Theunis De Jong
Member.. there is no any other language version. It is originally created in InDesign ..
It has been created on Mac OS X 10.5.8 in app version 5.0.4.682 (FS InDesign Japanese — a CS3 version) on Saturday, Oct 24, 2009, 10:14 AM. Per 13 July 2010 it was opened on a Mac OS X 10.5.8 with a Roman (regular) CS4 InDesign.
I've browsed the Scripting Ref but it appears the Roman InDesign simply does not have a command interface to change this. Create a new document and move your text in there.
Theunis De Jong
MemberGo through the document and delete all left-hand text frames? Hardly worth writing a script for ;)
Theunis De Jong
MemberRegarding vertical positioning: Use a Rule Above, with a color of None and a good distance in Vertical Offset, and switch “Keep In Frame” on to offset a first paragraph on a page. Works every time.
As for hiding a running header, rather than shift-click and deleting it (deprecated, actually) or applying another master page (which personally I prefer, and I take re-applying them for granted), you could use this extremely Dirty Trick. (Hold on to your seat.) In addition to your Rule Above, also define a Rule Below. Set its color to Paper and its thickness to +/- 12 pts — do not opt to Keep it In Frame. Then move it upwards with a negative Vertical Offset to cover the running header.
You might need to apply this style on the occasional left-hand blank page as well, if you start everything on a right hand page. If you have page numbers at the bottom, you can make a specialized “blank page” style, where you use the Rule Above (without Keep In Frame) to hide stuff on the top, and Rule Below to hide the bottom things.
Theunis De Jong
MemberThe worst part may yet come.
Ideally, Adobe would add a Toggle Frame Highlighting option in a new version — even more ideally, it would be Off by default ;)
Now imagine the hoards of bewildered CS5-first-time-users that upgrade to this new version and flood the forums with “ooh it doesn't highlite edges anymore, and i was counting on that feature! Adobe pleaz bring it back!”
Theunis De Jong
MemberThanks for the honourable mention, but I do think you're out of luck here …
Ad will find the first number in your story (i.e., one without a dollar sign before it) but GREP cannot discern frames. That is, A (and Z) will not match the first (or last) character per frame (much like GREP cannot 'see' the individual lines per paragraph).
You are also correct in your observation that anchored objects make things even more complicated — I've seen anchors move around and disappear when I tried to manipulate the text around them with GREP.
I think it's safest to remove all dollar signs using the regular Find-and-Change (GREP sometimes has problems with $, and you don't need a specialized GREP search to remove them either) and then just manually page through your document and insert them by hand where needed … :(
Theunis De Jong
MemberFred Goldman pointed out that the script did not work when the Character Style was set to “Ignore”. I've corrected that (new version) but it's a strange case. Setting “Ignore”, then closing the dialog and reopening it shows the setting as “None”. I should try to find out what InDesign actually does — either way, it's a bug somewhere.
Theunis De Jong
Memberw (type double backslashes in this forum ;)) doesn't really match a 'word', but just one 'word character'. According to InDesign, word characters include 0-9, a-z, A-Z, Cyrillic, Greek, and possibly other scripts as well (Hebrew, Arabic, Thai, Chinese and whatnot) and all accented variants of them. It noticeably does not include the common hyphen, so if you might have one in one of your words, you need to adjust your GREP.
The problem you are facing is that GREP is GREEDY by default: it tries to grab as much as possible, but always within the constraints you put in. That's why the seemingly straightforward “w.+~>” will capture anything up to the very last en space. Everything inbetween is matched because the period is 'any character at all', which is what gets repeated — in effect, it scans for the very first word character it can find, then matches everything up to the very last en space.
Fortunately, there is a toggle to make it less greedy: add a question mark after the repeat character. In addition, since the space is not a “word character” either, you need to specify that's valid too.
This ought to work better:
[w ]+?~>
which in plain English translates to “either a word character or a space, repeated as little as possible before encountering an en space”.
I'm a fan of matching as little as possible; in your case, it would match an optional initial space as well as the final en space. That's to be frowned upon, because imagine you want to apply underline instead of bold; then you'd see too much is marked. (I test my GREPs with Underline rather than Bold, so I can see what spaces get picked up.)
This somewhat more complicated GREP will do a neater job, because it only starts at a proper word character (not “word or space”, which picks up the first space) and checks for but does not include the final en space. I also added the hyphen in the repeating OR-set (it's a special character inside an OR set, so it needs escaping to get an 'actual' hyphen).
w[w- ]*?(?=~>)
Theunis De Jong
MemberSounds like we should be able to improve your workflow in a couple of different (possibly excluding) ways. You say you've made a few — can you post a link to a PDF, so we can see how it should look? One of those pages ought to be enough.
…[Copying] also copies over lots of spaces into the text which I end up having to delete manually …
Look up Find/Replace in the Help :D
Theunis De Jong
MemberThey fall under “something else” for sure. Footnotes are objects, just like text frames, rectangles, documents, and find/change sets, and have loads and loads of properties. Normally, I would write a script to copy all of the settings one by one, but … footnotes sure have a lot of them.
So I wrote an entirely new sort of script
It tries to copy intelligently whatever it can, from your currently active document (which should be in front of you), to either one single document of your choice, or to all open ones. In your case, you should open all of the documents in your book, then make sure the “source” for your footnote options is in front, and then run my script.It may display an alert telling you what items it cannot copy: not everything in the destination options can simply be “set” to the equivalent value in the source document. For example, if you created a custom character and paragraph style for your footnote options, there should be one with the same name in the destination documents. The same goes for colors and stroke styles.
The script only copies the names of these objects, not their definitions! So if you used a stroke color “MyOwnSpecialColor” that is defined as blue in your source but purple in one of the other documents, the color will not change.
The script is a bit too long to post in-line so d/l it here: ftnoptcopier.jsx (alternatively, download directly from my site: https://www.jongware.com/binaries/ftnoptcopier.zip)
Download (use a right click and select “Save target as”, or equivalent) and move it to your User Scripts folder. Double-click to run — well, after opening all documents you need to adjust, that is.
(After trying it: it seems it gets a .txt added to the file name for free. Remove this, it should simply be “fntoptcopier.jsx”, otherwise InDesign Does Not Compute.)
Theunis De Jong
MemberSure. Change the loop from
for (var d=0; d<book.bookContents.length; d++)
{
doc = app.open (book.bookContents[d].fullName);
words_a += countWords_a (doc);
words_b += countWords_b (doc);
doc.close(SaveOptions.NO);
}to
for (var d=0; d<app.documents.length; d++)
{
doc = app.documents[d];
words_a += countWords_a (doc);
words_b += countWords_b (doc);
} -
AuthorPosts
