This is Twilight Zone weird - font gets trimmed when converting to PNG....

[Michael Gould]

I am using FH10 (wish I could afford to upgrade). I am making a graphic
that needs to be scalable for different print jobs, and then cut it (export)
in PNG format (Since I do not have a post-script printer, I cannot make a
decent EPS file.).

So far, easy.

However, when I render to PNG, one font gets trimmed off the top (I will
lose the upper serifs.). The amount of trim is related (inversely) to the
amount of anti-aliasing I specify - I lose nothing with no anti-aliasing,
and lose the most with anti-aliasing set to 4.

Okay, so I will go ahead and convert the text to paths, right? Wrong. The
paths get distorted when I make the conversion (jagged curves).

Now here is the weirdest bit...this seems to happen with only one font -
Goudy Stout (ttf). I had two versions in my library with two different file
sizes and got the same issue whichever one I had installed.

I could cut it in fireworks, but Fireworks (I have MX) is rather unfriendly
to print ops, and mucks with my font spacing if I copy and paste from FH10,
plus I avoid converting fonts to curves because of the abovementioned path
distortion. Corel Draw doesn't have some of the precision features for text
stretching, and I had already used up my trial version of Illustrator.

Any advice or other things I could make use of will be appreciated, but I
definitely want to solve this in FreeHand if I can.

Thanks, All!

Mike

[Ian]

A couple of possible solutions (no guarantees!)

(1) Even if you don't have a physical postscript printer, you can still
install one and produce ps files, and hence possibly eps.

(2) From what I've seen, read & experienced with FH10 & later problems, the
best solution is to upgrade to FH9. (Upgrade in this context means "migrate
to a better, more stable, more print-friendly, less bug-ridden, faster
version" rather than "increase the version number, decrease productivity,
increase workload, discover new, slower, less efficient and worse way to do
things."

Ian.


"Michael Gould" <bugdagoulds@hotmail.com> wrote in message
news:cfqfrr$itk$1@forums.macromedia.com...

> I am using FH10 (wish I could afford to upgrade). I am making a graphic
> that needs to be scalable for different print jobs, and then cut it

(export)

> in PNG format (Since I do not have a post-script printer, I cannot make a
> decent EPS file.).
>
> So far, easy.
>
> However, when I render to PNG, one font gets trimmed off the top (I will
> lose the upper serifs.). The amount of trim is related (inversely) to the
> amount of anti-aliasing I specify - I lose nothing with no anti-aliasing,
> and lose the most with anti-aliasing set to 4.
>
> Okay, so I will go ahead and convert the text to paths, right? Wrong.

The

> paths get distorted when I make the conversion (jagged curves).
>
> Now here is the weirdest bit...this seems to happen with only one font -
> Goudy Stout (ttf). I had two versions in my library with two different

file

> sizes and got the same issue whichever one I had installed.
>
> I could cut it in fireworks, but Fireworks (I have MX) is rather

unfriendly

> to print ops, and mucks with my font spacing if I copy and paste from

FH10,

> plus I avoid converting fonts to curves because of the abovementioned path
> distortion. Corel Draw doesn't have some of the precision features for

text

> stretching, and I had already used up my trial version of Illustrator.
>
> Any advice or other things I could make use of will be appreciated, but I
> definitely want to solve this in FreeHand if I can.
>
> Thanks, All!
>
> Mike
>
>

[Michael Gould]

I've tried #1 with other projects, to no avail vis-á-vis EPS quality.

#2 sounds like something I could try...except that I only have an academic
license for ver 9 anda commercial license for 10 - any advice from the gang
out there?

Thanks Ian!

Mike

"Ian" <ian@pobox791.co.nz> wrote in message
news:cfv5qi$i7i$1@forums.macromedia.com...

>A couple of possible solutions (no guarantees!)
>
> (1) Even if you don't have a physical postscript printer, you can still
> install one and produce ps files, and hence possibly eps.
>
> (2) From what I've seen, read & experienced with FH10 & later problems,
> the
> best solution is to upgrade to FH9. (Upgrade in this context means
> "migrate
> to a better, more stable, more print-friendly, less bug-ridden, faster
> version" rather than "increase the version number, decrease productivity,
> increase workload, discover new, slower, less efficient and worse way to
> do
> things."
>
> Ian.
>
>
> "Michael Gould" <bugdagoulds@hotmail.com> wrote in message
> news:cfqfrr$itk$1@forums.macromedia.com...

>> I am using FH10 (wish I could afford to upgrade). I am making a graphic
>> that needs to be scalable for different print jobs, and then cut it

> (export)

>> in PNG format (Since I do not have a post-script printer, I cannot make a
>> decent EPS file.).
>>
>> So far, easy.
>>
>> However, when I render to PNG, one font gets trimmed off the top (I will
>> lose the upper serifs.). The amount of trim is related (inversely) to
>> the
>> amount of anti-aliasing I specify - I lose nothing with no anti-aliasing,
>> and lose the most with anti-aliasing set to 4.
>>
>> Okay, so I will go ahead and convert the text to paths, right? Wrong.

> The

>> paths get distorted when I make the conversion (jagged curves).
>>
>> Now here is the weirdest bit...this seems to happen with only one font -
>> Goudy Stout (ttf). I had two versions in my library with two different

> file

>> sizes and got the same issue whichever one I had installed.
>>
>> I could cut it in fireworks, but Fireworks (I have MX) is rather

> unfriendly

>> to print ops, and mucks with my font spacing if I copy and paste from

> FH10,

>> plus I avoid converting fonts to curves because of the abovementioned
>> path
>> distortion. Corel Draw doesn't have some of the precision features for

> text

>> stretching, and I had already used up my trial version of Illustrator.
>>
>> Any advice or other things I could make use of will be appreciated, but I
>> definitely want to solve this in FreeHand if I can.
>>
>> Thanks, All!
>>
>> Mike
>>
>>

>
>