1 |
On 1 March 2015 at 23:36, Guilherme Amadio <amadio@g.o> wrote: |
2 |
> On Sun, Mar 01, 2015 at 08:59:38PM +0800, Ben de Groot wrote: |
3 |
>> On 28 February 2015 at 19:52, Michael Orlitzky <mjo@g.o> wrote: |
4 |
>> > On 02/28/2015 01:47 AM, Ben de Groot wrote: |
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.) |
26 |
>> > |
27 |
>> > |
28 |
>> |
29 |
>> Actually, after thinking about it some more, and doing some more |
30 |
>> research, I think this approach is unnecessary. Unless someone can |
31 |
>> tell me otherwise, I don't think we have any software that can handle |
32 |
>> truetype fonts but not opentype fonts. Most if not all of these |
33 |
>> packages use media-libs/freetype, which displays both formats just |
34 |
>> fine. So when we have font packages that offer both ttf and otf, then |
35 |
>> we should just install the superior format, which is OpenType. |
36 |
>> |
37 |
>> For packages that only offer one format, we install that format. |
38 |
>> |
39 |
>> Webfonts are also not an issue, as they are simply repackaged OpenType |
40 |
>> fonts aimed at web delivery. But most web developers use third party |
41 |
>> CDNs for that, such as Google Fonts. For the very few people who want |
42 |
>> to serve WOFF fonts from their own websites, I'm sure they can locate |
43 |
>> them as necessary. |
44 |
>> |
45 |
>> And webfonts are not useful for clients. Users should simply install |
46 |
>> the otf (or ttf) format of those fonts locally, and they will be |
47 |
>> picked up instead of the webfonts. |
48 |
>> |
49 |
>> Summarized, I propose the following policy: |
50 |
>> |
51 |
>> 1. If there is a choice of formats between otf and ttf, install only otf. |
52 |
>> 2. Do not install webfonts. |
53 |
> |
54 |
> I agree with your policy, but I think it's still a good idea to offer a |
55 |
> mechanism to install the other formats for those who need it, maybe via |
56 |
> truetype and woff or webfont USE flags. LaTeX, for example, may not be |
57 |
> able to use OpenType fonts, unless you use XeTeX, or other newer |
58 |
> variant, and sometimes a package you may want to use is only available |
59 |
> for plain LaTeX or PDFTeX (pst-solides3d and pstricks come to mind). |
60 |
> |
61 |
> We could have global USE flags for each popular font format, turn on the |
62 |
> flag for OpenType by default, and let users choose extra formats they |
63 |
> want. Another thing we might want to work on is on a way to convert |
64 |
> fonts for use with legacy LaTeX software that can't use OpenType files. |
65 |
|
66 |
Alexis, can you shed some light on this from the TeX side? What font |
67 |
formats can be used by various TeX packages? |
68 |
|
69 |
-- |
70 |
Cheers, |
71 |
|
72 |
Ben | yngwin |
73 |
Gentoo developer |