From: Andreas Schneider <andreas@Mathematik.Uni-Marburg.de>
Subject: texfont produces faked ligatures with ec encoding
Date: Sun, 6 Aug 2006 10:07:52 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0608060955550.27920@rabat.Mathematik.Uni-Marburg.DE> (raw)
Hi,
with the ec encoding, texfont produces faked ligatures, although the font
has real fi and fl ligatures. With the texnansi encoding and the same
commands, the ligatures are ok. (I checked this by compiling a simple
sample file, just changing \setupencoding[default=ec] to
\setupencoding[default=texnansi].) The font I'm trying to install is
Bitstream Elegant Garamond (bgj) which I have got from a CorelDraw CD. I
used the following commands to install the font (note that the fontroot is
set because I create a Debian package):
mkdir -p debian/font-elegantgaramond/usr/share/texmf
texfont --fontroot=debian/font-elegantgaramond/usr/share/texmf --vendor=bitstrea --collection=eleggar --encoding=texnansi --makepath --install
TeXFont 2.2.1 - ConTeXt / PRAGMA ADE 2000-2004
encoding vector : texnansi
vendor name : bitstrea
source path : .
font collection : eleggar
texmf font root : debian/font-elegantgaramond/usr/share/texmf
pdftex map file : texnansi-bitstrea-eleggar.map
source path : .
processing files : all on afm path
locating afm files : using pattern *
copying files : afm
copying : bgjb.afm
copying : bgjr.afm
copying : bgjri.afm
copying files : pfb
copying : bgjb.pfb
copying : bgjr.pfb
copying : bgjri.pfb
no map file at : debian/font-elegantgaramond/usr/share/texmf/fonts/map/pdftex/context/texnansi-bitstrea-eleggar.map
font identifier : ElegantGaramondBT-Bold -> text -> tfm + vf
generating raw tfm/vpl : texnansi-raw-bgjb (from bgjb)
generating new vf : texnansi-bgjb (from texnansi-raw-bgjb)
font identifier : ElegantGaramondBT-Roman -> text -> tfm + vf
generating raw tfm/vpl : texnansi-raw-bgjr (from bgjr)
generating new vf : texnansi-bgjr (from texnansi-raw-bgjr)
font identifier : ElegantGaramondBT-Italic -> text -> tfm + vf
generating raw tfm/vpl : texnansi-raw-bgjri (from bgjri)
generating new vf : texnansi-bgjri (from texnansi-raw-bgjri)
updating map file : texnansi-bitstrea-eleggar.map
generating : ls-r databases
texfont --fontroot=debian/font-elegantgaramond/usr/share/texmf --vendor=bitstrea --collection=eleggar --encoding=ec --makepath --install
TeXFont 2.2.1 - ConTeXt / PRAGMA ADE 2000-2004
encoding vector : ec
vendor name : bitstrea
source path : .
font collection : eleggar
texmf font root : debian/font-elegantgaramond/usr/share/texmf
pdftex map file : ec-bitstrea-eleggar.map
source path : .
processing files : all on afm path
locating afm files : using pattern *
copying files : afm
copying : bgjb.afm
copying : bgjr.afm
copying : bgjri.afm
copying files : pfb
copying : bgjb.pfb
copying : bgjr.pfb
copying : bgjri.pfb
no map file at : debian/font-elegantgaramond/usr/share/texmf/fonts/map/pdftex/context/ec-bitstrea-eleggar.map
font identifier : ElegantGaramondBT-Bold -> text -> tfm + vf
generating raw tfm/vpl : ec-raw-bgjb (from bgjb)
generating new vf : ec-bgjb (from ec-raw-bgjb)
font identifier : ElegantGaramondBT-Roman -> text -> tfm + vf
generating raw tfm/vpl : ec-raw-bgjr (from bgjr)
generating new vf : ec-bgjr (from ec-raw-bgjr)
font identifier : ElegantGaramondBT-Italic -> text -> tfm + vf
generating raw tfm/vpl : ec-raw-bgjri (from bgjri)
generating new vf : ec-bgjri (from ec-raw-bgjri)
updating map file : ec-bitstrea-eleggar.map
generating : ls-r databases
rm -vf debian/font-elegantgaramond/usr/share/texmf/ls-R
,,debian/font-elegantgaramond/usr/share/texmf/ls-R" entfernt
mkdir -p debian/font-elegantgaramond/usr/share/texmf/tex/context/typescript
cp -v type-eleggar.tex debian/font-elegantgaramond/usr/share/texmf/tex/context/typescript/
,,type-eleggar.tex" -> ,,debian/font-elegantgaramond/usr/share/texmf/tex/context/typescript/type-eleggar.tex"
mkdir -p debian/font-elegantgaramond/etc/texmf/updmap.d
cp -v debian/10bgj.cfg debian/font-elegantgaramond/etc/texmf/updmap.d
,,debian/10bgj.cfg" -> ,,debian/font-elegantgaramond/etc/texmf/updmap.d/10bgj.cfg"
mkdir -p debian/font-elegantgaramond/usr/share/texmf/fonts/map/dvips/bgj
cp -v *.map debian/font-elegantgaramond/usr/share/texmf/fonts/map/dvips/bgj
,,bgj.map" -> ,,debian/font-elegantgaramond/usr/share/texmf/fonts/map/dvips/bgj/bgj.map"
mkdir -p debian/font-elegantgaramond/usr/share/texmf/tex/latex/bgj
cp -v *.fd debian/font-elegantgaramond/usr/share/texmf/tex/latex/bgj
,,t1bgj.fd" -> ,,debian/font-elegantgaramond/usr/share/texmf/tex/latex/bgj/t1bgj.fd"
mkdir -p debian/font-elegantgaramond/usr/share/texmf/tex/latex/bgj
cp -v eleggar.sty debian/font-elegantgaramond/usr/share/texmf/tex/latex/bgj
,,eleggar.sty" -> ,,debian/font-elegantgaramond/usr/share/texmf/tex/latex/bgj/eleggar.sty"
The typescript I'm using is the following:
% Typescript for serif family Bitstream ElegantGaramond
\usetypescriptfile[type-buy]
% load map file
\starttypescript[map][eleggar][\defaultencoding]
\loadmapfile[\defaultencoding-bitstrea-eleggar.map]
\stoptypescript
% mapping from PostScript name to TFM file name
\starttypescript[serif][eleggar][\defaultencoding]
\definefontsynonym[ElegantGaramondBT-Bold][\defaultencoding-bgjb][encoding=\defaultencoding]
\definefontsynonym[ElegantGaramondBT-Roman][\defaultencoding-bgjr][encoding=\defaultencoding]
\definefontsynonym[ElegantGaramondBT-Italic][\defaultencoding-bgjri][encoding=\defaultencoding]
\stoptypescript
% mapping from generic family name to PostScript name
\starttypescript[serif][eleggar][name]
\usetypescript[serif][fallback]
\definefontsynonym[Serif] [ElegantGaramondBT-Roman]
\definefontsynonym[SerifItalic][ElegantGaramondBT-Italic]
\definefontsynonym[SerifBold] [ElegantGaramondBT-Bold]
\stoptypescript
% family definition
\starttypescript [eleggar]
\definetypeface [eleggar] [rm] [serif] [eleggar] [default] [encoding=\defaultencoding]
\stoptypescript
What do I do wrong?
Thank you for your help
Andreas
next reply other threads:[~2006-08-06 8:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 8:07 Andreas Schneider [this message]
2006-08-06 9:52 ` Taco Hoekwater
2006-08-06 15:00 ` Andreas Schneider
2006-08-06 16:53 ` Thomas A. Schmitz
[not found] ` <Pine.LNX.4.64.0608062211300.31615@rabat.Mathematik.Uni-Marburg.DE>
2006-08-06 21:00 ` Thomas A. Schmitz
2006-08-07 7:59 ` Andreas Schneider
2006-08-07 8:29 ` Andreas Schneider
2006-08-07 8:42 ` Taco Hoekwater
2006-08-07 12:34 ` texfont: installed font only works with pdftex Andreas Schneider
2006-08-07 13:25 ` texfont produces faked ligatures with ec encoding Hans Hagen
2006-08-08 7:14 ` texfont: font only works with pdftex Andreas Schneider
2006-08-08 8:05 ` Hans Hagen
2006-08-08 8:33 ` texfont: installed " Andreas Schneider
2006-08-08 8:56 ` Taco Hoekwater
2006-08-08 19:27 ` Andreas Schneider
2006-08-08 21:26 ` Taco Hoekwater
2006-08-08 21:46 ` Hans Hagen
2006-08-08 21:57 ` Taco Hoekwater
2006-08-09 5:29 ` Thomas A. Schmitz
2006-08-09 10:21 ` Hans Hagen
2006-08-09 11:33 ` Taco Hoekwater
2006-08-09 13:58 ` Taco Hoekwater
2006-08-09 14:14 ` Hans Hagen
2006-08-09 14:29 ` Thomas A. Schmitz
2006-08-09 14:52 ` Hans Hagen
2006-08-09 15:44 ` Thomas A. Schmitz
2006-08-08 21:50 ` Hans Hagen
2006-08-11 9:34 ` Andreas Schneider
2006-08-11 9:59 ` Taco Hoekwater
2006-08-11 10:33 ` Andreas Schneider
2006-08-06 21:42 ` texfont produces faked ligatures with ec encoding Hans Hagen
2006-08-06 23:22 ` Mojca Miklavec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0608060955550.27920@rabat.Mathematik.Uni-Marburg.DE \
--to=andreas@mathematik.uni-marburg.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).