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

List:       kde-devel
Subject:    Re: Font installer, Xftconfig, Xfs, and CVS
From:       Eric Laffoon <sequitur () easystreet ! com>
Date:       2001-06-11 15:01:31
[Download RAW message or body]

On Monday 11 June 2001 07:11 am, Craig Drummond wrote:

> Hi,
>
> I think that I've almost finished my font installer KControl module.
>
> As part of the installing of fonts, the module can also edit XftConfig
> files - and will add each directory in the X fonts directory that
> contains TrueType or Type1 fonts to XftConfig. It also allows for other
> XftConfig parameters to be edited - exlcuding a range of point sizes
> from being anti-aliased, and enabling of sub-pixel hinting. I was also
> thinking of being able to add extra "rules" to the XftConfig file -
> such as font name substition. However, I'm not really sure that this
> sort of functionality belongs within a "font installer". Is this a good
> idea?

I expect there might be some wanting to limit it but font substitution was in 
the first XftConfig I saw as an example and it seems pretty useful. Whatever 
the arguments to keep it simple it seems to me simple is being able to use a 
common option with a tool vs reading the docs and hoping you don't make a 
typo with an editor.
>
> Other things to be added include support of Xfs config files - but as I
> don't use Xfs I'm not to sure about how to do this. i.e. which
> directories should be placed in the Xfs config file - the same as for
> XF86Config, or only those containing TrueType fonts? Plus, should
> Xf86Config also contain the directories listed in Xfs's config file?

I've used xfs for some time and (unless I'm missing something) it is 
functionally identical to where you list font directories in your XF86Config.
>
> Speedo fonts are always installed as iso8859-1 - is this OK? Should I
> use the locale instead? If not, how do I tell the encoding of a Speedo
> font? I realise that most people will not be installing Speedo fonts -
> but it'd be nice to be able to install them properly anyway.
>
> As a further point - I realise that it's too late for it to be included
> in 2.2 (plus I'm not sure if it's stable enough anyway) - but maybe it'
> s time that I placed the code into KDE's CVS, in the kdenonbeta module?
> Again, is this a good idea to do it now - or would it be better to wait
> a while (e.g. until I've added Xfs support)?

It would be great to have it in cvs. There is no reason I can see to wait to 
put it in kdenonbeta.
>
> Ciao
>
> Craig.
>
> p.s. Please send any email regarding kfontinst to cpdrummond@freeuk.com
> - and not my UKLinux account (because at the moment I can only access
> the UKLinux account at weekends...)
>
> p.p.s. The latest version of the code is http://www.cpdrummond.uklinux.
> net/kfontinst-new/kfontinst-0.10b3.tar.gz
>
> >> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<

-- 
Eric Laffoon                    sequitur@kde.org
A member of the Quanta+ Web development team
http://quanta.sourceforge.net
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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