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