I solved it!
There's a file called Moray.ini that has a chart for all the possible
character map codes, what they are in Moray, and what they are converted to
in Pov. For some reason, at least for this particular font, the conversion
numbers are wrong, but if you change the Pov number to be the same as the
Moray number, it works correctly. Unfortunately, I wasted a lot of time last
night not getting results, because I found out this morning you have to
*re-start the computer* before the changes will take effect. I also found
out that it works with either Povray 3.1 or  3.5 ( I installed the Moray
patch, build 7025, which is supposed to make it compatible).
Thanks for your input.
Alex Wolff <ale### [at] gmxde> wrote in message
news:3C006A6F.21FC96E0@gmx.de...
> hi steve,
> the new povray 3.5 is not yet supported by moray. maybe you will have
> success by hand-coding your scene in povray 3.5.
> about moray 3.3: one of the new features in 3.3 is described as:
> >Added character mapping for TrueType objects. MORAY.INI contains a
> section where you can change mappings for the high ASCII characters. It
> contains mappings for all the base characters. Moray will now make
> POV-Ray render text with high-ASCII characters (umlauts, etc.)
> correctly.<
> i don't know what changes you'll have to make. maybe lutz can explain...
>
> i tried some umlauts (a, o or u with two dots above) and the results are
> very... well funny: with some ttfs all is working well, othertimes only
> one dot is rendered and othertimes nothing of sense comes out.
> sorry for my too fast answer. i did only read the features without
> trying out...
> alex wolff
>

Post a reply to this message