This is driving me bonkers. I got xfstt working when I was using 6.1. I decided to install it again to get better fonts with Netscape. Here's where I am. I put a bunch ot tt fonts in /usr/share/fonts/truetype. I installed xfstt. I ran (as root) xfstt --sync and xfstt & before starting X. In X as root, when I try xset fp+ unix/:7100 LInux replies xset: bad font path element (#38), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax I've gotten this question answered before, but damned if I can find the answer now. Any help will be appreciated. -- Kenneth R. Kellum -- San Jose State University This life is a test. It is only a test. If this was a real life, I would have been given instructions on where to go and what to do. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Kenneth Kellum wrote:
This is driving me bonkers. I got xfstt working when I was using 6.1. I decided to install it again to get better fonts with Netscape.
Here's where I am.
I put a bunch ot tt fonts in /usr/share/fonts/truetype. I installed xfstt. I ran (as root) xfstt --sync and xfstt & before starting X. In X as root, when I try xset fp+ unix/:7100 LInux replies
xset: bad font path element (#38), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax
I've gotten this question answered before, but damned if I can find the answer now.
Any help will be appreciated.
I am currently experimenting with xfsft, there is a config file /etc/xfs.conf that contains a line that points to your fonts: /usr/X11R6/lib/X11/fonts/TrueType in my case well, I do not need to talk about permissions... ;-) for the missing font.dir, I use a file called fonts.scale that contains the font descriptions versus the font file the font is in (I need to extract them using a tool). Anything wrong with that setup? my xset command reads slightly different: Žxset fp+ tcp/localhost:7100Ž (hope I didn't make a fool out of me with that last statement, I don't know what it means, but it works in my case) Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Fri, 14 Jan 2000, Juergen Braukmann wrote:
Kenneth Kellum wrote:
This is driving me bonkers. I got xfstt working when I was using 6.1. I decided to install it again to get better fonts with Netscape.
Here's where I am.
I put a bunch ot tt fonts in /usr/share/fonts/truetype. I installed xfstt. I ran (as root) xfstt --sync and xfstt & before starting X. In X as root, when I try xset fp+ unix/:7100 LInux replies
xset: bad font path element (#38), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax
I've gotten this question answered before, but damned if I can find the answer now.
Any help will be appreciated.
I am currently experimenting with xfsft, there is a config file /etc/xfs.conf
Interesting. There's no such file on my system.
that contains a line that points to your fonts: /usr/X11R6/lib/X11/fonts/TrueType in my case
well, I do not need to talk about permissions... ;-)
for the missing font.dir, I use a file called fonts.scale that contains the font descriptions versus the font file the font is in (I need to extract them using a tool).
Which tool? I seem to recall that when I did this before I did something to create fonts.dir. It's not there now and I can't remember. Thanks
Anything wrong with that setup?
my xset command reads slightly different: Žxset fp+ tcp/localhost:7100Ž (hope I didn't make a fool out of me with that last statement, I don't know what it means, but it works in my case)
Juergen
-- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- Kenneth R. Kellum -- San Jose State University This life is a test. It is only a test. If this was a real life, I would have been given instructions on where to go and what to do. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Kenneth Kellum wrote:
On Fri, 14 Jan 2000, Juergen Braukmann wrote:
Kenneth Kellum wrote:
[...]
Any help will be appreciated.
I am currently experimenting with xfsft, there is a config file /etc/xfs.conf
Interesting. There's no such file on my system.
that contains a line that points to your fonts: /usr/X11R6/lib/X11/fonts/TrueType in my case
well, I do not need to talk about permissions... ;-)
for the missing font.dir, I use a file called fonts.scale that contains the font descriptions versus the font file the font is in (I need to extract them using a tool).
After a very *deep* depression yesterday (I tried to dokument what I did and add a few fonts) I found more and more unsolved questions and didn't know what I did to get it running. the tool I meant is ttmkfdir, but I think it's nessesarry for xfsft ttmkfdir by Jörg Pomnitz http://www.darmstadt.gmd.de/~pommnitz/TrueType/xfsft.html My article tells something about mkfontdir (this tool comes with SuSE, a modified[?] version comes with xfsft) to generate a fonts.dir file that is (according to the man page) needed by the server) And that was one of the misleading points im my article that drove me mad. I learned that it's a very good idea to restart the fontserver, or even as I learned even more with netscape restart X. (init 2, init 3). Juergen
Which tool? I seem to recall that when I did this before I did something to create fonts.dir. It's not there now and I can't remember.
Thanks
Anything wrong with that setup?
my xset command reads slightly different: Žxset fp+ tcp/localhost:7100Ž (hope I didn't make a fool out of me with that last statement, I don't know what it means, but it works in my case)
Juergen
-- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Fri, Jan 14, 2000 at 06:03:31AM -0800, Kenneth Kellum wrote:
This is driving me bonkers. I got xfstt working when I was using 6.1. I decided to install it again to get better fonts with Netscape.
Here's where I am.
I put a bunch ot tt fonts in /usr/share/fonts/truetype. I installed xfstt. I ran (as root) xfstt --sync and xfstt & before starting X. In X as root, when I try xset fp+ unix/:7100 LInux replies
xset: bad font path element (#38), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax
Now with all these details given, I think I know the answer. From version 0.9.99 on, xfstt changed the port from 7100 to 7101 to avoid interference problems with xfs. It's explained in the tarball but if you installed from rpm then the explanation probably is lost. (Digression: This is a typical example of the problems which arise with installation from -rpm or other- binaries, a la Windows. Unfortunately, due to popular demand, we are going at full speed in that direction. At the end I'm afraid that Linux will not be anything better, or significantly different from the Redmond beast - but that's a different story). -- # \\\|/// # (-@-@-) # ====oOO==(_)==OOo========================================== # Andrei Mircea <mircea.andrei@wanadoo.fr> # .oooO Oooo. Yerres (91) FRANCE # ====( )==( )=========================================== # \ ( ) / # \_) (_/ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Fri, 14 Jan 2000, Andrei Mircea wrote:
On Fri, Jan 14, 2000 at 06:03:31AM -0800, Kenneth Kellum wrote:
This is driving me bonkers. I got xfstt working when I was using 6.1. I decided to install it again to get better fonts with Netscape.
Here's where I am.
I put a bunch ot tt fonts in /usr/share/fonts/truetype. I installed xfstt. I ran (as root) xfstt --sync and xfstt & before starting X. In X as root, when I try xset fp+ unix/:7100 LInux replies
xset: bad font path element (#38), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax
Now with all these details given, I think I know the answer. From version 0.9.99 on, xfstt changed the port from 7100 to 7101 to avoid interference problems with xfs.
Using "7101" I get exactly the same error.
It's explained in the tarball but if you installed from rpm then the explanation probably is lost.
I can't blame rpm's. I downloaded the tarball and missed this in the docs. To paraphrase Walt Kelly "I have met the enemy and he is me." Thanks much.
(Digression: This is a typical example of the problems which arise > with installation from -rpm or other- binaries, a la Windows. Unfortunately, due to popular demand, we are going at full speed in that direction. At the end I'm afraid that Linux will not be anything better, or significantly different from the Redmond beast - but that's a different story).
-- # \\\|/// # (-@-@-) # ====oOO==(_)==OOo========================================== # Andrei Mircea <mircea.andrei@wanadoo.fr> # .oooO Oooo. Yerres (91) FRANCE # ====( )==( )=========================================== # \ ( ) / # \_) (_/
-- Kenneth R. Kellum -- San Jose State University This life is a test. It is only a test. If this was a real life, I would have been given instructions on where to go and what to do. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Andrei Mircea wrote:
(Digression: This is a typical example of the problems which arise with installation from -rpm or other- binaries, a la Windows. Unfortunately, due to popular demand, we are going at full speed in that direction. At the end I'm afraid that Linux will not be anything better, or significantly different from the Redmond beast - but that's a different story).
In this respect I think rpm distribution is slightly inferior, since Windows products often have, as an installation option, the ability to read the pertinente README file. That would be a nice feature to have in rpm installations and would answer your valid concerns. Paul Abrahams -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I'm resending this under a more appropriate subject line. Andrei Mircea wrote:
(Digression: This is a typical example of the problems which arise with installation from -rpm or other- binaries, a la Windows. Unfortunately, due to popular demand, we are going at full speed in that direction. At the end I'm afraid that Linux will not be anything better, or significantly different from the Redmond beast - but that's a different story).
In this respect I think rpm distribution is slightly inferior, since Windows products often have, as an installation option, the ability to read the pertinente README file. That would be a nice feature to have in rpm installations and would answer your valid concerns. Paul Abrahams -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (4)
-
abrahams＠mbs.valinet.com -
juergen.braukmann＠ruhr-west.de -
kkellum＠pacbell.net -
mircea.andrei＠wanadoo.fr