Only if you conduct search query on the topic, you'll be more likely to find same issue. It has bee, in fact, discussed often as recently many times.
Secondly, please know and understand that Fireworks CS4 USE new, and DIFFERENT type engine. In legacy version of Fireworks CS3, Fireworks used formerly Macromedia type engine.
Now with Fireworks CS4 use new, different font engine technology that conforms with all other Adobe creative suite applications.
If you read this article related to "Working with the Adobe Text Engine in Fireworks CS4" discussed in Adobe Developer Center | Firework articles...
Once you read that information, I believe and trust you'll have a better experience working with Fireworks using this system.
Hope that helps and good luck!
The version of the Adobe text engine in FW hardly conforms with that of PS and AI. No where in that article does it discuss how to prevent the "Convert Text to Paths" tool from demolishing your fonts OR prevent fireworks from causing text to bleed 10px outside of it's text box when moved. I just need someone to tell me that they recognize the problem and are working on a (free) update as we speek. All of the responses I've seen to bugs are hardly helpful, try to turn the story around to make it seem like the user is wrong, or give some quick fix that switches back the rendering engine to CS3's which can be equally buggy at times. Bugs are treated like features and no one wants to admit there is something wrong.
If this is a "feature" of the new engine, I don't want to know what a bug looks like.
I haven't used CS4 much yet. But if I had to speculate, I seriously doubt that this is either: a) news to Adobe or b) something they can fix quickly.
If there's enough outcry then they'll spend the resources on a patch.
Does any of the text objects which you were converting to paths, had missing fonts? When we convert any text (which is having missing font) to paths, it gets substituted with default font and then rendered as paths.
Can you post an editable png file where you are seeing this issue?
No missing fonts. This is Arial, Georgia, and Times New Roman (it's editable):
You're converting text from the new text engine to paths from the new vector engine. How did you guys not foresee this as a problem? Text-to-paths is the most vital tool for sending documents to others who don't have the same fonts as you and CS4 renders the feature useless because the output is laughable.
Originally posted by: Tim Shundo
You're converting text from the new text engine to paths from the new vector engine. How did you guys not foresee this as a problem?
Maybe because it is an isolated problem. Tim, I opened your file in Fw CS4 here, and converted your "9" to paths using Ctrl+Shift+P. I got an image not nearly as distorted as yours. I could detect minor differences only if I overlapped mine with the original and zoomed in very closely. You can download and see my results here.
If your only concern is font compatibility, you could try flattening the text to bitmap (Ctrl+Alt+Shift+Z) instead. I tried that too, and on my setup it resulted in a pixel-perfect copy of the original - see on the image above.
http://design.thaiwonders.com - Innovative Fireworks Tutorials
Having the same problem with Fireworks CS4....
Distorted text when converting form text to paths....
Figured it out......
Happens if you SCALE a text field, and then try to convert to paths...
If you have the problem you must copy the contents of thet text area into a new (non scaled) text area, then convert to paths....