I use povray 3.6 under Debian Linux. I see timrom.ttf in the include directory,
but if I simply #include timrom.ttf I get an error, since this is not a text
file. But if I try to use the text command as follows

text {
ttf "timrom.ttf" ...

I get

Parse Error: Cannot open font file.

What did I miss? Thanks.

David

Post a reply to this message

Le 11/05/2012 04:27, David J Bush a écrit :
> I use povray 3.6 under Debian Linux. I see timrom.ttf in the include directory,
> but if I simply #include timrom.ttf I get an error, since this is not a text
> file. But if I try to use the text command as follows
> 
> text {
> ttf "timrom.ttf" ...
> 
> I get
> 
> Parse Error: Cannot open font file.
> 
> What did I miss? Thanks.
> 
> David
> 
> 


Please check your debian-installation: they might have moved the
timrom.ttf out of the expected -L paths in system povray ini file.
(traditional variation is /usr or /usr/local ... distro repackaging sucks)

Quick fix: in your povray.ini ( $HOME/.povray/3.6/povray.ini IIRC), add
line:
-L<path to the directory where timrom.ttf is>


I/O restriction might also be on the way, but it is something I never
use. (I compile my povray myself, so I can disable it)

Post a reply to this message

Le_Forgeron <lef### [at] freefr> wrote:
> Le 11/05/2012 04:27, David J Bush a écrit :
> > I use povray 3.6 under Debian Linux. I see timrom.ttf in the include directory,
> > but if I simply #include timrom.ttf I get an error, since this is not a text
> > file. But if I try to use the text command as follows
> >
> > text {
> > ttf "timrom.ttf" ...
> >
> > I get
> >
> > Parse Error: Cannot open font file.
> >
> > What did I miss? Thanks.
> >
> > David
> >
> >
>
>
> Please check your debian-installation: they might have moved the
> timrom.ttf out of the expected -L paths in system povray ini file.
> (traditional variation is /usr or /usr/local ... distro repackaging sucks)
>
> Quick fix: in your povray.ini ( $HOME/.povray/3.6/povray.ini IIRC), add
> line:
> -L<path to the directory where timrom.ttf is>
>
>
> I/O restriction might also be on the way, but it is something I never
> use. (I compile my povray myself, so I can disable it)

I appreciate your help!

When I use the verbose option, povray tells me, before it looks at the input
file, that it uses the library path /usr/share/povray/include, which contains
the ttf files and everything else I should need. I tried cyrvetic.ttf with the
same error. I even ran sudo povray to avoid any read restrictions. No change.

The documentation says "any [true type] font will do." How might I go about
installing some other ttf file?

If I have to, I could define my own "font" built from primitives, but talk about
a kludge! Everything else seems to work well. Could this really be a bug in the
Debian distro?

Post a reply to this message

David J Bush <twi### [at] cstonenet> wrote:
> When I use the verbose option, povray tells me, before it looks at the input
> file, that it uses the library path /usr/share/povray/include, which contains
> the ttf files and everything else I should need. I tried cyrvetic.ttf with the
> same error. I even ran sudo povray to avoid any read restrictions. No change.

  If nothing else helps, make a soft link in the same directory as the pov
file you are using that points to the ttf font you want to use. Such as
for example:

    ln -s /usr/share/povray/include timrom.ttf .

-- 
                                                          - Warp

Post a reply to this message

Le 11/05/2012 14:56, David J Bush a écrit :

> I even ran sudo povray to avoid any read restrictions

WARNING !

povray I/O restriction are not managed by the system, but by povray
itself. Being run as root does not change that mechanism. (at
best/worst, it might change the accessibility of files & folder for the
program, but it won't stop povray from denying the access)

If Warp's answer is useful (having a symlink in the local directory),
then you have to learn how to get the right behavior from I/O
restrictions in the config file of povray.

Post a reply to this message

I found the problem. I typed in .tff instead of .ttf

How embarrassing.

Thanks for your advice and attention!

Post a reply to this message