Replace KcmFontinst with kio_fonts

[Neil Stevens]

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

On Sunday March 16, 2003 11:17, Vadim Plessky wrote:
> On Sunday 16 March 2003 20:46, Craig Drummond wrote:
> |  > As FontConfig is widely presented by now 9and would be on 95% of
> |  > desktops by KDE 3,2 release time), is there any reaosn to have
> |  > kio_fonts at all? I also think that current KControl module for
> |  > fonts configuration is somewhat overhead, as it was designed to
> |  > support legacy applications.
> |  >
> |  > You don't have something like this in case of FontConfig insatlled.
> |  > You just copy fonts to some folder (using Konqueror), that's it.
> |  > FC would fetch new fonts in 1sec. or so :-)
> |
> |  Yup I agree - if all systems and apps are using Fontconfig. As this
> | does both fontconfig, and standard X - what's the harm? It makes
> | exisiting and older apps work.
>
> We would (should) require XFree86 4.3.0 for KDE 3.2 release, as you
> won't get latest XRENDER and XCursors otherwise (not speaking about
> RandR) As FC is natural part of XF 4.3.0, I don't see how you can avoid
> installing it.

No, we shouldn't tie anything to one particular release of one particular X 
server.  Not unless you want to call this xfreefonts: protocol instead of 
fonts.

- -- 
Neil Stevens - neil at qualityassistant.com
"The shepherd drives the wolf from the sheep's throat, for which the
sheep thanks the shepherd as a liberator, while the wolf denounces him
for the same act as the destroyer of liberty." -- Abraham Lincoln
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+dNk0f7mnligQOmERAhJXAJ4ut58S1ZUwGQhTX1dP0NX0pbtdOwCcCQM5
CYKtO9pEK4J7OXZjtPrRXKU=
=79Jd
-----END PGP SIGNATURE-----