Re: [NTG-context] texfont produces faked ligatures with ec encoding
On Sun, 6 Aug 2006, Thomas A. Schmitz wrote: No, I never had problems with Umlauts. Now I've found lm-ec.enc in another texmf tree. When I copy lm-ec.enc to the directory where I run texfont, it works fine. What you can also try is this: if you open EC.enc, you'll find a couple of LIGKERN instructions at the beginning of the file. These seem to confuse some utilities so they don't include the default ligatures anymore. So what you can do: just delete lines 1-27 of EC.enc, so the first line is /ECEncoding [% now 256 chars follow Then save this new file in the directory where you run texfont so it will be found first. You can discard it afterwards. With this trick, it works as well. Thanks for your help Andreas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont produces faked ligatures with ec encoding
On Mon, 7 Aug 2006, Andreas Schneider wrote:
Now I've found lm-ec.enc in another texmf tree. When I copy lm-ec.enc to
the directory where I run texfont, it works fine.
Unfortunately it only works with pdftex, i.e. texexec --pdf and pdflatex.
With texexec or latex it does not work. For example, if I run texexec over
the simple sample file
\setuppapersize[A4][A4]
\mainlanguage[de]
\language[de]
\enableregime[windows]
\setupencoding[default=ec]
%\loadmapfile[ec-bitstrea-eleggar.map]
\usetypescriptfile[type-eleggar]
\usetypescript[eleggar]
\setupbodyfont[eleggar,11pt]
\setupbodyfontenvironment[default][em=italic]
\starttext
Dies ist ein Text, der in ElegantGaramond erscheinen soll.
Er enthält auch {\it kursive} und {\bf fette} Teile.
{\em Hervorgehoben}
Einige Zeichen: `, ', --, ,
Ligaturen: fi, fl, ff, ffi, ffl
Aufgelöste Ligaturen: f|i, f|l
Umlaute: ä, ö, ü, ß, Ä, Ö, Ü; a, o, u, s
\stoptext
it doesn't complain, but xdvi gives error messages like
xdvi.bin: Warning: Character 228 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
xdvi.bin: Warning: Character 18 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
xdvi.bin: Warning: Character 16 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
xdvi.bin: Warning: Character 21 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
xdvi.bin: Warning: Character 19 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
xdvi.bin: Warning: Character 20 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
xdvi.bin: Warning: Character 28 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
xdvi.bin: Warning: Character 29 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
xdvi.bin: Warning: Character 246 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
xdvi.bin: Warning: Character 252 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
xdvi.bin: Warning: Character 255 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
xdvi.bin: Warning: Character 214 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
xdvi.bin: Warning: Character 220 is mapped to .notdef in font ec-raw-bgjr (page
1), replacing by whitespace.
and ligatures and umlauts are not displayed. With the texnansi encoding, I
get similar results:
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.
How can I solve this? (Since I've got a postscript printer, I would like
to have tex - dvi - ps working.)
Andreas___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont produces faked ligatures with ec encoding
Andreas Schneider wrote: it doesn't complain, 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. Cheers, Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont produces faked ligatures with ec encoding
Andreas Schneider wrote: \setuppapersize[A4][A4] \mainlanguage[de] \language[de] \enableregime[windows] \setupencoding[default=ec] %\loadmapfile[ec-bitstrea-eleggar.map] \usetypescriptfile[type-eleggar] \usetypescript[eleggar] \setupbodyfont[eleggar,11pt] \setupbodyfontenvironment[default][em=italic] \starttext since you're typesetting german ... why not using the texnansi encoding instead of the flawed ec encoding? 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 produces faked ligatures with ec encoding
Andreas Schneider wrote: What do I do wrong? As far as I know, that should have worked. Did you run texexec ec-bitstrea-eleggar ? The first page should show a font table, and that may help debugging (perhaps your local ec.enc is wrong) Taco ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont produces faked ligatures with ec encoding
On Sun, 6 Aug 2006, Thomas A. Schmitz wrote: Sorry, I haven't followed this thread closely (so I have no idea if this has already been solved), but I had a similar symptom a while ago. It turned out that it was something with the default EC.enc that ships with tetex. Can you try to do the conversion again, this time using lm-ec.enc instead of EC.enc? I can send a longer explanation if that's of interest, but I found that it solved the problem in my case. Thanks for that hint. There is no file lm-ec.enc in my installation, but ec-var-lm.enc. If I add a --variant=var-lm to the parameters for texfont (or alternatively create a symbolic link ec.ec - ec-var-lm.enc in my private texmf tree), then the ligatures work correctly! Unfortunately, umlauts don't work anymore, both typed directly (ä, ö, ü. ß, ...) and with the TeX commands (a, o, u, s, ...). Did you have problems with umlauts as well using lm-ec.enc? Maybe I should try cork.enc (--encoding=cork) instead? The main reason I want to install the font with ec encoding is that I also want to use it under LaTeX with the T1 encoding. Andreas___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont produces faked ligatures with ec encoding
On Aug 6, 2006, at 10:28 PM, Andreas Schneider wrote: Thanks for that hint. There is no file lm-ec.enc in my installation, but ec-var-lm.enc. If I add a --variant=var-lm to the parameters for texfont (or alternatively create a symbolic link ec.ec - ec-var-lm.enc in my private texmf tree), then the ligatures work correctly! Unfortunately, umlauts don't work anymore, both typed directly (ä, ö, ü. ß, ...) and with the TeX commands (a, o, u, s, ...). Did you have problems with umlauts as well using lm-ec.enc? Maybe I should try cork.enc (-- encoding=cork) instead? The main reason I want to install the font with ec encoding is that I also want to use it under LaTeX with the T1 encoding. No, I never had problems with Umlauts. What you can also try is this: if you open EC.enc, you'll find a couple of LIGKERN instructions at the beginning of the file. These seem to confuse some utilities so they don't include the default ligatures anymore. So what you can do: just delete lines 1-27 of EC.enc, so the first line is /ECEncoding [% now 256 chars follow Then save this new file in the directory where you run texfont so it will be found first. You can discard it afterwards. HTH Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] texfont produces faked ligatures with ec encoding
On 8/6/06, Andreas Schneider wrote: On Sun, 6 Aug 2006, Thomas A. Schmitz wrote: Sorry, I haven't followed this thread closely (so I have no idea if this has already been solved), but I had a similar symptom a while ago. It turned out that it was something with the default EC.enc that ships with tetex. Can you try to do the conversion again, this time using lm-ec.enc instead of EC.enc? I can send a longer explanation if that's of interest, but I found that it solved the problem in my case. Thanks for that hint. There is no file lm-ec.enc in my installation Hmmm ... how old is your ConTeXt then? You should install the new verision of Latin Modern, but recent version of ConTeXt doesn't work with the old version of Latin Modern. but ec-var-lm.enc. If I add a --variant=var-lm to the parameters for texfont (or alternatively create a symbolic link ec.ec - ec-var-lm.enc in my private texmf tree), then the ligatures work correctly! Unfortunately, umlauts don't work anymore, both typed directly (ä, ö, ü. ß, ...) and with the TeX commands (a, o, u, s, ...). Did you have problems with umlauts as well using lm-ec.enc? Maybe I should try cork.enc (--encoding=cork) instead? Cork won't help you. It's just as bad as ec.enc (they're just synonyms - both are old and kind-of-obsolete, but nobody wants to modernise them; they say that you have to write your own for the usage with recent fonts). You can try if you'll have more luck with this one (should be more or less equivalent with ec-lm.enc if you would have the latest version of LM installed): http://www.tug.org/fontname/tex256.enc ec.enc would give you way too many missing glyphs anyway. Mojca ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
