Menu

#1 Changes for tetex 3 and for pdftex

open
nobody
None
5
2007-01-26
2007-01-26
No

I've made some changes to tex-fontconfig to make it work with tetex 3 and including the latest version of fontinst, as well as better support for pdftex. I'm sorry that this is all one big patch...

CHANGES

* Now works with tetex 3 installation of Fedora Core 5

* genmapping(): change to regexp match to improve on mapping file when
the vendor is inclded in the font name, e.g. Arial-BoldMT

* Broken afm files produced by ttftot42 and ttf2pt1 - I've put line
into fix this

* Changed location of map files to fonts/map from dvips/misc

* kpsewich in tetex3 can find ${SUPPLIER}-${fontname}.map -- need to
look for ${familyname}.map instead

* Now puts truetype fonts in truetype dir for PDF and puts the
appropriate pdfmaplines in the .fd files

* Use the facility in the latest version of fontinst to genearate the
map files rather than the shell code

* Substitute "<<" for "<" in the map files to stop divps complaining

* Build changes: use docbook2man instead of docbook-to-man -- this
helps compiling on Fedora core 5

NOTES

* Note that pdftex cannot support type 42 fonts or slannted ttf fonts, so
there appears to be no way of having all features and top quality
for pdftex. We could create type 1 fonts for pdftex and give them
different names from the type 42 ones, but I haven't done this.

* There is a now a ghostscript-based ttf to type 42 conversion
(http://ctan.loria.fr/cgi-bin/ftp2web?OK=1&DIRCTAN=fonts/utilities/TrueTypeToType42)
and
also ttfps (available from
http://www.pps.jussieu.fr/~jch/software/files/\)

It might be preferable to use one of these instead of ttftot42,
which seems somewhat unsupported

Discussion

  • David Sterratt

    David Sterratt - 2007-01-26

    Changes to tex-fontconfig tree

     
  • David Sterratt

    David Sterratt - 2007-01-29

    Logged In: YES
    user_id=1093787
    Originator: YES

    I now realise this point was incorrect:

    * kpsewich in tetex3 can't find ${SUPPLIER}-${fontname}.map -- need to
    look for ${familyname}.map instead

    The reason that dvips couldn't find the file was that I had put the information in my .dvipsrc (I'm installing fonts into my home directory).

    I've now discovered that updmap may be the "correct" way to install fonts, though it's not clear to me yet how it could be set up to generate a separate map file for pdftex (referring to type 1 fonts to allow slanted text). So perhaps the code that inserts pdfmaplines in the .fd files is redundant.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.