POV-Ray : Newsgroups : povray.unofficial.patches : Text in MacMegaPov Server Time
2 Nov 2024 17:18:37 EDT (-0400)
  Text in MacMegaPov (Message 1 to 7 of 7)  
From: Josh English
Subject: Text in MacMegaPov
Date: 25 Jan 2000 11:08:56
Message: <388DCA74.EE5CEA14@spiritone.com>
Has anyone tried including a .ttf font into a scene using MacMegaPov
0.3? I get a whole string of errors.  It tells me that it can't find the
character "xxx" where "xxx" is the hexadecimal code (I think that's hex,
anyway) for every character.

I don't have this problem with the December release of the McUnofficial.

--
Josh English
eng### [at] spiritonecom
"May your hopes, dreams, and plans not be destroyed by a few zeros."


Post a reply to this message

From: smellenbergh
Subject: Re: Text in MacMegaPov
Date: 25 Jan 2000 14:41:00
Message: <1e4z8uy.98oe1s1n2asasN%smellenbergh@skynet.be>
Josh English <eng### [at] spiritonecom> wrote:

> Has anyone tried including a .ttf font into a scene using MacMegaPov
> 0.3? I get a whole string of errors.  It tells me that it can't find the
> character "xxx" where "xxx" is the hexadecimal code (I think that's hex,
> anyway) for every character.
This only happens with Mac converted fonts. At least, that's what we
found out. We can use all original windows true type fonts.
If we use the little utility that comes with the official 3.1 Macintosh
version to convert the installed Mac fonts, we can use some converted
Mac fonts (like verdana) but most of them are unusable.

We can not verify at this moment if the number of usable converted fonts
has decreased since the december release. If we remember well, there are
no changes between the december version and the current in the handling
of the true type fonts object.

The official Mac Team does warn that not all converted fonts are usable,
perhaps nothing has changed yet.


Smellenbergh

> I don't have this problem with the December release of the McUnofficial.
> 
> --
> Josh English
> eng### [at] spiritonecom
> "May your hopes, dreams, and plans not be destroyed by a few zeros."


-- 
e-mail:sme### [at] skynetbe

http://users.skynet.be/smellenbergh


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: Text in MacMegaPov
Date: 25 Jan 2000 15:23:47
Message: <388e0653@news.povray.org>
In article <1e4z8uy.98oe1s1n2asasN%smellenbergh@skynet.be> , 
sme### [at] skynetbe (smellenbergh) wrote:

> This only happens with Mac converted fonts. At least, that's what we
> found out. We can use all original windows true type fonts.
> If we use the little utility that comes with the official 3.1 Macintosh
> version to convert the installed Mac fonts, we can use some converted
> Mac fonts (like verdana) but most of them are unusable.

Basically all it does is take the resource based ttf data and copies it into
the data fork.

> We can not verify at this moment if the number of usable converted fonts
> has decreased since the december release. If we remember well, there are
> no changes between the december version and the current in the handling
> of the true type fonts object.

There must have been a change, it is probably looking for the wrong cmap
tables (Windows only ones) and ignores the Mac cmap tables...

> The official Mac Team does warn that not all converted fonts are usable,
> perhaps nothing has changed yet.

I found that depending on the font adding all Mac cmap tables (and for
MegaPOV I would also add all Unicode tables) will give better results, at
least for the official version.  Just try to run the Apple AAT Font Tool
over the font <http://fonts.apple.com/Tools/tooldir/AATFontTool.sea.hqx>, or
try the tons of other programmer level tools at
http://fonts.apple.com/Tools/agreed.html.
NOTE: Fonts may grow in size considerably when adding all cmap tables!!!


      Thorsten



____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Jon A  Cruz
Subject: Re: Text in MacMegaPov
Date: 25 Jan 2000 23:53:00
Message: <388E7EC6.7FC7AB9B@geocities.com>
Usually it's a problem either with not having the Apple MacRoman mapping table
(for the standard POV-Ray), or the Microsoft Unicode mapping table (for patched
versions with Unicode support). Many newer mac fonts have only the generic
Unicode mapping table and not the Apple MacRoman one, and thus can also be a
problem.

I really need to fix up my patch to compensate for this, and especially for the
newer Mac fonts since they don't work with the stock nor the Unipatched
versions. I'm sorry, I'll get my code out now and finish up the new rev to the
patch.

If you don't see something in a day or two, send me mail and ask me about it.


Thorsten Froehlich wrote:

> In article <1e4z8uy.98oe1s1n2asasN%smellenbergh@skynet.be> ,
> sme### [at] skynetbe (smellenbergh) wrote:
>
> > This only happens with Mac converted fonts. At least, that's what we
> > found out. We can use all original windows true type fonts.
> > If we use the little utility that comes with the official 3.1 Macintosh
> > version to convert the installed Mac fonts, we can use some converted
> > Mac fonts (like verdana) but most of them are unusable.
>
> Basically all it does is take the resource based ttf data and copies it into
> the data fork.
>
> > We can not verify at this moment if the number of usable converted fonts
> > has decreased since the december release. If we remember well, there are
> > no changes between the december version and the current in the handling
> > of the true type fonts object.
>
> There must have been a change, it is probably looking for the wrong cmap
> tables (Windows only ones) and ignores the Mac cmap tables...
>
> > The official Mac Team does warn that not all converted fonts are usable,
> > perhaps nothing has changed yet.
>
> I found that depending on the font adding all Mac cmap tables (and for
> MegaPOV I would also add all Unicode tables) will give better results, at
> least for the official version.  Just try to run the Apple AAT Font Tool
> over the font <http://fonts.apple.com/Tools/tooldir/AATFontTool.sea.hqx>, or
> try the tons of other programmer level tools at
> http://fonts.apple.com/Tools/agreed.html.
> NOTE: Fonts may grow in size considerably when adding all cmap tables!!!
>
>       Thorsten
>
> ____________________________________________________
> Thorsten Froehlich
> e-mail: mac### [at] povrayorg
>
> I am a member of the POV-Ray Team.
> Visit POV-Ray on the web: http://mac.povray.org

--
"My new computer's got the clocks, it rocks
But it was obsolete before I opened the box" - W.A.Y.


Post a reply to this message

From: Josh English
Subject: Re: Text in MacMegaPov
Date: 26 Jan 2000 12:17:26
Message: <388F2B89.7D514208@spiritone.com>
I see. I tested it with the basic Text Fonts template, which uses cyrstal, and
it works fine.
I'll try porting the fonts from my Windows machine again. I can't remember
which .ttf files I copied and which ones I converted... It looks like I'll
have some hunting to do!

Thanks

smellenbergh wrote:

> Josh English <eng### [at] spiritonecom> wrote:
>
> > Has anyone tried including a .ttf font into a scene using MacMegaPov
> > 0.3? I get a whole string of errors.  It tells me that it can't find the
> > character "xxx" where "xxx" is the hexadecimal code (I think that's hex,
> > anyway) for every character.
> This only happens with Mac converted fonts. At least, that's what we
> found out. We can use all original windows true type fonts.
> If we use the little utility that comes with the official 3.1 Macintosh
> version to convert the installed Mac fonts, we can use some converted
> Mac fonts (like verdana) but most of them are unusable.
>
> We can not verify at this moment if the number of usable converted fonts
> has decreased since the december release. If we remember well, there are
> no changes between the december version and the current in the handling
> of the true type fonts object.
>
> The official Mac Team does warn that not all converted fonts are usable,
> perhaps nothing has changed yet.
>
> Smellenbergh
>
> > I don't have this problem with the December release of the McUnofficial.
> >
> > --
> > Josh English
> > eng### [at] spiritonecom
> > "May your hopes, dreams, and plans not be destroyed by a few zeros."
>
> --
> e-mail:sme### [at] skynetbe
>
> http://users.skynet.be/smellenbergh

--
Josh English
eng### [at] spiritonecom
"May your hopes, dreams, and plans not be destroyed by a few zeros."


Post a reply to this message

From: Jon A  Cruz
Subject: Re: Text in MacMegaPov
Date: 26 Jan 2000 12:29:01
Message: <388F2FF2.32FC3CB2@geocities.com>
If you are having problems and need to figure out some issues with fonts, send me
a mail. I have a simple Java utility I've been hacking on to get info from fonts
so that I can do the right thing in regards to TTF support. I can clean up a copy
and add a couple of warning lights so that you can see what the problem is.

Josh English wrote:

> I see. I tested it with the basic Text Fonts template, which uses cyrstal, and
> it works fine.
> I'll try porting the fonts from my Windows machine again. I can't remember
> which .ttf files I copied and which ones I converted... It looks like I'll
> have some hunting to do!
>
> Thanks
>
> smellenbergh wrote:
>
> > Josh English <eng### [at] spiritonecom> wrote:
> >
> > > Has anyone tried including a .ttf font into a scene using MacMegaPov
> > > 0.3? I get a whole string of errors.  It tells me that it can't find the
> > > character "xxx" where "xxx" is the hexadecimal code (I think that's hex,
> > > anyway) for every character.
> > This only happens with Mac converted fonts. At least, that's what we
> > found out. We can use all original windows true type fonts.
> > If we use the little utility that comes with the official 3.1 Macintosh
> > version to convert the installed Mac fonts, we can use some converted
> > Mac fonts (like verdana) but most of them are unusable.
> >
> > We can not verify at this moment if the number of usable converted fonts
> > has decreased since the december release. If we remember well, there are
> > no changes between the december version and the current in the handling
> > of the true type fonts object.
> >
> > The official Mac Team does warn that not all converted fonts are usable,
> > perhaps nothing has changed yet.
> >
> > Smellenbergh
> >
> > > I don't have this problem with the December release of the McUnofficial.
> > >
> > > --
> > > Josh English
> > > eng### [at] spiritonecom
> > > "May your hopes, dreams, and plans not be destroyed by a few zeros."
> >
> > --
> > e-mail:sme### [at] skynetbe
> >
> > http://users.skynet.be/smellenbergh
>
> --
> Josh English
> eng### [at] spiritonecom
> "May your hopes, dreams, and plans not be destroyed by a few zeros."


Post a reply to this message

From: Anton Raves
Subject: Re: Text in MacMegaPov
Date: 28 Jan 2000 02:56:08
Message: <280120000856096279%a.raves@direct.a2000.nl>
With the official release of POV-Ray Mac came a REadMe document that
contained tips on how to use Macromedia's Fontographer to convert
PostScript Type 1 fonts into all fully usable TrueType fonts, I have
converted over 500 fonts myself that way and happily use them!

With the kindest of greetings,
  Anton Raves
  Wormerveer
  Netherlands
  http://people.a2000.nl/araves/

In article <1e4z8uy.98oe1s1n2asasN%smellenbergh@skynet.be>,
smellenbergh <sme### [at] skynetbe> wrote:

> Josh English <eng### [at] spiritonecom> wrote:
> 
> > Has anyone tried including a .ttf font into a scene using MacMegaPov
> > 0.3? I get a whole string of errors.  It tells me that it can't find the
> > character "xxx" where "xxx" is the hexadecimal code (I think that's hex,
> > anyway) for every character.
> This only happens with Mac converted fonts. At least, that's what we
> found out. We can use all original windows true type fonts.
> If we use the little utility that comes with the official 3.1 Macintosh
> version to convert the installed Mac fonts, we can use some converted
> Mac fonts (like verdana) but most of them are unusable.
> 
> We can not verify at this moment if the number of usable converted fonts
> has decreased since the december release. If we remember well, there are
> no changes between the december version and the current in the handling
> of the true type fonts object.
> 
> The official Mac Team does warn that not all converted fonts are usable,
> perhaps nothing has changed yet.
> 
> 
> Smellenbergh
> 
> > I don't have this problem with the December release of the McUnofficial.
> > 
> > --
> > Josh English
> > eng### [at] spiritonecom
> > "May your hopes, dreams, and plans not be destroyed by a few zeros."


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.