Replace KcmFontinst with kio_fonts
greeneg at student.gvsu.edu
Thu Mar 13 05:33:56 GMT 2003
-----BEGIN PGP SIGNED MESSAGE-----
On Wednesday 12 March 2003 5:05 am, Craig Drummond wrote:
> > > I disagree, this is the way both Windows and Mac install and manage
> > fonts
> > > (drag them into a folder, delete them from the folder), and it is very
> > > intuitive and simple for the average person to do, as well as what they
> > a
> > re
> > > used to. Users should not have to worry about TrueType vs. Type1, or
> > have
> > > to go through an install wizard, or other such nonsense.
> > if the kcm module is set up the way you propose, then maybe...
> > The only problem I see is the n00b breaking his font system by adding
> > ttfs to
> > his type1 directory and vice versa.
> This woulnd't break anything - there is no point in separting the fonts
> into different directories based upon type. KcmFontinst and kio_fonts will
> handle mixed font types in the same dir, it has its own mechanism for
> creatnig fonts.dir and fonts.scale (it doesn't use mkfontdir, ttmkfdir, or
Actually this is wrong. On some distributions (I can think of two right off
the bat: Mandrake and SuSE) the font cache and scale files are generated by
the system level config tools (drakefont amd SuSEConfig respectively). These
applications are designed to have the different font types in their own
Gary L. Greene, Jr.
Sent from uriel.gvsu.edu
00:30:34 up 1:45, 2 users, load average: 1.62, 0.38, 0.16
Founder and president of the Grand Valley Linux Users Group.
Chief Systems Architect, S4, Inc. - OS Department.
Project Lead for the Sentinel Linux OS Project (KOMODO)
PHONE : 331-0562
EMAIL : greeneg at student.gvsu.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the kde-core-devel