nanogui: Thread: Can not find fonts.

I grabbed the latest version from the CVS and the latest stable version
fo Freetype2
I built and installed Freetype to on my test system then I compiled the
the CVS version of Nano-X
Here is the problem. When I ran my program that was working using
Freetype1 I now get font not found.
I am passing the entire path of the font and when it reports back that
it can not open the font it includes the path and a , and then the point
size.
I put the older verison of nano back on the system and it works just fine.
Any ideas?

: Here is the problem. When I ran my program that was working using
: Freetype1 I now get font not found.

You're saying that you were using FT1, and now you're
using FT2, and it's not working, right?



: I am passing the entire path of the font and when it reports back that
: it can not open the font it includes the path and a , and then the point
: size.

I would nonetheless set the path prefix for freetype in the 
nano-X config file, perhaps there's something strange going
on here.  Also, run the src/fontdemo*.sh scripts, they use
freetype and will use the freetype fonts in the src/fonts
directory, which the config also defaults to (using non-absolute
paths).

Regards,

Greg

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greg Haerr wrote:
> : Here is the problem. When I ran my program that was working using
> : Freetype1 I now get font not found.
> 
> You're saying that you were using FT1, and now you're
> using FT2, and it's not working, right?
Correct. Works just fine with the build of mano-X that used FT1
I am including the full path of the font in the createfont command. That
should override the font path in the config correct?

> 
> 
> 
> : I am passing the entire path of the font and when it reports back that
> : it can not open the font it includes the path and a , and then the point
> : size.
> 
> I would nonetheless set the path prefix for freetype in the 
> nano-X config file, perhaps there's something strange going
> on here.  Also, run the src/fontdemo*.sh scripts, they use
> freetype and will use the freetype fonts in the src/fonts
> directory, which the config also defaults to (using non-absolute
> paths).
> 
> Regards,
> 
> Greg
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-nr1 (Windows XP)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEVAwUBR1BFEOLnn4qAcbUGAQIbdggAg6+sgbLv/Wl/oa62N1aj4f58ypHBJXgk
Xiz1rKzW7u4fUJf56b62Wlc2UuTPBrLgIQJoJB2sAbQxwD0LHFgbZGZ4t1e9ljI0
D5VMHRxTpePO0ZHU83fbdJ4kyKsshN+/Vgxv/NFdN7H9TS1s2P7xTBE7RsDcj/c1
XZRjiwvXATurB5cRP3ZnwHOOyaLAtoahf/tE/fkaBO9VuYe1O7MybApJ7UBORECS
K1YZ4LGQLeGtFFOq2skMEAlOWUiFgWSFSPcqcTPnVQxeui/hC7aGP69hLVVn3mV7
tRfXaEc/2VY/s1hhrNnhmVgIkBTO9ckaBYrVQU7TDOZo1zKRQO7SEg==
=Yr/I
-----END PGP SIGNATURE-----

: I am including the full path of the font in the createfont command. That
: should override the font path in the config correct?

Yes.  Perhaps that's a bug with the FT2 driver... ?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Okay I set the directory to "/usr/share/fonts/truetype" under the
Freetype 1.x section.
I set nano-x to use truetype-2.
I made sure that a copy of the font VeraBd.tff was in that directroy.
When I run my program I get this error


fnt_fontcreate: VeraBd.ttf , 14 not found

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-nr1 (Windows XP)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEVAwUBR1B1yeLnn4qAcbUGAQLBmwf/aP7/P4GpkJ1NMS8AxOWn48nTkXk6ZPBk
CvV4TukrgYFvhRj+XBzZibvzPXnZaahaypAeLybopruxPGhzVObu/xvTiqKaM17R
m8yPAJRwl9Tvg8EisY1uoijLHe12OJ/pyxyw9RqkBKYcrD8B4FuBzHBBDpKKm3TQ
j9w6k6DoAV/z+9jbYYfw2m0d2Q1Vkvrsjrlg1chGluCu1BWNOZJkkvs613G4zZiz
J7U3vJHRjXL73ke4RPfyV9p6sWJ05OCpcRBSV61m8WQ8v7gd5vBjRlmLxgsNGppj
v4SGWICRrJnPKtWDEbTbRvUpcdGb8MvNIM7/nCCMZwMTWFALLe6qPg==
=5gQi
-----END PGP SIGNATURE-----

: fnt_fontcreate: VeraBd.ttf , 14 not found

This means that the "nano-X format .FNT font" subdriver
didn't find the .ttf font, which it shouldn't.  So this isn't an
error.  Your font was likely selected and worked using
the ft_ driver.

I have a patch to change this printf behaviour, which I'll 
apply, to make things less confusing.  If you turn off
FNT fonts in the config file, this won't display.

Regards,

Greg

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greg Haerr wrote:
> : fnt_fontcreate: VeraBd.ttf , 14 not found
> 
> This means that the "nano-X format .FNT font" subdriver
> didn't find the .ttf font, which it shouldn't.  So this isn't an
> error.  Your font was likely selected and worked using
> the ft_ driver.
> 
> I have a patch to change this printf behaviour, which I'll 
> apply, to make things less confusing.  If you turn off
> FNT fonts in the config file, this won't display.
> 
> Regards,
> 
> Greg
> 
> 
> 
Okay but it isn't rendering any text as well as getting that error.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-nr1 (Windows XP)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEVAwUBR1CD1OLnn4qAcbUGAQLNwgf8DtQwUBqjBhNJ8WBN1gGSwFNpHGd2hhjR
tDNPuIwjxUVwowrJPW+IgagV8V3WB/ynzLdD8l5AxZb0w/UPDgmYfDEUYk4iMUGU
0YyBQ8BxwdgZgY8sOYqsTYUqpIfcYvfP+lS3zq0Cw2mcVF/nhnRRWiAq98kTX5YO
QKroAYLW73f0n90HxCnGrKWxlkC1wz4iqg6OfjwnznbIe6Hj3mSjJMSebXzddNvA
FQ1dlCwPLQMzxDaI45Fh8sIbbubSEkVpD9Lf/rKKDhhwzzQM9Pyp7kI0oPQ2Bj5V
tsBa/p/dm+/JaWMBOpjl6bPfsF2oGqlrKWOgEZutAm+6K0HilNAhOA==
=v9nX
-----END PGP SIGNATURE-----

I think this error means that the file was fond but the size 14 was not.
Are you trying to use size 14?
The problem is that the TTF fonts are rendered and the files themselves
do not contain sizes.
Are you using the latest patches.
I thought this was fixed recently.
Martin


-----Original Message-----
From: David Siebert ####@####.#### 
Sent: Friday, November 30, 2007 1:43 PM
To: Greg Haerr
Cc: ####@####.####
Subject: Re: [nanogui] Can not find fonts.

Greg Haerr wrote:
> : fnt_fontcreate: VeraBd.ttf , 14 not found
> 
> This means that the "nano-X format .FNT font" subdriver didn't find 
> the .ttf font, which it shouldn't.  So this isn't an error.  Your font

> was likely selected and worked using the ft_ driver.
> 
> I have a patch to change this printf behaviour, which I'll apply, to 
> make things less confusing.  If you turn off FNT fonts in the config 
> file, this won't display.
> 
Okay but it isn't rendering any text as well as getting that error.

: Okay but it isn't rendering any text as well as getting that error.

So you're saying that the fontdemo*.sh scripts don't
show any text?  Lets start with known working demos,
then move to your code.

Regards,

Greg

> I think this error means that the file was fond but the size 14 was not.

No, this is showing that size 14 VearBd.ttf is being requested.


> The problem is that the TTF fonts are rendered and the files themselves
do not contain sizes.

There's a DPRINTF that can be changed to a printf in
engine/devfont.c::GdCreateFont for the freetype driver.
This will show whether the freetype driver accepted the
font path string.

> Are you using the latest patches.  I thought this was fixed recently.

I fixed NXLIB issues with ttf fonts, that had to do with matching
XLFD strings in the fonts.dir file.  The other fix, a couple of
months prior,  was implementing support for later versions
for freetype, including 2.3.5.  The issues there were related to
not rotating properly, and having to have caching turned off
for certain versions of FT2.

Regards,

Greg




Greg Haerr wrote:
> : fnt_fontcreate: VeraBd.ttf , 14 not found
> 
> This means that the "nano-X format .FNT font" subdriver didn't find 
> the .ttf font, which it shouldn't.  So this isn't an error.  Your font

> was likely selected and worked using the ft_ driver.
> 
> I have a patch to change this printf behaviour, which I'll apply, to 
> make things less confusing.  If you turn off FNT fonts in the config 
> file, this won't display.
> 
Okay but it isn't rendering any text as well as getting that error.