Comments on: InDesignSecrets Podcast 028

By: Jandeman

Jandeman — Tue, 06 Mar 2007 23:36:16 +0000

Well, suppose you have a very large textbox with justified text in Paragraph composer. In this text box, you have three lines of text before a forced line break, but the last line before this forced line break consist of only four or five words. The moment you type this forced line break, those first three lines get divided over the full column width which results in very large white space between the words (which can be very ugly).
In this case, I don’t want InDesign to fill out this third line, but there is no way, to my knowledge, to prevent this (while keeping justified text).
The only ‘bad’ solution, is to switch to Single line composer en to insert a flush space or tab before the forced line break.
Problem is that the rest of the paragraph is then also in single line composer.
I hope this explains more my question. (I’m from Belgium so my english could be somewhat ‘foreign’).

By: David Blatner

David Blatner — Tue, 06 Mar 2007 04:08:14 +0000

Jandeman, I’m not sure what you mean by “strange white space.” But why would you use a flush space before a forced line break (shift-return)? I agree that it is strange that ID adds a little space, but it is even more strange to put a flush space before a forced line break.

By: Jandeman

Jandeman — Tue, 27 Feb 2007 14:22:33 +0000

And, regarding this, I have a question:
The Flush space-thing applied before forced line break, works very well with Justified text, but only when I (have to) use the Single-Line composer. When I change it to Paragraph composer, I see some strange white space appear. It’s really annoying so if any one has a solution for this, please, let it go.
Thanks,
Jan

By: Jandeman

Jandeman — Tue, 27 Feb 2007 14:14:24 +0000

About flush space: where I use it: when you have text justified and you want to have a new line break, the last line will fill out which can give very large white spaces between the words. So there I use a flush space.

By: Name Alexey

Name Alexey — Tue, 10 Oct 2006 18:50:47 +0000

!!! It is class to itself

By: Andry

Andry — Sun, 08 Oct 2006 18:40:38 +0000

Autor, Respect!

By: Alan Gilbertson

Alan Gilbertson — Fri, 25 Aug 2006 05:05:42 +0000

Yes, that’s exactly what happened, and it drove me nuts until I’d figured it out. Since then I’ve done a few similar projects so I have it fairly well grooved in. But getting there was a tortuous process.

Data merge is easy enough once you grasp the key limitation, but it’s not exactly spelled out in the manual, is it? I really hope this gets fixed in CS3 so it’s more functional. I happen use it frequently, so the really annoying bits (like not being able to set up a two-sided, two-up layout as one document) are in my face regularly.

By: David Blatner

David Blatner — Thu, 24 Aug 2006 13:33:19 +0000

Great ideas, Alan. Thanks. I think what’s happening with the hyperlink/button problem is that you’re making a hyperlink in a text frame and then converting that to a button. The text frame is sitting “inside” the button object. You need to make a button object and then apply a hyperlink to that.

The data merge thing is definitely tricky. Rufus Deuchler wrote a good article on it for InDesign Magazine which was picked up by CreativePro.com.

As for the other interactive features, I can only suggest Sandee’s InDesign Visual QuickStart Guide, or “Real World InDesign CS2″ (by Olav Kvern and myself), which goes into a lot of details about these issues.

By: Alan Gilbertson

Alan Gilbertson — Tue, 22 Aug 2006 21:24:37 +0000

I’m on a roll today. Sorry. A great extension to the interactive button theme would be Hide/Show fields, which I also beat my head against a wall over. (I can show you the marks, but they’re not pretty.) You can create terrific rollover effects with this. The trouble is, getting there is like hacking into Sleeping Beauty’s castle: you know it’ll be worth it in the end, but man (or is that “dude”, these days), it’s painful.

By: Alan Gilbertson

Alan Gilbertson — Tue, 22 Aug 2006 20:31:41 +0000

Having wrassled with the interactive features a few times, I noticed a point that you might want to make clear. Setting up hyperlinks in InDesign is simple enough, and setting up buttons is, well, not so simple but still a hair this side of rocket science. Combine the two and you hit the really, really obscure feature: a hyperlink converted to a button doesn’t link. The hyperlink can be there, and sans button can work perfectly well. It will even test out okay from the Hyperlink palette — in InDesign. But it won’t work in the resulting PDF.
The only way to make a button hyperlink to its hyperventilating target is to add it to the (usually Up) button state by selecting Button Options from the flyout menu and adding Go To Anchor as a behavior. The anchor would be whatever you set up as a hyperlink destination inside the document.
As an aside: You might consider adding an “InDesign Drive-You-Crazy Feature of the Week” to the podcast. This one would be on my list, along with the “Everything on a data merge page except the data has to be on a master page” feature, which prevents even the sample label sheet that comes with InDesign from working. I still have brick-shaped marks on my head from both of those. (And, yes, it felt great when I stopped.)