From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/24689 Path: news.gmane.org!not-for-mail From: Hans Hagen Newsgroups: gmane.comp.tex.context Subject: Re: A font question. Date: Fri, 23 Dec 2005 10:19:55 +0100 Message-ID: <43ABC13B.1050903@wxs.nl> References: <200512221811.13808.john@wexfordpress.com> <43ABAAFC.9000902@elvenkind.com> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1135329704 29662 80.91.229.2 (23 Dec 2005 09:21:44 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 23 Dec 2005 09:21:44 +0000 (UTC) Original-X-From: ntg-context-bounces@ntg.nl Fri Dec 23 10:21:43 2005 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from ronja.vet.uu.nl ([131.211.172.88] helo=ronja.ntg.nl) by ciao.gmane.org with esmtp (Exim 4.43) id 1Epj7O-0001tP-PP for gctc-ntg-context-518@m.gmane.org; Fri, 23 Dec 2005 10:21:42 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 831A5128E9; Fri, 23 Dec 2005 10:21:42 +0100 (CET) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 31097-10; Fri, 23 Dec 2005 10:21:42 +0100 (CET) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id A3E52128C3; Fri, 23 Dec 2005 10:19:55 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id BCF42128C3 for ; Fri, 23 Dec 2005 10:19:53 +0100 (CET) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 31097-09 for ; Fri, 23 Dec 2005 10:19:52 +0100 (CET) Original-Received: from mail.pragma-ade.net (dsl-212-84-128-085.solcon.nl [212.84.128.85]) by ronja.ntg.nl (Postfix) with ESMTP id A36EB128B4 for ; Fri, 23 Dec 2005 10:19:52 +0100 (CET) Original-Received: from [10.100.1.102] (unverified [10.100.1.102]) by controller-1 (SurgeMail 3.5b3) with ESMTP id 9057 for ; Fri, 23 Dec 2005 10:27:28 +0300 User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en Original-To: mailing list for ConTeXt users In-Reply-To: <43ABAAFC.9000902@elvenkind.com> X-Server: High Performance Mail Server - http://surgemail.com r=-274017400 X-Authenticated-User: hagen@controller-1 X-Virus-Scanned: amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.5 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl X-Virus-Scanned: amavisd-new at ntg.nl Xref: news.gmane.org gmane.comp.tex.context:24689 Archived-At: Taco Hoekwater wrote: > Hi John, > > John R. Culleton wrote: > >> I use Context for highly formatted non-fiction, but I am a bit >> reluctant to use it for much of my work because of the strange >> (to me) font handling arrangements. I see no purpose for the >> multiple synonyms of the same font. That just adds layers of >> extra work. > > > It also adds layers of configurability. Clearly you do not > need that (your font setups is extremely simple and low-level), > but lots of other people do. For example, I have documents that > use 6 totally different font sets, because all 'examples' and > 'definitions' are typeset in font families that differ from > the normal text font family. It would be a nightmare if I had to > define and remember the 200+ font definitions by hand. Also, when you want some special size, by using the synonyms you can say \definedfont[Serif at 123pt] without worrying about what the current serif is. Many years ago, Taco wrote a style for the dutch math journal which had several font sets, complex columns, mixed encodings per document, etc (i still do not understand how he managed to do it in those-days context -). A few years later when some specs changed I was asked to rewrite those styles and in the process typescripts (font classes), column sets (complex figure placement) and some more things evolved. Since then Taco and I have less nighmares -) >> So here is my question. If I set up my own font definition >> system and as part of it I have statements like: >> \font\tfa bchr8r at 10.45pt >> \font\tfb bchr8r at 11.37pt >> ... >> ... will the rest of Context accept the above tfb font and size in >> places >> where a heading macro automatically defaults to tfb? > > > Only if you never make any \{setup,switchto}bodyfont switches after > your new font definitions. if you want that, you'd say: \definefont[MyNiceBigFont][bchr8r at 10.45pt] or better: \usetypescript [serif] [charter] [ec] \definefont[MyNiceBigFont][Charter-Roman at 10.45pt] in which case you at least see what font is used, and more important, you get the encoding for free \setuphead[chapter][style=\MyNiceBigFont] btw, if there is a system behind those sizes, you can say: \definebodyfontenvironment [default] [a=1.045, b=1.137] and such which lets the a-d sizes scale that way Hans