From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/6416 Path: main.gmane.org!not-for-mail From: Giuseppe Bilotta Newsgroups: gmane.comp.tex.context Subject: Re[2]: More font problems --- encoding errors Date: Fri, 28 Dec 2001 10:48:40 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <82527601.20011228104840@bigfoot.com> References: <5.1.0.14.1.20011227141026.03c798e8@server-1> Reply-To: Giuseppe Bilotta 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 1035396947 10423 80.91.224.250 (23 Oct 2002 18:15:47 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:15:47 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: Hans Hagen In-Reply-To: <5.1.0.14.1.20011227141026.03c798e8@server-1> Xref: main.gmane.org gmane.comp.tex.context:6416 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:6416 Thursday, December 27, 2001 Hans Hagen wrote: >>Is this WAD (Working As Designed) or a bug? Shouldn't the encoding >>be tied to the font? HH> right, normally one does never set the encoding, the font switch does (and HH> therefore the typescript files should mention =8r somewhere; i probably HH> have to add a couple of 8r's here and there; btw, is 8r really used?). Yes it is, that's how these problem surfaced :-) >>\definefontsynonym >>[Times-Roman] [\typefaceencoding-utmr8a] [encoding=\typefaceencoding] >>(called with typefaceencoding=8r) >>\definefontsynonym [8r-utmr8a] [ptmr8r] >> >>Shouldn't in the end the ptmr8r be called with the encoding 8r >>defined in the previous synonym? HH> indeed, and if it goes wrong, then there is a bug; do you use the latest HH> beta? I have 2001.07.10 HH> ... in my local typeface files -) I know that you have cont-loc.tex, but HH> since that one is pretty experimental and only for very special use; use HH> cont-new instead; since cont-loc is not (and will never be) part of the HH> distribution, stuff in there may conflict (actually, there is some already HH> replace font stuff in there (esp some changed in the way font attrs like HH> encoding are resolved); did you try these things without cont-loc.tex HH> available?) Uh, I'm not using the cont-loc you gave me (for that precise reason), but a new, empty one :-) Since those things are encoding-specific and not typescript specific, I thought they had to go to cont-new or cont-loc, rather. Anyway ... Now I'll check out the small caps thing. -- Giuseppe "Oblomov" Bilotta