[Xapian-discuss] Powered by Xapian

[Daniel Ménard]

James Aylett a écrit :
> This is correct. (While IANAL, I've had to deal with font licensing
> before.) What tends to happen is that the font files are licensed, and
> that license includes permission to create renderings.
>
> SVG typically will just reference the font, but of course you can
> generate outlines of the font rendering as proposed. This will in
> general produce lower quality bitmap renderings than by working with
> the original font, because of the lack of things like hinting and
> kerning information.
>   
If if understand correctly, it would mean that the "Drupal approch" is 
acceptable.
>> Legally it may be fine to provide an SVG version, but it's unambiguously
>> safe to use a freely licensed font, and it's certainly philosophically
>> more consistent.  So I think that's probably my preference if we can
>> find one which looks good with the logo.
>>     
>
> I'm not wild about the font we have at the moment anyway. I will note
> that lots of suitably-free fonts aren't actually very good. There are
> lots of fonts that aren't strictly OSS, but have licenses sufficiently
> permissive that they can be used by anyone; some of these are pretty
> good.
>   
For me, the problem is to choose one...
If you have some candidates, I can render some graphics so we can see if 
they look good with the logo.

>>> Last : I don't know what are the most useful sizes/formats to offer to 
>>> users.
>>> If anybody have any hint/recommendation, it would help (for now I've 
>>> just taken multiples of 2 for the height: 16, 32, 64, 128 and 256 px).
>>>       
>
> They feel very techie-orientated. I don't know any designers who'd
> naturally chose those kinds of grids. It may be worth looking at the
> IAB ad sizes guidelines (currently
> <http://www.iab.net/iab_products_and_industry_services/1421/1443/1452>)
> for button sizes. 
>   
Good suggestion, I will check.

Thanks,

Daniel