Using Windows 95, POV-Ray version 3.0 as well as 3.1, I get error
messages when trying to use a particular TrueType font:

"Character XX not found" (XX being the ASCII number of the character)
All the characters in each line of text are defined in this font, and no
other programs have trouble using the font except for POV-Ray. They are
not high-ASCII characters; most of them are uppercase or lowercase
letters.
Now here's the stinger: This font is homemade. It was made with a tool
called Softy, which doesn't allow some additional data (offset/size for
superscripts, subscripts, etc., etc.) to be defined. Other fonts that
*do* work have additional table entries that I suspect are expected by
POV-Ray to be there.

The irony of this bug is that if a character is not found, a capital A
from the font is shown in its place. ("A" is the third glyph in the
font.) However, if "A" is included in the text, I am told "Character 65
(0x41) not found in font ....", despite the fact that it still displays
just fine. Obviously POV-Ray is having no trouble reading the glyph
table, but it can't read the character map for anything; not in this
font, anyway.

I can provide a copy of the font in question upon request.

Additional (but irrelevant) information about my system: I am running a
Pentium 166 (why yes, it *is* slow) with 32MB of RAM. (The font file is
under 10K in size, so memory is not a concern.) There are several
gigabytes of free hard disk space.

My guess about this bug is that POV-Ray is looking for a part of the
font file that doesn't need to exist in order to have a working font.
(However, if anyone can tell me what's still missing, and what I can do
to add that information to the font, I'd be most grateful.) It should be
able to check the character map without trouble, but something is
throwing it off.
It should be noted again that this font file works perfectly in all
other applications; only in POV-Ray have I had a problem with it.

Thanks in advance for any help or advice that can be offered regarding
this bug.

Lummox JR

Post a reply to this message