I suffer the same problem when applying manual line breaks.

Héctor

So is this a limitation of the Paragraph Composer?

So is this a limitation of the Paragraph Composer?

It’s sort of the point of paragraph composer. Paragraph composer is not designed with much user intervention in mind, and works better for justified copy than ragged. If you want to start breaking stuff manually switch to single-line composer.

I would hardly call it a “limitation”.

What InDesign is trying to do, in Paragraph Composer mode, is to equalize the space widths of the entire paragraph. That’s best visible with justified text, but it also works with ragged-right text. It appears it works backwards from the manual line break for the first part, and forwards for the rest.

Putting in manual line breaks should be a last resort, as these will always bite you back when editing the text afterwards. Try using “No Break” on just those words you want to keep together. That will allow ID to use its own judgement on where the exact line breaks will come. I use that function so much for these sort of manual tinkering, I’ve assigned a shortcut key to it.

If you intended to get rid of the “used” because it sticks out of the rest, you could try fiddling with the hyphenation settings. The “Hyphenation Zone” doesn’t mean much to me, but you could try moving the “Better spacing - Fewer hyphens” slider either way.

If you desperately need total control of the paragraph (all of them or just this one), switch to the Line Composer. That’ll behave the way you are used of lesser programs (!)

Hi James,
Yes, I did some further reading and discussion with people more experienced with inDesign and sort of came to the same conclusion.

thanks,
Fredrik

Hi Theunis,
Thanks for your comments. I will try around with the “No Break” to get to know how that works.
And just for the record, I think InDesign is a great program ;)

F.

An easy way to create a non breaking word is to insert a discretionary hyphen before the word.

This is just an observation, but why are you adding a break before “used”? Your rag in the original is nominal, and hyphenation is limited, but as soon as you force return, you get twice as many hyphens and the ragging seems to become more prevalent. And if you forced return because “used” was too close to the margin, you’ve now force “found” a few lines lower even closer.

Like I said, just an observation.

It’s paragraph specific (return to return), but you can switch between single-line and paragraph composer. So if you want to manipulate a single paragraph, this might lead to a more suitable solution.

as soon as you force return, you get twice as many hyphens and the ragging seems to become more prevalent
Well, yes, that’s the undesired effect of the manual line break that had me asking in the first place :)

In any case, for my purposes, I’ll simply use the single-line composer and manually fix the rag.

Fredrik,

Could you post an image of the same paragraph with your manual tweaking? I’d love to compare the overall look of that against ID’s automated (mathematically optimized) solution.

For justified paragraphs, I’m almost always satisfied with how ID handles it. Mainly I adjust by hand to avoid a bad break (a visual one, not technical), or to keep “I” or “A” and the next word on a single line — just to be picky.

Ragged-right paragraphs are harder to judge, because of the big differences between two tries, but, while I don’t always take ID’s breaks for granted, I’m always struggling to get the overall look I want.

Just use “no break” formatting and apply it to the word “used” and the following word. Then the paragraph composer can still work its magic on the rest of the paragraph.

Cheers,

T