Re: [NTG-context] texfont: installed font only works with pdftex
On Tue, 8 Aug 2006, Taco Hoekwater wrote: This process works in a similar fashion for all programs like pdftex, dvipdfmx, dvips, and xdvi, but texfont only creates a map file for pdftex. Unf, the pdftex map file cannot be used by dvips, so for dvips you have to create your own (like you did). When you create a map file for dvips for a texfont-installed font family, it needs to have those *-raw-* entries that will map the fonts to the real postscript font files on your harddisk, and those were missing from your bgj.map. Using the attached map file fragment, I can create a postscript file that has fi ligatures of your example in texnansi encoding using dvips. I have no xdvi here to try it, but that should work as well. Thanks a lot, with that it works now (with the texnansi encoding)! These facts should be mentioned in the docs. I also have created another map file ec-bgj.map with the entries ec-raw-bgjb ElegantGaramondBT-Bold ECEncoding ReEncodeFont lm-ec.enc bgjb.pfb ec-raw-bgjr ElegantGaramondBT-Roman ECEncoding ReEncodeFont lm-ec.enc bgjr.pfb ec-raw-bgjri ElegantGaramondBT-Italic ECEncoding ReEncodeFont lm-ec.enc bgjri.pfb With that and the ec encoding the document is shown correctly with xdvi. dvips seems to work correctly as well: This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com) ' TeX output 2006.08.11:1041' - schrift.ps tex.prolm-ec.enctexps.pro. bgjb.pfbbgjri.pfbbgjr.pfb[1] But gv gives an error when I try to view the ps file: Error: /undefined in ECEncoding Operand stack: Fa 139 --nostringval-- 29 13 --nostringval-- 28 38 101 --nostringval-- 3 91.3242 --nostringval-- 91.3242 0 Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- Dictionary stack: --dict:1051/1123(ro)(G)-- --dict:0/20(G)-- --dict:73/200(L)-- --dict:80/300(L)-- --dict:10/12(L)-- Current allocation mode is local Last OS error: 2 GPL Ghostscript 8.01: Unrecoverable error, exit code 1 My printer does not print it either. Maybe the reason is that I use lm-ec.enc, but ECEncoding is defined in EC.enc which is slightly different. The second problem: texfont simply does not 'do' EC correctly (at least not on my machine). There are simply no fi ligatures, not in pdftex either. I will investigate this further. On my machine the font works without problems with pdftex (texexec --pdf) and the ec encoding, ligatures and umlauts are okay. Andreas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Andreas Schneider wrote: Thanks a lot, with that it works now (with the texnansi encoding)! These facts should be mentioned in the docs. The next version of texfont will create a dvips and dvipdfmx map file as well as a pdftex one, making life a bit easier. But gv gives an error when I try to view the ps file: Error: /undefined in ECEncoding This is error is because lm-ec.enc does not name its encoding ECEncoding but enclmec , so you have to change the ReEncode strings in the map file. Best, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Hi! On Fri, 11 Aug 2006, Taco Hoekwater wrote: Andreas Schneider wrote: Thanks a lot, with that it works now (with the texnansi encoding)! These facts should be mentioned in the docs. The next version of texfont will create a dvips and dvipdfmx map file as well as a pdftex one, making life a bit easier. Good! But gv gives an error when I try to view the ps file: Error: /undefined in ECEncoding This is error is because lm-ec.enc does not name its encoding ECEncoding but enclmec, so you have to change the ReEncode strings in the map file. Ah, thanks again, with that it now works perfectly. Andreas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Thomas A. Schmitz wrote: On Aug 8, 2006, at 11:57 PM, Taco Hoekwater wrote: how does -afmpl perform? i always suspected afm2tfm not to take non existing ligs into account Just as bad (here, at least). I'll get back to you about this tomorrow, it is too late for me to do serious work. I've experimented with afm2pl, and as I wrote in an earlier mail: the beginning of EC.enc with its additional LIGKERN instructions confuses well, we can consider to let texfont use a ec-fixed encoding for afm2tfm and the regular ec encoding for the rest --afmencoding=ec-fixed or so it so it will not include default ligatures. If you delete this, it will work. If you use lm-ec.enc (which has a number of mistakes fixed anyway), it works. BUT afm2pl needs a file default.lig which is not present in all TeX distributions. I asked Siep a couple of months ago, and he replied there was a switch to ignore default.lig, but in she that case, the default ligs would have to be supplied by texfont itself (which should be doable). IMHO, texfont should switch to afm2pl by default; it's much better at preserving kerning information (Adam, any thoughts on this?), and it makes virtual fonts unnecessary. I now use it regularly for all my font needs and am very satisfied with it. for a while afm2pl was the default, but then it suddenly defaulted to latex default (em) spacing which ruined a project here because that went unnoticed and resulted in incompatible output, so it made me more careful; i'm not sure to what extend afm2pl uses the same default for the fontdimen related things as afm2tfm Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Hans Hagen wrote: well, we can consider to let texfont use a ec-fixed encoding for afm2tfm and the regular ec encoding for the rest --afmencoding=ec-fixed or so or fix afm2pl. for a while afm2pl was the default, but then it suddenly defaulted to latex default (em) spacing which ruined a project here because that went unnoticed and resulted in incompatible output, so it made me more careful; i'm not sure to what extend afm2pl uses the same default for the fontdimen related things as afm2tfm from the afm2pl documentation: -f font_dimensions afm2tfm compatible settings would be something like -f 300,100,0,1000, But as of 0.702 -f afm2tfm is also accepted Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Thomas A. Schmitz wrote: On Aug 8, 2006, at 11:57 PM, Taco Hoekwater wrote: how does -afmpl perform? i always suspected afm2tfm not to take non existing ligs into account Just as bad (here, at least). I'll get back to you about this tomorrow, it is too late for me to do serious work. I've experimented with afm2pl, and as I wrote in an earlier mail: the beginning of EC.enc with its additional LIGKERN instructions confuses it so it will not include default ligatures. As it turns out, this is the same for afm2tfm. And to make matters even more confusing, I had the following problem: At one point, I had copied EC.enc to the current directory and fixed it. However, it still didn't work, because: [EMAIL PROTECTED] new]$ ls *.enc EC.enc [EMAIL PROTECTED] new]$ kpsewhich --progname=dvips ec.enc /opt/tex/teTeX/texmf/fonts/enc/dvips/base/EC.enc because of a line in /opt/tex/teTeX/texmf/aliases :-/ Either way, it seems that this LIGKERN interpretation that overrules the afm file is actually considered a feature. The sane way out seems to be to ship our own encoding files in fonts/enc/texfont or so. Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Taco Hoekwater wrote: because of a line in /opt/tex/teTeX/texmf/aliases :-/ ah, the dreadful aliases file ... in tex live they're gone ; let's hope that this aliases fiel does not contain anything related to context tex files (patterns for instance) Either way, it seems that this LIGKERN interpretation that overrules the afm file is actually considered a feature. The sane way out seems to be to ship our own encoding files in fonts/enc/texfont or so. hm, we can let texfont search for a texfont-ec file first (the map file can still refer to the normal one i suppose) (an alternative is to let texfont copy the ec.enc file to the local path, remove the messy lines, and remove that one afterwards) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
On Aug 9, 2006, at 3:58 PM, Taco Hoekwater wrote: I've experimented with afm2pl, and as I wrote in an earlier mail: the beginning of EC.enc with its additional LIGKERN instructions confuses it so it will not include default ligatures. As it turns out, this is the same for afm2tfm. And to make matters even more confusing, I had the following problem: At one point, I had copied EC.enc to the current directory and fixed it. However, it still didn't work, because: [EMAIL PROTECTED] new]$ ls *.enc EC.enc [EMAIL PROTECTED] new]$ kpsewhich --progname=dvips ec.enc /opt/tex/teTeX/texmf/fonts/enc/dvips/base/EC.enc because of a line in /opt/tex/teTeX/texmf/aliases :-/ Either way, it seems that this LIGKERN interpretation that overrules the afm file is actually considered a feature. The sane way out seems to be to ship our own encoding files in fonts/enc/texfont or so. Taco Yes, I have a dim recollection that afm2tfm has the same problem. Isn't lm-ec.enc the better choice anyway? Couldn't we make texfont default to lm-ec.enc when it is called with --en=EC? And for the LIGKERN: yes, I asked about them on the tex-fonts list a while ago, and nobody considered them a problem. IMHO, they're totally useless or even worse, but I received the same ol' answers: can't change that, it's legacy etc. I think Mojca knows something about this as well. So my suggestion would be: make ec a synonym for lm-ec in texfont (but then, because of one or to glyphnames, lm- ec.enc has to be in the mapfile as well). Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Thomas A. Schmitz wrote: And for the LIGKERN: yes, I asked about them on the tex-fonts list a while ago, and nobody considered them a problem. IMHO, they're totally useless or even worse, but I received the same ol' answers: can't change that, it's legacy etc. I think Mojca knows something indeed, not even broken things are fixed; i wonner what those ol' users are doing with their patterns since i expect an update in patterns to have more consequences than a fix in fonts about this as well. So my suggestion would be: make ec a synonym for lm-ec in texfont (but then, because of one or to glyphnames, lm- ec.enc has to be in the mapfile as well). i see, interesting; before we do that, can you check if we can/need to do the same with texnansi, qx, etc ? Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
On Aug 9, 2006, at 4:52 PM, Hans Hagen wrote: i see, interesting; before we do that, can you check if we can/need to do the same with texnansi, qx, etc ? Hans texnansi is OK, in my experience, and qx as well. t5 also has some LIGKERN instructions at the beginning, but doesn't have f-ligatures in its character set, AFAICS, so this should work as well. I can run some texts this weekend (if you want) and see what comes up. Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Andreas Schneider wrote: On Tue, 8 Aug 2006, Hans Hagen wrote: if the problem is in a font not having glyphs, you can consider making a special encoding vector + enco-* file; not that complex since one can start with an existing one The problem is that it does work with pdftex (tex - pdf via texexec --pdf), but it does NOT work with tex - dvi - ps via texexec, dvips (some glyphs, such as ligatures and umlauts, don't work in the latter case). It should be possible to get it working, as fontinst is able to do it, so I don't know why I should need an extra encoding. Somehow you yourself (and not texfont!) have created a font map file called bgj.map for dvips, and that file is wrong. Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
On Tue, 8 Aug 2006, Taco Hoekwater wrote: Somehow you yourself (and not texfont!) have created a font map file called bgj.map for dvips, and that file is wrong. Hmm, I have created it just for LaTeX. Since it contains only entries for ec-bgj* (without 'raw') it should not interfere with the other mapfiles (created by texfont) which are for ec-raw-bgj* and texnansi-raw-bgj* (with 'raw'), or am I mistaken? Anyway xdvi complains about texnansi-raw-bgj* (see example below which I had already included in one of my previous mails). Andreas - \setuppapersize[A4][A4] \mainlanguage[de] \language[de] \enableregime[windows] \setupencoding[default=texnansi] \usetypescriptfile[type-eleggar] \usetypescript[eleggar] \setupbodyfont[eleggar,11pt] \setupbodyfontenvironment[default][em=italic] \starttext Einige Zeichen: `, ', --, , Ligaturen: fi, fl, ff, ffi, ffl Aufgelöste Ligaturen: f|i, f|l Umlaute: ä, ö, ü, ß, Ä, Ö, Ü; a, o, u, s \stoptext - xdvi.bin: Warning: Character 228 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 132 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 147 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 150 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 12 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 8 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 246 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 252 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 223 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 214 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace. xdvi.bin: Warning: Character 220 is mapped to .notdef in font texnansi-raw-bgjr (page 1), replacing by whitespace.___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Hi Andreas, Andreas Schneider wrote: On Tue, 8 Aug 2006, Taco Hoekwater wrote: Somehow you yourself (and not texfont!) have created a font map file called bgj.map for dvips, and that file is wrong. Hmm, I have created it just for LaTeX. Since it contains only entries for ec-bgj* (without 'raw') it should not interfere with the other mapfiles (created by texfont) which are for ec-raw-bgj* and texnansi-raw-bgj* (with 'raw'), or am I mistaken? Anyway xdvi complains about texnansi-raw-bgj* (see example below which I had already included in one of my previous mails). There are two problems that I can see. There is only one that you can fix, and there is another problem that is a base texfont issue. The fixable problem first: If there is a virtual font, then dvi processors will recursively break it down into its constituents (those are the *-raw-* font metrics). Eventually, when there are no longer virtual fonts to resolve, it looks for the 'base' fonts in its map file. This process works in a similar fashion for all programs like pdftex, dvipdfmx, dvips, and xdvi, but texfont only creates a map file for pdftex. Unf, the pdftex map file cannot be used by dvips, so for dvips you have to create your own (like you did). When you create a map file for dvips for a texfont-installed font family, it needs to have those *-raw-* entries that will map the fonts to the real postscript font files on your harddisk, and those were missing from your bgj.map. Using the attached map file fragment, I can create a postscript file that has fi ligatures of your example in texnansi encoding using dvips. I have no xdvi here to try it, but that should work as well. The second problem: texfont simply does not 'do' EC correctly (at least not on my machine). There are simply no fi ligatures, not in pdftex either. I will investigate this further. Taco texnansi-raw-bgjb ElegantGaramondBT-BoldTeXnANSIEncoding ReEncodeFont texnansi.enc bgjb.pfb texnansi-raw-bgjr ElegantGaramondBT-Roman TeXnANSIEncoding ReEncodeFont texnansi.enc bgjr.pfb texnansi-raw-bgjri ElegantGaramondBT-Italic TeXnANSIEncoding ReEncodeFont texnansi.enc bgjri.pfb ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Taco Hoekwater wrote: The second problem: texfont simply does not 'do' EC correctly (at least not on my machine). There are simply no fi ligatures, not in pdftex either. I will investigate this further. how does -afmpl perform? i always suspected afm2tfm not to take non existing ligs into account Hans -- - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Taco Hoekwater wrote: When you create a map file for dvips for a texfont-installed font family, it needs to have those *-raw-* entries that will map the fonts to the real postscript font files on your harddisk, and those were missing from your bgj.map. the reason why i create the map files the way we do is that i want to prevent pdftex to be too clever in sharing font resources (thre are versions out there that assume sequivalent Names to always equivalent which is not always true (think of slanted or extended fonts) (i've been bitten too often by that so i play safe) it is no problem to add that entry optionally (grep for cleanfont in texexec.pl; to tired to see the light now) Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
Hans Hagen wrote: Taco Hoekwater wrote: The second problem: texfont simply does not 'do' EC correctly (at least not on my machine). There are simply no fi ligatures, not in pdftex either. I will investigate this further. how does -afmpl perform? i always suspected afm2tfm not to take non existing ligs into account Just as bad (here, at least). I'll get back to you about this tomorrow, it is too late for me to do serious work. Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
On Aug 8, 2006, at 11:57 PM, Taco Hoekwater wrote: how does -afmpl perform? i always suspected afm2tfm not to take non existing ligs into account Just as bad (here, at least). I'll get back to you about this tomorrow, it is too late for me to do serious work. I've experimented with afm2pl, and as I wrote in an earlier mail: the beginning of EC.enc with its additional LIGKERN instructions confuses it so it will not include default ligatures. If you delete this, it will work. If you use lm-ec.enc (which has a number of mistakes fixed anyway), it works. BUT afm2pl needs a file default.lig which is not present in all TeX distributions. I asked Siep a couple of months ago, and he replied there was a switch to ignore default.lig, but in that case, the default ligs would have to be supplied by texfont itself (which should be doable). IMHO, texfont should switch to afm2pl by default; it's much better at preserving kerning information (Adam, any thoughts on this?), and it makes virtual fonts unnecessary. I now use it regularly for all my font needs and am very satisfied with it. Best Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont: installed font only works with pdftex
On Mon, 7 Aug 2006, Taco Hoekwater wrote: Andreas Schneider wrote: but xdvi gives error messages like [...] My guess is that you have to copy the final ec.enc file you used to the folder where dvips (and xdvi, which looks in the same place normally) looks for encoding files. I created a symlink in my private texmf tree (ec.enc - lm-ec.enc) and ran texhash, and after that it was all the same. Anyway, this would not explain why I have the same symptom with the texnansi encoding, too. Maybe it helps debugging that dvips gives different error messages: This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com) ' TeX output 2006.08.07:1402' - schrift.ps tex.pro8r.enctexps.pro. bgjb.pfbbgjri.pfbbgjr.pfb Warning: module writet1 of dvips (file bgjr.pfb): glyph `pi' undefined Warning: module writet1 of dvips (file bgjr.pfb): glyph `product' undefined Warning: module writet1 of dvips (file bgjr.pfb): glyph `ffl' undefined Warning: module writet1 of dvips (file bgjr.pfb): glyph `ffi' undefined Warning: module writet1 of dvips (file bgjr.pfb): glyph `ff' undefined Warning: module writet1 of dvips (file bgjr.pfb): glyph `dotlessj' undefined [1] Also I get a slightly different result: With gv I can see some umlauts in the postscript file (ä, ö, ü work, but ß does not). Instead of the ligatures there are only spaces. Andreas___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
