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

Debian TeX Policy / fonts -- update in the works...



Hi,

I was preparing an update for the font section in the policy, with more
structure, so that it is easier to follow, and the 10 default priority
(see below). But I have to go now. Will finish probably this evening.

	  <p>
	  A package that provides PostScript Type&nbsp;1 fonts for TeX should
          be usable with any Basic TeX Package. For the rest of this section,
          we'll assume we are dealing with a package named <var>package</var>
          that installs such fonts for TeX.
          </p>

          <p> <var>package</var> should fulfill the following requirements:
            <enumlist>
              <item>
                It should depend on <package>tex-common</package> (for
                <prgn>update-updmap</prgn> and a sane <file>texmf.cnf</file>,
                so that <prgn>mktexlsr</prgn> and <prgn>updmap-sys</prgn> can
                be run safely if they are present) but not on any Basic TeX
                Package, unless needed for another task than simply installing
                the fonts for TeX.

              <item>
                It should install the necessary map files (<file>.map</file>
                extension) below <file>/etc/texmf/map/</file>. This directory
                (or relevant subdirectories such as <file>dvipdfm</file>,
                <file>dvips</file> and <file>pdftex</file>) is symlinked from
                <file><var>TEXMFMAIN</var>/fonts/map</file> by the Basic TeX
                packages. For more details about the placement of map files
                and other TeX-related files, please refer to
                <file>TETEXDOC.pdf</file> (<tt>texdoc TETEXDOC</tt>) for
                teTeX, and more generally to the TeX Directory Structure, also
                known as TDS and found at <url id="http://www.tug.org/tds/";
                name="http://www.tug.org/tds/";> (teTeX&nbsp;3 follows TDS
                version&nbsp;1.1). Of course, when any these documents
                mentions a directory under <file><var>TEXMFMAIN</var> that is,
                due to the symbolic links installed by the Basic TeX Packages,
                accessible under <file>/etc</file>, <var>package</var> should
                install the files in the appropriate subdirectory of
                <file>/etc</file>, because the symlinks mean that the
                directory is considered to contain configuration files (for
                instance, don't install map files into
                <file>/usr/share/texmf/fonts/map/dvips</file>; use
                <file>/etc/texmf/map/dvips</file> instead.

              <item>
                It should also obviously install other needed or useful files
                provided by upstream to use the fonts with TeX-related
                programs (<file>.pfb</file>, <file>.tfm</file>,
                <file>.enc</file>, <file>.fd</file>, <file>.sty</file>,
                documentation, etc.).

              <item>
                It should register the map files by putting a configuration
                file whose name follows the pattern
                <tt>10<var>name</var>.cfg</tt> into
                <file>/etc/texmf/updmap.d/</file> and calling
                <tt>update-updmap --quiet</tt>. The file contents will then be
                included into <file>/var/lib/texmf/web2c/updmap.cfg</file>,
                the effective configuration file for <prgn>updmap-sys</prgn>.

              <item>
                Before running <prgn>updmap-sys</prgn> with this updated
                <file>updmap.cfg</file>, <var>package</var> should call
                <prgn>mktexlsr</prgn> so that <prgn>updmap-sys</prgn> can
                locate the newly-installed files. It is recommended to invoke
                the three programs in the following order:
                <prgn>update-updmap</prgn>, <prgn>mktexlsr</prgn> and then
                <prgn>updmap-sys</prgn>. We have just explained why the
                <prgn>mktexlsr</prgn> call is necessary before running
                <prgn>updmap-sys</prgn>. It is also slightly better after
                <prgn>update-updmap</prgn>, because
                <file>/var/lib/texmf/web2c/updmap.cfg</file> might have been
                created by <prgn>update-updmap</prgn>, although it more
                probably already existed. And since it would be of no use to
                call <prgn>mktexlsr</prgn> before <prgn>update-updmap</prgn>,
                it is better after, just in case.
            </enumlist>

-- 
Florent



Reply to: