claidheamdanns wrote:
A non-breaking space or changing to non-breaking would do the same thing, if there was change in the paragraph content.
Not necessarily. A forced line break will ALWAYS break the line at that point. A non-breaking space will simply prefnt the line from breaking at that point. This means that if the line break were to be forced to the beginning of the next line due to an edit you'll get a near-empty line in the middle of your paragraph. With the non-breaking space the following text will simply follow naturally and the line will break further along.
Yes, but what we are talking about here is where an editor wants to push a word to the next line. So, apart from using a soft return, your method would be to group that word together with the following word, via no break in the the paragraph/character or via a non-breaking space character.
So then, if a word was taken out of the paragraph somewhere before that, we could conceivably still be left with a nasty-looking break in the text.
An additional issue with using the non-breaking function is that it causes an override in the style, which is not desirable.
I do use non-breaking styles in GREP, for instance, to make sure that the a.m. does not get separated from a time, or to keep web addresses from breaking. But since these are written into GREP, they do not cause an override in the style.
It's not the problem of the editor pushing the first word to the next line, it's when he or she comes back and makes a second change. At best a non-breaking space will simply disappear visually (and it is NOT a style override, by the way, just another character as is the forced break, as opposed to No Break -- but the desirability or lack thereof of having the occasional override is another discussion) and at worst it will screw up the line like the forced break.
You can do what you want, but I prefer the odds with the non-breaking space.
You can do what you want, but I prefer the odds with the non-breaking space.
Indeed - the chances that it will appear in the middle of a line and not unduly alter the composition of the paragraph are much better than the odds that a soft return will, after a second edit, just happen to fall on the end of a line. It depends on a wide variety of factors, of course, but I'm in general quite pleased that I have so many ways to affect text composition. I use 'em all. Using only soft returns is something like using only tracking - you starve yourself of options, and the elegance of your layouts can suffer as a result. It doesn't necessarily suffer, of course, but the chances are good.
Peter, I may not have worded it accurately, but that's exactly what I was talking about. And yes, I meant the No Break function was a style override, not the non-breaking space.
I definitely not opposed to using new methods. I've tested out your method, and I can see where your non-breaking space has merit if only a single word is being pushed, but quite often it is 2 or three trailing words on the end of a line or a cascade within the paragraph.
Here's a good example for the soft return:
Tasting Times: 11 am – 5 pm, Monday – Friday; 11 am – 6 pm,
Saturday – Sunday
I have been asked to push 11 am – 6 pm down to the next line. This would require 4 separate non-breaking spaces, or I could just use on soft return. I tried it both ways.
Claidh, I actually use the "No Break is an override" part to restore any messed-with paragraph to its "normal" state ...
I don't care what I did to a particular paragraph, or why, but I just may want all of its custom tracking and tweaking be gone because. Typically, if there were some pretty major editings in the text, this'd make all earlier tinkering obsolete, and possibly even harmful.
Your manually applied Soft Returns would stay behind ...
I've found another use for the soft return, and I'm kind of new at this but I wanted to throw it in the discussion:
When doing listings, for example address listings, and the whole address block needs to stay together... Maybe some of the addresses have 5 lines and some have 4 (ruling out the practicality/uniformity of a table), and you want to employ the "keep" paragraph option, but each line of the address block starts a new paragraph. All the "keep" options apply only to lines within one paragraph - therefore, soft returning after each line within the block will keep the whole address block in one paragraph and enable the "keep" functionality.
I was wary to use soft returns for any reason, but I could not find another way to do this. I'm beginning to appreciate the distinct usefulness of soft returns.
--
music to make you feel better about being depressed
North America
Europe, Middle East and Africa
Asia Pacific