Re: Client fonts

I'm afraid I will not candidate there but would love hinting João if  
he can. My perspective is that of a content-provider though and I  
know that the browser-implementor's perspective is quite different.

For downloadable fonts, in particular, see the big bugzilla bug:
   http://bugzilla.mozilla.org/show_bug.cgi?id=52746

paul

PS: For my involvement, I'd rather work on the copy-and-paste area  
which seems to have found an amount of consensus but no real time-fuel.


Le 13 juil. 07 à 08:45, Charles McCathieNevile a écrit :
> João, Paul, are you interested in writing a more formal  
> specification? And in doing the work of asking browser developers  
> whether they have a need or desire for this, and are likely to  
> implement it?
>
> cheers
>
> Chaals
>
> On Tue, 10 Jul 2007 00:42:46 +0100, João Eiras  
> <joao.eiras@gmail.com> wrote:
>
>> There could be a collection, similar to navigator.plugins, which  
>> is navigator.fonts.
> ...
>> That collection would be bound to a read only array in ecmascript,  
>> on which method like join() could be used to get a quick list of  
>> all fonts.
>>
>> This can be immensely useful for any rte editor which runs on a  
>> browser.
>
>> Paul Libbrecht <paul@activemath.org> escreveu:
>>> Le 9 juil. 07 à 21:55, João Eiras a écrit :
>>>> Is there any proposed API to get information about installed fonts
>>>> in the client at runtime ? something like navigator.plugins or
>>>> navigator.mimeTypes
>>>
>>> I would largely second that!
>>> Even obtaining the metrics would be nice.
>>> Moreover, knowing if an installed font does have glyph-x or glyph-y
>>> (note: a unicode range availability is useless) should be.
>
>
> -- 
>   Charles McCathieNevile, Opera Software: Standards Group
>   hablo español  -  je parle français  -  jeg lærer norsk
> chaals@opera.com    Catch up: Speed Dial   http://opera.com
>