From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/6180 Path: main.gmane.org!not-for-mail From: Berend de Boer Newsgroups: gmane.comp.tex.context Subject: Re: latest context problems Date: 16 Nov 2001 15:15:15 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <87lmh6redo.fsf@dellius.nederware.nl> References: <5.1.0.14.1.20011116141503.02f27100@server-1> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035396723 8247 80.91.224.250 (23 Oct 2002 18:12:03 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 18:12:03 +0000 (UTC) Cc: ConTeXt mailinglist Original-To: Hans Hagen In-Reply-To: <5.1.0.14.1.20011116141503.02f27100@server-1> Xref: main.gmane.org gmane.comp.tex.context:6180 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:6180 Hans Hagen writes: > >With the latest context things like: > > > > \setupbodyfont > > [ber,pos] > > > >produce lots of error messages about missing fonts. I went back to my > >previous release. > Did you read the cont-sys.rme file? Yes, but that didn't help at all. > Because multiple conflicting encoding need to be supported, and > because one can create instances like slanted or capitalized locally, > from now on we use the more verbose names > > texnansi-blabla > > and alike [see mtexfont.pdf and mfonts.pdf] > > This also means that ber does not make much sense now. But what commands do the trick by using the plain postscript fonts? For example what should I say for: \usebodyfont [ber,pos,ss,10pt] -- Groetjes, Berend. (-: