From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/654 Path: main.gmane.org!not-for-mail From: Erik Frambach Newsgroups: gmane.comp.tex.context Subject: Re: LaTeX's T1 encoding / LaTeX PS fonts Date: Fri, 16 Jul 1999 16:26:13 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <199907161426.QAA29283@dep.eco.rug.nl> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Trace: main.gmane.org 1035391503 25900 80.91.224.250 (23 Oct 2002 16:45:03 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:45:03 +0000 (UTC) Original-To: ntg-context@ntg.nl Xref: main.gmane.org gmane.comp.tex.context:654 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:654 > Attached are two files, that together should allow Context to use the > psnfss virtual fonts from a 'standard' TeX installation instead of the > texnansi encoded fonts. I don't see a good reason why one would want > to do that, Until now always had problems with Times: first ConTeXt seems to insist on using tir.tfm, etc., then I get problems with either missing accents or funny characters instead of ligatures ff, fi, fl or funny characters instead of quotes. But never everything correct at the same time. Maybe I'm stupid, but anyway I for one am VERY happy to see that this new method actually WORKS for me. I noticed a few strange characters in Taco's example, but maybe that's on purpose: - \v d yields d' - \v l yields l' - \=d yields a d with a dash that collides with the stem. \= b and other "tall" characters look fine with the dash somewhat above the stem What is "t: \t ae" supposed to yield? I get simply "t: ae". Erik