From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/20196 Path: news.gmane.org!not-for-mail From: Ville Voipio Newsgroups: gmane.comp.tex.context Subject: RE: Capitalized headings Date: Wed, 4 May 2005 00:32:59 +0300 Message-ID: <98D0564335EC4848A87BEDEFF4EA056B55C2@posti.kpatents.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" Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1115155529 26840 80.91.229.2 (3 May 2005 21:25:29 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 3 May 2005 21:25:29 +0000 (UTC) Original-X-From: ntg-context-bounces@ntg.nl Tue May 03 23:25:28 2005 Return-path: 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 1DT4sm-0003bd-0b for gctc-ntg-context-518@m.gmane.org; Tue, 03 May 2005 23:24:44 +0200 Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 5DE8E12814; Tue, 3 May 2005 23:31:08 +0200 (CEST) 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 22997-04; Tue, 3 May 2005 23:31:02 +0200 (CEST) Original-Received: from ronja.vet.uu.nl (localhost.localdomain [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 5FF58127FF; Tue, 3 May 2005 23:31:02 +0200 (CEST) Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id B79FD127FF for ; Tue, 3 May 2005 23:31:01 +0200 (CEST) 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 22869-06 for ; Tue, 3 May 2005 23:31:01 +0200 (CEST) Original-Received: from mail.kpatents.com (mail.kpatents.com [195.170.128.67]) by ronja.ntg.nl (Postfix) with SMTP id E307B127A2 for ; Tue, 3 May 2005 23:31:00 +0200 (CEST) Original-Received: (qmail 2157 invoked from network); 3 May 2005 21:31:00 -0000 Original-Received: from unknown (HELO posti.kpatents.com) (192.168.100.180) by mail.kpatents.com with SMTP; 3 May 2005 21:31:00 -0000 Original-Received: by posti.kpatents.com with Internet Mail Service (5.5.2653.19) id ; Wed, 4 May 2005 00:33:00 +0300 Original-To: "'ntg-context@ntg.nl'" X-Mailer: Internet Mail Service (5.5.2653.19) 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 Xref: news.gmane.org gmane.comp.tex.context:20196 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:20196 > The bad news is that now I have a lot more questions concerning the It really seems that I do... I played around with the capitalization commands and got some interesting results. My test file is (works in live.contextgarden.net if required): --- \enableregime[il1] =20 \starttext =20 abcABC=E5=E4=F6=C5=C4=D6 \cap{abcABC=E5=E4=F6=C5=C4=D6} \uppercased{abcABC=E5=E4=F6=C5=C4=D6} \WORD{abcABC=E5=E4=F6=C5=C4=D6} \uppercase{abcABC=E5=E4=F6=C5=C4=D6} =20 \stoptext =20 --- So, the test string is: = abcABC\aumlaut\aring\oumlaut\Aumlaut\Aring\Oumlaut (just in case it does not display correctly). It gives: \cap -> ABCABC=C5=C4=D6=C5=C4=D6 (in \tfx size), just as expected \uppercased -> ABCABC=E5=E4=F6=C5=C4=D6 (ABC's in \tfx, rest untouched) \WORD -> ABCABC=C5=C4=D6xxx (where xxx's are gibberish) \uppercase -> ABCABC=C5=C4=D6xxx The plain TeX \uppercase seems to be known for its nasty behaviour with anything else than US characters. \WORD seems to be a thin wrapper around it, so similar behaviour is to be expected. \uppercased makes interesting things, as it does uppercase the abc's well but does not touch the accented characters in any way. Only \cap seems to do exactly what it should. --- Things become even stranger, when the regime is switched to UTF-8. Then \WORD and \uppercase give some errors and refuse to compile. \uppercased and \cap work as described above. --- As \uppercase is a plain TeX macro, fixing it is not a good choice, especially because it is known to be bad. However, if \WORD could be built on \cap but without the font size changing, it would work fine. The odd behaviour of \uppercased (and the reasons to use it instead of the other choices) remains unclear to me. - Ville