Replace KcmFontinst with kio_fonts

[Neil Stevens]

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

On Monday March 17, 2003 12:17, Vadim Plessky wrote:
> On Sunday 16 March 2003 23:03, George Staikos wrote:
> |  On Sunday 16 March 2003 14:17, Vadim Plessky wrote:
> |  > |  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.
> |
> |      That's impossible.  Not all platforms even have XFree86, let
> | alone the fact that upgrading XFree86 just isn't always possible.
>
> So, you think we should sacrifice KDE functionality and usability in
> favour of compatibility with, say, Solaris?
>
> AFAIK, FreeBSD uses XFree86, as well as Linux.
> Besides, XiGraphics implemented Xrender in their (closed-source) X
> server, so what do we really talking about here?..

"Linux" is not tied to any one XFree86.  Different OSes that use linux have 
different X servers.  And even OSes that use XFree don't necessarly run 
and use the newest, compatibility-breaking, unstable XFree release.  And 
users of the OSes that do don't necessarily run out and grab the newest 
versions of their OS.

KDE is capable of supporting different systems without sacrificing 
features.  Craig Drummond already said that he can support different font 
systems.  So to do what you say, to tie KDE to one X server, would be to 
sacrifice functionality, not to add any.

- -- 
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)

iD4DBQE+di3rf7mnligQOmERAh4JAJ9A7f+lOkJhmIQnf1jsnkETmtQDsQCYiMFF
Lnr05F4IJv7SRGzcdTcIew==
=4nff
-----END PGP SIGNATURE-----