Re: Fonts in X [Off Topic]
On Wed, 22 Apr 1998, Stephen Carpenter wrote:
> Luiz Otavio L. Zorzella wrote:
>
> > Remco Blaakmeer writes:
>
> > > It is probably illegal to use the fonts that come with Windows.
> >
> > Why? If you bought a Windows license, you bought a license for the
> > Windows components, I think.
>
> That sounds right to me....It is of course illegal to distribute the font
> thatcome with windows, well...I havn't actually looked to see if the
> windows fonts are available on any sort of "Free" licence...
> but... What are the chances of Micro$oft using any sort of free licence for
> anything?
>
> > Not being legal to use Windows fonts in Linux would be like being
> > illegal to buy Coke and using the jar to carry Oranje Juice...
>
> I think a better analogy might be "You buy a coke bu tbecause of thelicence
> agreement you have to drink the whole thing, you can't dump
> half of it out even if you don't like its flavor"
>
> > > To let the X server use the fonts, you can do:
> >
> > > $ xset fp+ tcp/localhost:7100
> >
>
> you can also edit /etc/XF86config and add the fontpath"unix:7100" (I think thats
> it don't have the docs in front of me...
> in any case it is in the xfstt docs from the tarball on sunsite)
> NB: if you do this..and reboot your machine you MUST
> run xfstt & ...if you do not have xfstt and you have this line in your
> XF86Config file...then X will refuse to start and exit with an error
Yes, I said that in the same post where I mentioned the xset command.
And BTW, you are right where you say that xfstt *must* be running if you
add the line to XF86Config. I just tried it. If a _directory_ in the
fontpath is missing or otherwise invalid, it is deleted from the fontpath.
But if a font server is not present, this is considered a fatal error and
the X server refuses to load. If you are using xdm to start X and the X
server refuses to start, you'll end up with a flashing screen caused by
the X server being started over and over again. If you ever encounter such
a problem, you can solve it by stopping xdm through a telnet connection or
trying to hit Ctrl-Alt-Del at a moment where the X server has stopped and
isn't yet being restarted and then booting into single user mode.
If nobody objects to it, I'll file bug reports for the following
annoyances I have encountered when X is misconfigured:
- If the X server fails to start, xdm seems to be restarting it
indefinitely. I'd say that if the X server is restarted too often too
fast, it should be disabled because it is obviously not working. Just like
init disables processes that are respawning too fast.
- If there is a non-existing font directory in xfs's config file, this is
a fatal error and xfs doesn't start at all, which causes my X server to
fail because it can't find its fonts, which is very annoying because I use
xdm.
- If there is a non-existing font server in the FontPath of an X server,
this is a fatal error and it refuses to start, which is annoying like I
said above. Of course, if the X server can't find the font 'fixed', it
should still fail to start.
Remco
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: