From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/38619 Path: news.gmane.org!not-for-mail From: Arthur Reutenauer Newsgroups: gmane.comp.tex.context Subject: Re: active strings in luatex? Date: Mon, 14 Jan 2008 01:20:40 +0100 Message-ID: <20080114002040.GI5056@phare.normalesup.org> References: <20080113033142.GB12550@phare.normalesup.org> <4789F39D.30909@elvenkind.com> <6faad9f00801130638l253bd3b8le102527953a61f7b@mail.gmail.com> Reply-To: Mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1200270120 7082 80.91.229.12 (14 Jan 2008 00:22:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 14 Jan 2008 00:22:00 +0000 (UTC) To: Mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Mon Jan 14 01:22:23 2008 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 lo.gmane.org with esmtp (Exim 4.50) id 1JED5l-0002AS-Sy for gctc-ntg-context-518@m.gmane.org; Mon, 14 Jan 2008 01:22:17 +0100 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id CCCD81FB8F; Mon, 14 Jan 2008 01:21:52 +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 30911-01-9; Mon, 14 Jan 2008 01:21:18 +0100 (CET) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 0B8B31FB49; Mon, 14 Jan 2008 01:21:18 +0100 (CET) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id E9C3B1FB49 for ; Mon, 14 Jan 2008 01:21:16 +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 02324-01-7 for ; Mon, 14 Jan 2008 01:20:41 +0100 (CET) Original-Received: from nef2.ens.fr (nef2.ens.fr [129.199.96.40]) by ronja.ntg.nl (Postfix) with ESMTP id 62D181FB01 for ; Mon, 14 Jan 2008 01:20:41 +0100 (CET) Original-Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef2.ens.fr (8.13.6/1.01.28121999) with ESMTP id m0E0Ke5A035173 for ; Mon, 14 Jan 2008 01:20:41 +0100 (CET) X-Envelope-To: Original-Received: by phare.normalesup.org (Postfix, from userid 1008) id B544E38070; Mon, 14 Jan 2008 01:20:40 +0100 (CET) Content-Disposition: inline In-Reply-To: <6faad9f00801130638l253bd3b8le102527953a61f7b@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.1.4 (nef2.ens.fr [129.199.96.32]); Mon, 14 Jan 2008 01:20:41 +0100 (CET) X-Virus-Scanned: amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.9 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:38619 Archived-At: > XeTeX always converts, say, c + combining caron into a ccaron whenever > one exists in the font Does it really? I had understood from the last discussion on the XeTeX list that it did not, with the example of capital alpha + combining breathing which was not set correctly. But maybe it's LaTeX's fault? > In the case of LM, the font has > combining characters with zero width with the accent shifted to the > left, so that it looks OK on an average glyph That's a nice trick, but in the case of 'l', it looks really ugly. > (but in general, TeX > does a better job with combining characters) unless one requests two > accents. Sure. > So, either ccaron or c+combining caron (or l+combining tilde) should > behave the same way: Yes, of course. This is Unicode canonical equivalence, explained in the links Idris gave in the Unicode Standard (chapter 2 is "Introduction", chapter 3 is "Conformance", and we may be concerned by chapter "Implementation guidelines", too). > Also, {\v x} and other strange combinations don't work in ConTeXt (I > guess it does in plain TeX) since ConTeXt MK II uses a clever way to > figure out if such characters exist in the font encoding Mapping sequences like "\v c" to the appropriate slot in the current font encoding is quite legitimate; LaTeX does the same with its own font encodings. I didn't know it meant things like "\v x" couldn't be displayed, though. That said, it is something different from supporting combining characters. Arthur ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________