From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/25922 Path: news.gmane.org!not-for-mail From: Adam Lindsay Newsgroups: gmane.comp.tex.context Subject: Re: Dense encoding, part II Date: Fri, 10 Feb 2006 16:35:58 +0000 Message-ID: <43ECC0EE.2030500@comp.lancs.ac.uk> References: <6faad9f00601230737q5a3a248ala84953f04bbdede1@mail.gmail.com> <43D4FC81.4030106@wxs.nl> <43E640B7.7060007@comp.lancs.ac.uk> <6faad9f00602100759w3e217c7avcaa50222ebcb6e2e@mail.gmail.com> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1139620809 12892 80.91.229.6 (11 Feb 2006 01:20:09 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 11 Feb 2006 01:20:09 +0000 (UTC) Original-X-From: ntg-context-bounces@ntg.nl Sat Feb 11 02:19:43 2006 Return-path: Original-Received: from ronja.vet.uu.nl ([131.211.172.88] helo=ronja.ntg.nl) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1F7bIg-0005sY-00 for ; Fri, 10 Feb 2006 17:39:14 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id B59F41278B; Fri, 10 Feb 2006 17:39:13 +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 18638-04; Fri, 10 Feb 2006 17:39:13 +0100 (CET) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id C628F1278A; Fri, 10 Feb 2006 17:35:52 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id A7FE31278A for ; Fri, 10 Feb 2006 17:35:51 +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 18638-03 for ; Fri, 10 Feb 2006 17:35:50 +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 SMTP id 4FF2812788 for ; Fri, 10 Feb 2006 17:35:49 +0100 (CET) Original-Received: from [194.80.37.193] (localhost [127.0.0.1]) by mail.comp.lancs.ac.uk (8.12.10/8.12.10) with ESMTP id k1AGZnpG022047 for ; Fri, 10 Feb 2006 16:35:49 GMT User-Agent: Thunderbird 1.5 (Macintosh/20051201) Original-To: mailing list for ConTeXt users In-Reply-To: <6faad9f00602100759w3e217c7avcaa50222ebcb6e2e@mail.gmail.com> X-Virus-Scanned: amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.7 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:25922 Archived-At: Mojca Miklavec wrote: > On 2/5/06, Adam Lindsay wrote: >> Hans Hagen wrote: >>> Mojca Miklavec wrote: >>> >>>> Hello, >>>> >>>> The fact that all Polish fonts (lm, iwona, kurier, antt) now ship with >>>> el-* files makes me wonder: is there time to do the next step and >>>> finish the second encoding with symbols? >>>> >>>> >>> indeed >> Oop. Sorry, I hadn't been watching that. >> I've suggested texnansi as a starting point, at least within ConTeXt. >> What symbols do people want that *aren't* within texnansi? > > 1. Would Caron & similar uppercase accents make sense? I doubt that > many accents are needed in addition to what is already present in the > other encoding anyway, but something like that could be used if there > is no Ccaron present in the font for example: > > \definecharacter Ccaron {\buildtextaccent\textCaron C} > instead of > \definecharacter Ccaron {\buildtextaccent\textcaron C} > > In well-designed fonts (including all Polish fonts such as lm, > antykwa, iwona, ...) the lowercase and the uppercase variant of the > accent differ. (Try to write \Scaron\Ccaron in texnansi encoding for > example to see the difference). Good point... except that there are *no* accents available in eurolett, anyway. It *should* have all of the accented uppercase characters you need (within roman ;). The whole theory is to do away with building text accents. But what does Hans want? Should lc and uc accents be available to create `weird' combinations? > Of course some care has to be taken, so that it will also work for > fonts without those additional accents for uppercase characters (using > \iffontchar perhaps?). Indeed. I do want to avoid a strong dependency on the specific glyphs that appear in the font. That moves the encoding mess to *within* ConTeXt, which is not pretty, either. > 2. perhaps some currency symbols missing in texnansi > I would suggest to add Euro, but with some special care of course. > Perhaps some users still prefer to use the regular (geometrical) > symbol rather than the one taken from I-forgot-which-font (the default > behaviour when \texteuro is used). > > Any other currency on this list worth supporting? > http://www.unicode.org/charts/PDF/U20A0.pdf > Perhaps dong, lira, Won ... sounds like ts1-like stuff. > 3. Perhaps a short glimpse into: > http://source.contextgarden.net/ts1-lm.enc > http://www.cstug.cz/aktivity/2005/lm-at11e.pdf > http://www.janusz.nowacki.strefa.pl/pliki/AntykwaTorunska-doc-en-2_03.pdf > if you notice anything worth supporting. > > "married" might be useful for geneaology, I guess that the leaf is > there for the same purpose. No idea why anyone would want to use the > musical note (ugly in lm and probably hardly present in any other > font). They're there because of ts1, which is *mostly* unhelpful here. I would have thought glyph coverage from places like Adobe, Storm, and Emigre (for example) might be a better guide. > 4. numero sign, ordfeminine, ordmasculine, copyleft ;), I don't know well, some of those are in standard practice, at least. ;) > if anybody needs fractions, permyriad, ... one/two/...superior > (present in some regimes) are pretty pointless in TeX where you can > use \high{} I guess. Perhaps there should be two different glyphs for > "tilde" and "asciitilde" (not sure about the last one.) Yeah, I'm trying to be driven by *requirements* instead of "technical capability" (i.e., what already exists in a family of fairly peculiar fonts). I know those are around, but I don't hear a lot of calls for them since ConTeXt moved to EC as a default encoding. adam -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 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 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-