Apparently this bug has been around for ages! What the hell?
http://forums.adobe.com/message/2233023
I'm using Illustrator CS 5.1, but they mention CS2 ! Are you fricken kidding me??
The text was just an example (lorem ipsum dolor...). The actual text uses a lot of hyphens to split long words and I can't use Illustrator's built-in dictionary to hyphenate them for me. These hyphens have to be EXACTLY in the right spots, hence the need for manual break lines (Shift+Enter).
You think this behaviour is normal? Because even though these are just two paragraphs, it behaves like every line is an individual paragraph. The icons are very misleading. They act exactly like the first 3.
Apparently this bug has survived across versions for YEARS.
steve fairbairn wrote:
Illie is just doing what she is supposed to do. It is your text that is the problem.
Why have you got all those returns at line ends? They shouldn't be there.
Delete them and things will behave as you expect them to.
The Op is trying to set the text to a preferred way the lines should break to the next line. there is no reason that the soft returns line breaks should not be honored.
That ios what line breaks are for to be able to choose the way you want the text to flow.
You are correct Jacob soft returns were Introduced in I believe CS 2 and the justification and hyphenation should not be part of the equation if you do not desire hyphenation for instance.
It is an old bug since the inception of the soft return.
Perhaps it is fixed in CS 6 we will find out soon I already have my license on order.
It's a problem Jacob
There are many instances where adjusting spacing will alter lines which were previously fine. Basically it's a catch 22.... you get bad lines... fix spacing to correct the bad lines... you get other bad lines. What is needed is the ability to add a soft return (a la Indesign) and maintain the justification.
The current workaround is to add a hard return and then adjust any paragraph spacing and/or line spacing for the line above the hard return. It's WAY more trouble than it should be.
Not a bug by my definition but a poor feature or I won't be surprised if it is deliberately limited because they use it in the same way in Photoshop. If you copy text with non-paragraph breaks (soft returns) from Illustrator and paste it in inDesign the hidden characters show that Illustrator uses another kind of character that has nothing to do with soft return.
Trust Scott and me on the emil emil this is an acknowledged bug it is not supposed to work this way
We know this as a fact it is not suuposed to work this way it is supposed to work as the OP expects it to work. It is a short coming of the type engine but also because it is not implemented properly.
Doug Katz pointed out the there was n soft returns in Illustrator and so I made the feature request and when the soft returns where supported he immediately pointout the bug as i recall right heere on the forum and i filed the bug immediately after it was acknowledged after several other users confirmed the bug and it was never corrected.
If it is acknowledged by Adobe as a bug, then it is a bug. Did Adobe respond to someone with such confirmation?
What makes me think that it may not be a bug is the fact that Photoshop also has the same bug - in its paragraph panel it has the same text justifying options and lines with soft returns are treated the same. I'm also with the OP on this expecting the normal behavior to be the same as inDesign but I've seen crippled features made by design. I'll be happy to be wrong because if it is officially acknowledged as a bug then there is a chance they may eventually fix it.
Take two minutes and go to InDesign if you want to understand how Spider wants it to work
I know all about that. InDesign has the infuriating habit of disarranging text that one has maybe spent a long time arranging.
If you insert an optional hyphen at some point, the lines previous to it it may suddenly be completely messed up although there was nothing wrong with them before.
It sometimes takes some considerable effort to hyphenate a paragraph satisfactorily and InDesign's automation of the hyphenation process frequently works against you.
If you take pride in your work a more manual approach is often more satisfactory.
You never seem to read this correctly I clearly wrote that they have acknowledge it do you really think I am making this up?
Trust me I had communications with Adobe about this in what form I cannot tell you but this is a bug. Like it or not and you might think what you wish it will not change anything and unless they have address this issue in CS 6 then it is a bug that is still there.
It's a bug!
There are beta testers that comne this forum regularly if it were not a bug trust me they would have jumped in by now.
InDesign does not use the same Type engine as far as I know and I think that Photoshop and ID type engines are more related toeach other than Illustrator's type engine.
Which is one of the problems.
But I am pretty certain, though only guessing, that this will all come togehter in CS 7. And perhaps this bug might be fixed in a point release.
It would make illustrator so much more apealing.
Orly?
http://help.adobe.com/en_US/illustrator/cs/using/WS714a382cdf7d304e7e0 7d0100196cbc5f-63a4a.html
"Illustrator uses the same composition methods for line and word breaks that is used in Adobe InDesign. For more information on using these features, see web Help."
This problem doesn't exist in ID, so yes different code. Even aside from this problem, identical text doesn't justify the same in AI vs ID. Might not be noticable in a single paragraph, but set a couple of thousand words in both programs and compare and you'll find plenty of different line breaks.
Yours
Vern
North America
Europe, Middle East and Africa
Asia Pacific