[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 77280] font installer cannot install fonts that have no
From:       Craig Drummond <Craig.Drummond () gmx ! net>
Date:       2004-03-31 21:24:30
Message-ID: 20040331212430.5593.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=77280      




------- Additional Comments From Craig.Drummond gmx net  2004-03-31 23:24 -------
> ------- Additional Comments From matze stud fbi fh-darmstadt de  2004-03-31
> 21:47 ------- As the fonts are on a local disk they don't need to be
> "downloaded". As they are Type1, there should be no problem with detecting

But then you have differences between copying from different protocols.
> the mimetype. But kfontinst does not even _try_ to install them. As soon as
> I select them in the filedialog and hit return, it tells me that it cannot
> install them because they're not Type1 or TTF. No fonts:/ involved up to

But kcmfontinst is *just* a front end to fonts:/ I suppose I could (in the 
case of a file:/ url) copy the font to a temp folder, rename it 
<font>.pfa/pfb - and then copy to fonts:/. But this seems a lot of work for a 
not very common scenario.

> here. If I rename them and add .pfb, it is actually installing them. Why
> should the name of the file make a differences?

For one its a quick and easy way of detemining the font type.
[prev in list] [next in list] [prev in thread] [next in thread]