Replace KcmFontinst with kio_fonts
Craig.Drummond at gmx.net
Tue Mar 11 20:46:20 GMT 2003
On Tuesday 11 Mar 2003 20:37, Andras Mantia wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 2003. March 11., Tuesday 22:21, Craig Drummond wrote:
> > The KControl module tries to also configure Ghostscript
> > and StarOffice - but I don't think this is neccessary, and just adds
> > bloat (please see my original email).
> For some of us, it's still important. I have documents that I can open only
> in StarOffice, but not in OpenOffice. :-( Newer OpenOffices may help, but
> it's too big piece of software to update it regullary. I would say that the
> new kio fonts based font install should replace the kcm module, only if it
> provides all the functionality that was present in the old one. BTW, can it
> do the trick with Disable/Enable the fonts (and thus recreating the needed
Not really. to "enable"/"disable" fonts you'd have to make them "hidden" -
i.e. named (e.g.) .times.ttf I suppose this could be done using the
"special" command for ioslaves - but I'm not sure how to do this.
> config files) after the distro config tool breaks the installations? ;-) In
> my case after installing a new package and running SuSEConfig, I had no
> anti-aliased fonts. I had to disable and re-enable the TrueType fonts.
Well this is a bug with SuSEConfig.
More information about the kde-core-devel