From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/18312 Path: main.gmane.org!not-for-mail From: "Adam Lindsay" Newsgroups: gmane.comp.tex.context Subject: Re: Choosing an encoding - what are the consequences? Date: Tue, 15 Feb 2005 14:50:54 +0000 Message-ID: <20050215145054.13727@mail.comp.lancs.ac.uk> References: <4211B4EA.1030200@gmx.de> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1108479093 23980 80.91.229.2 (15 Feb 2005 14:51:33 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 15 Feb 2005 14:51:33 +0000 (UTC) Original-X-From: ntg-context-bounces@ntg.nl Tue Feb 15 15:51:33 2005 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 1D1408-00056O-5k for gctc-ntg-context-518@m.gmane.org; Tue, 15 Feb 2005 15:48:34 +0100 Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id E9B51127B6; Tue, 15 Feb 2005 15:50:59 +0100 (CET) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (ronja.vet.uu.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 29027-01; Tue, 15 Feb 2005 15:50:56 +0100 (CET) Original-Received: from ronja.vet.uu.nl (localhost.localdomain [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 73F8C1277B; Tue, 15 Feb 2005 15:50:56 +0100 (CET) Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id C71BD1277B for ; Tue, 15 Feb 2005 15:50:54 +0100 (CET) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (ronja.vet.uu.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 28847-03 for ; Tue, 15 Feb 2005 15:50:54 +0100 (CET) Original-Received: from mail.comp.lancs.ac.uk (mail.comp.lancs.ac.uk [148.88.3.45]) by ronja.ntg.nl (Postfix) with ESMTP id F171112778 for ; Tue, 15 Feb 2005 15:50:53 +0100 (CET) Original-Received: from [194.80.36.199] (localhost [127.0.0.1]) by mail.comp.lancs.ac.uk (8.12.10/8.12.10) with ESMTP id j1FEorAX029825 for ; Tue, 15 Feb 2005 14:50:53 GMT Original-To: "mailing list for ConTeXt users" In-Reply-To: <4211B4EA.1030200@gmx.de> X-Mailer: CTM PowerMail version 5.1 build 4340 English X-Virus-Scanned: by 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: by amavisd-new at ntg.nl X-MailScanner-From: ntg-context-bounces@ntg.nl X-MailScanner-To: gctc-ntg-context-518@m.gmane.org Xref: main.gmane.org gmane.comp.tex.context:18312 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:18312 Stefan Wachter said this at Tue, 15 Feb 2005 09:38:02 +0100: >I am on the burdensome path to understanding font handling in ConText. >Now I wonder what the consequences are with choosing certain encodings. I'll give an answer based on what I understand. Mind you, I'm lucky enough to write almost exclusively in English, where it's not an issue. >For example if I choose "8a" encoding (called "Adobe standard encoding"): Okay, as far as I know, ConTeXt doesn't have an 8a/Adobe encoding vector defined yet. >1. There are lots of empty slots in this encoding. What does ConText do >if a symbol that is to be typeset is not contained in an encoding? It falls back to the enco-def encoding, where it substitutes or composes a character from known (or expected) defaults. >2. Can I ommit the 8a encoding in map files when PDF documents are >generated (because it is the Adobe standard encoding)? Dunno. But it's worth finding out! :) >3. Somewhere I read that "texnansi" is a preferred encoding. Why? I think it's got the most useful (to Hans) glyphs packed in there. There's the secondary fact that the built-in fonts shipped with most distributions don't include it, and Hans seems to view most pre- fabricated TFM files with some suspicion. If you build a local TFM file with texfont, then you know what you're getting! But that's only my interpretation. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-