| 1 |
On 02/28/2015 01:47 AM, Ben de Groot wrote: |
| 2 |
>> |
| 3 |
>> Since this is mostly used for web developers, I recommend to leave it |
| 4 |
>> off for desktop users, but possibly on for servers, for example. |
| 5 |
> |
| 6 |
> If we do the use expand, we should leave it up for users to set. I |
| 7 |
> suggest we default to only otf, if there is a choice. Other formats |
| 8 |
> should not be installed by default, unless it's the only option for |
| 9 |
> that package. |
| 10 |
> |
| 11 |
|
| 12 |
This is going to get confusing fast -- please consider just installing |
| 13 |
everything by default. If you default to "only OTF," what happens when |
| 14 |
you install a foo-ttf package? Is it a no-op? What if there's a package |
| 15 |
that only ships WOFF files? A combination of TTF and WOFF? |
| 16 |
|
| 17 |
Most of the fonts are tiny and it's not worth the hassle to avoid a few |
| 18 |
kilobytes. It will also keep the eclass nice and clean. If you default |
| 19 |
to installing everything, then when a user goes out of his way to remove |
| 20 |
(say) WOFF, you can go ahead and just ignore WOFF files even if the |
| 21 |
result is something stupid like an empty package. |
| 22 |
|
| 23 |
(The webfonts might be useful for clients, by the way. If they're not |
| 24 |
installed locally, your browser downloads them on-demand and caches them |
| 25 |
for later use.) |
Archives