Comment 12 for bug 535582

Arne Goetje [2010-04-15 14:02 -0000]:
> Please replace the ttf-kacst package with ttf-kacst-one in the seeds.

Will do once it builds (it was dep-wait on python-fontforge; promoted

ttf-kacst is 940 kB, while t-k-one is just a mere 33 kB. Is that

> In addition to the ttf-indic-fonts-core package, please also seed
> ttf-punjabi-fonts, since that one only contains 2 fonts and therefor it
> doesn't make sense to move them into ttf-indic-fonts-core.

Seeded. (It's tiny)

> How is the space situation?

695 MiB ATM, and we have 4 (amd64)/6 (i386) langpacks. I. e. "full"
and "removing even more langpacks would be really bad".

> Do we need to split the ttf-thai-tlwg and ttf-khmeros packages?

We don't ship ttf-khmeros at all right now. ttf-thai-tlwg is 3 MB, so
if that can be reduced it would certainly be nice. But I don't think
it should happen for lucid still: We have bigger fish to fry right now
and don't want to introduce a potential font support regression just
to save 1 or 2 MB (which wouldn't even be enough for a new langpack).
For maverick and onwards it's a nice potential space saving, though,
if/when we are back in CD space trouble. So we should certainly shelve
this idea, thanks!

> ttf-takao-gothic has not been uploaded into Debian yet, but I could get
> it from the svn on alioth... however, that package is quite large (12MB)
> , as it contains 3 fonts, of which we only need one for the LiveCD. So,
> I can split that package into -core and -extra and prepare it for
> upload, if you agree. (That would replace the ttf-vlgothic package in
> the seeds.)

ttf-vlgothic is indeed a hog (5 MB); how big is the one font that we
need from ttf-takao-gothic? How much different are they compared to
the two in ttf-vlgothic?

3852276 VL-Gothic-Regular.ttf
3974300 VL-PGothic-Regular.ttf

Could we split out/drop one of them to get a similar effect?



Martin Pitt |
Ubuntu Developer ( | Debian Developer (