[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#133649: cm-super packaging



"JM" == Josselin Mouette <joss@debian.org> writes:

    JM> Le lun 10/02/2003 à 22:53, C.M. Connelly a écrit :
    >> FYI, these packages are going to be pretty big.  Without
    >> the AFMs, the package is around 57 MB,~59 MB installed .
    >> The AFM package will probably be a lot smaller, but the
    >> AFMs themselves are 53 MB ungzipped.

    JM> Isn't it possible to split out the different encodings ?
    JM> E.g. most users will want only the T1 fonts. IIRC it is
    JM> possible as different encodings are provided by different
    JM> font files and different map files.

Yes, you could split out the different encodings, but that isn't
really going to affect the number of Type 1 fonts you're going to
need.

The README file for CM-Super says

   Each Type 1 font program contains ALL glyphs from the following
   standard LaTeX font encodings: T1, TS1, T2A, T2B, T2C, X2, and
   also Adobe StandardEncoding (585 glyphs per non-SC font and 468
   glyphs per SC font)....

The different encodings are achieved using ``map'' files, which
say, basically, if TeX asks for font A, it's really font X, with
encoding E, so reencode the Type 1 font using encoding E.  So the line

   ecrm1000 SFRM1000 "T1Encoding ReEncodeFont" <cm-super-t1.enc <sfrm1000.pfb

(from cm-super-t1.map) says

   if TeX wants ecrm1000, use SFRM1000, which is the sfrm1000.pfb
   Type 1 PostScript font reencoded according to the rules in the
   cm-super-t1.enc encoding file.

So the encodings basically boil down to a couple of small text
files each (< 40 KB for both), splitting them out wouldn't help.

The package could be divided into font families, I guess, with
packages along the lines of

   core CM (EC) fonts
   weird CM fonts (Dunhill, Fibonacci, ``Funny Italic'')
   SliTeX fonts
   CM (EC) Concrete
   CM Bright

I'm not sure if the added complication would be worthwhile,
though, as you would then be placing the onus on the user to
actually know what these different font families were and which
ones they need to install.

My inclination is to just do two packages at first -- one with the
PFBs and TeX support files and one with the AFMs and any
mechanisms we need to get things to work with other applications.
If there's a demand for smaller packages, then we could look at
splitting things up a bit more.  Even if things are split up, the
core font package would be fairly large (around 388 fonts out of
the total of 409) so there might not be a significant savings in
disk space or download time no matter what.

   Claire

+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
 Man cannot be civilised, or be kept civilised by what he does in his
	    spare time; only by what he does as his work.
			     W.R. Lethaby
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
  C.M. Connelly               cmc@debian.org                   SHC, DS
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+





Reply to: