From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/24680 Path: news.gmane.org!not-for-mail From: Taco Hoekwater Newsgroups: gmane.comp.tex.context Subject: Re: A font question. Date: Fri, 23 Dec 2005 08:45:00 +0100 Message-ID: <43ABAAFC.9000902@elvenkind.com> References: <200512221811.13808.john@wexfordpress.com> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1135323891 15082 80.91.229.2 (23 Dec 2005 07:44:51 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 23 Dec 2005 07:44:51 +0000 (UTC) Original-X-From: ntg-context-bounces@ntg.nl Fri Dec 23 08:44:49 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 1EphbZ-0004fd-N8 for gctc-ntg-context-518@m.gmane.org; Fri, 23 Dec 2005 08:44:45 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id C0FEF128B3; Fri, 23 Dec 2005 08:44:43 +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 29472-04; Fri, 23 Dec 2005 08:44:38 +0100 (CET) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id E00EF127E3; Fri, 23 Dec 2005 08:44:37 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 53ED7127E3 for ; Fri, 23 Dec 2005 08:44:36 +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 29556-02 for ; Fri, 23 Dec 2005 08:44:35 +0100 (CET) Original-Received: from post-24.mail.nl.demon.net (post-24.mail.nl.demon.net [194.159.73.194]) by ronja.ntg.nl (Postfix) with ESMTP id 58B4412796 for ; Fri, 23 Dec 2005 08:44:35 +0100 (CET) Original-Received: from boo.demon.nl ([82.161.175.147]:55528 helo=[192.168.1.3]) by post-24.mail.nl.demon.net with esmtp (Exim 4.51) id 1EphbO-0002mg-P2 for ntg-context@ntg.nl; Fri, 23 Dec 2005 07:44:35 +0000 User-Agent: Mozilla Thunderbird 1.0 (X11/20050215) X-Accept-Language: en-us, en Original-To: mailing list for ConTeXt users In-Reply-To: <200512221811.13808.john@wexfordpress.com> 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:24680 Archived-At: 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. > If the page comes up a line short because of strict widow > prevention then the extra space is distributed imperceptibly > among the lines. It is only imperceptible if the paper you print on does not shine through at all, and if you use a noteblock (head) binding instead of book (back) binding, so it is not something I would recommend for general use. > This kind of fine tuning by users is perhaps foreign to Context as it now > exists. Font sizes are in fixed steps for one thing. The fixed steps (of .1pt) are actually an optimization, and it is possible to circumvent that, using either \chardef\fontdigits=2 or \def\normalizebodyfontsize#1\to#2{\setvalue{#2}{#1}} > 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. Cheers, Taco