In article <20090706092842.4389c...@trite.i.flarn.net.i.flarn.net>, Rob
Kendrick <r...@netsurf-browser.org> wrote:
> On Mon, 06 Jul 2009 07:01:42 +0100 Dave Symes <d...@triffid.co.uk>
> wrote:

> > In article <20090706003522.53717...@trite.i.flarn.net.i.flarn.net>,
> >    Rob Kendrick <r...@netsurf-browser.org> wrote:
> > > On Sun, 5 Jul 2009 21:03:02 +0100 Mike Hobbs
> > > <mike.ho...@antplc.com> wrote:
> > 
> > > > And all this trouble seems to be over fonts which NetSurf is
> > > > never likely to use.
> > 
> > > But NetSurf doesn't know this unless it scans them.  The solution
> > > to people swapping their sets of fonts all the time is to remove
> > > the reason for them swapping fonts all the time.

> > Could you expand on that a bit Rob... Not quite sure what you meant?

> I'm not sure how; I don't understand why people swap their fonts
> around. 

To make use of them?

I don't understand how anyone can manage with (a) only a handful of font
families, and (b) everything they produce looking 'the same'.  :-)

With hundreds of magpied font families, some may only be used once or
never, for a specific (printed on paper) document or to create a web
image. You use a font manager to avoid having hundreds of seldom-used
decorative and blackletter fonts active all the time and consequent
slowness and HUGE font menus in programs such as (insert name of any
program which allows you to select a font). I would imagine that if I
didn't swap active fonts around, and had them all active all the time,
NetSurf would take at least three eons to scan them all several times
every day and other software would explode, as would my brain.  ;-)

I have tried it now: my usual active collection on Myonix takes a few
mere seconds to be scanned. It has just taken 15 minutes to scan all 200
or so families and the NetSurf font picker is 40 screens high.

Soft loading RISC OS 5.15 at boot seems always to cause NetSurf to
re-scan fonts (don't get me wrong; this is not a major issue to me - I
don't mind it scanning my active fonts!). 

If I load an old document by dropping it on my font manager to
auto-activate the (probably decorative) fonts it contains the next load
of NetSurf (RUfl?) detects the change and it then chunters though the
font scanning doo-dad again. Again, not a problem with only a few active
fonts. 

> As soon as somebody works out why, perhaps they could put some
> effort into removing the reasons.

I don't imagine many people will change the way they work.

Too many (not that many) active fonts results in very long and unwieldy
font menus and general font related slowness. So, would somebody please
re-write every app which has a font menu to provide instead a standard
interface to my font collection ordered by the arbitrary groups I keep
them in. i.e. detect the next font I select with EasyFontPro and use that.

It appears there is an "incompatibility" between NetSurf's approach and
font managers which hide the bulk of your collection from the font$path.
It seems that RUfl assumes we don't change the 'active' selection more
often than its developer changes his.  ;-)

For all the font scanning, though, I have a font Inkburrow but NetSurf
doesn't use it even though it's active and here in h1:
http://www.sarva.co.uk/style.css
A different font issue methinks but ironic that NetSurf has bothered to
scan this active font but isn't able to use it, except maybe if it has
unique unicode characters to substitute elsewhere.


Reply via email to