From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/106 Path: main.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: bigger characters Date: Thu, 30 Jul 1998 23:25:22 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <35C0E4C2.5A779BC9@wxs.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 1035390982 21352 80.91.224.250 (23 Oct 2002 16:36:22 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:36:22 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: Frans Goddijn Xref: main.gmane.org gmane.comp.tex.context:106 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:106 Frans Goddijn wrote: > Generally in the ConTeXt manuals, the dense purely logical explanations of > how things work are too dense for me to understand. I see > [...,...=...,...] but I don't understand what should be mentally > substituted for the "..." there. Usually, below such an [...,...=...,...] > there's a grey box with options listed, some of them underlined but it > takes a few examples and their printed results before I get the idea of > it. As a simple user I often seem to lack the intellectual abstraction > level to imagine the workings of the "..." which in my mind remain little > portable black holes... Well, there is a certain login in it. ... means that you can specify more than one. I guess that if I added 10 pages of explaining this, few people would read it. Anyway, I hope it reads more easy than your regular latex style files. If not, I failed. BTW, these gray stuff is generated from rather rather structred definitions. When I add a keyword, I only have to add it to this description, and all manuals are up to date. The QRC docs (only interactive) explain the keys, but is only partially finished. > \def\os{\oldstyle} > > but after the first \os{1997} all other text in the chapter was typeset in > the expert set, i.e. small caps and weirder characters.... ;=} > > I changed this into the longer > > \def\os#1{{\oldstyle #1}} > > and now it works. I guess it can be done shorter but it works! \def\os{\groupedcommand{\oldstyle}{}} is the better way (accepts {\os ...} and \os{...}) but the official way is the one Taco explained earlier (the 'oud' definition), which you can also use as value to the letter/style key. BTW, '\groupedcommand' is rather complicated command. If you can understand the definition (see syst-gen.tex) you a pro. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | mail: pragma@wxs.nl -----------------------------------------------------------------