Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with SMTP id q0BMF2jB004046 for ; Wed, 11 Jan 2012 23:15:03 +0100 Received: (qmail 20428 invoked by alias); 11 Jan 2012 22:14:44 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 11 Jan 2012 22:14:44 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx057) with SMTP; 11 Jan 2012 23:14:44 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id q0BMBEcQ030716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jan 2012 23:11:14 +0100 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id q0BG4ni4014785; Wed, 11 Jan 2012 23:11:14 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 1968902 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 11 Jan 2012 23:11:14 +0100 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id q0BMBEaD002306 for ; Wed, 11 Jan 2012 23:11:14 +0100 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id q0BMB35d015070 for ; Wed, 11 Jan 2012 23:11:07 +0100 Received: from mittelbach-online.de (p3EE3F421.dip.t-dialin.net [62.227.244.33]) by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis) id 0MGR4S-1RyLup1c6i-00DCTo; Wed, 11 Jan 2012 23:11:03 +0100 Received: by mittelbach-online.de (Postfix, from userid 783) id 1D028940A41; Wed, 11 Jan 2012 23:10:58 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on Marlowe X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED,AWL autolearn=unavailable version=3.2.5 Received: from [127.0.0.1] (unknown [192.168.123.100]) (Authenticated sender: frank) by mittelbach-online.de (Postfix) with ESMTPSA id 22C65940669 for ; Wed, 11 Jan 2012 23:10:55 +0100 (CET) User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 References: <4EFF960F.6010407@morningstar2.co.uk> <4F0DFC2A.1020804@morningstar2.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 120111-1, 11.01.2012), Outbound message X-Antivirus-Status: Clean X-Provags-ID: V02:K0:6cxtIx8O5BJSnCq+md+iLD9PzXo+bAzBdrlUSGfMlRT paNlsPAoE40fMwemWnH82EAnhwFgrQhF36G8ZQ7Edb0Tznnat2 yrfFi1H4l+qWkROD4Ai9LDfDulGvhoELNuNwhJvZI02YBdV/M9 pKUerxjqwuUeoOY6EzyElpXo4fylnpaHss2KOELThJTxXOLJZ0 JSzm/ikHZ1P6bkerwi/5sbXqJae6104IRAOt5N9xhmJ/ZMMueG kCmSP3Wm48rXuKWTh/nyC9sK5urjPNEiCqHyNb5WnqMXUD9JIY DcA7KSrGn46Cs89prsXGYf6a2wLGD0sQchwH63s7d3mL1QjVYC 26cD4qQSdwj97MdsyDAekHrrApgiow48guK4fN0MJ Message-ID: <4F0E08EE.30007@latex-project.org> Date: Wed, 11 Jan 2012 23:10:54 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Frank Mittelbach Subject: Re: How to describe category codes: documentation and \char_show_value_catcode:n To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <4F0DFC2A.1020804@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (eXpurgate); Detail=5D7Q89H36p6sJLDpZh614Kjz2nt6F3tHhzt9a9IvKV07U2dQ+18vQeJMS4eKiQAtrvfka ymiubocfQxsKjhoIXO7ttVINNc1S8w0FI0HmS+suL3nhYaAW6ze9BIJOxoF8WMMsYR68upGQ1S1s yiOTPYm7Z0Nr24dGsSZfyeDDTu63vC8MDIWyso9JS5NXyN3BOWrGO7rGzc=V1; X-Resent-By: Forwarder X-Resent-For: rainer.schoepf@gmx.net X-Resent-To: rainer@rainer-schoepf.de Status: R X-Status: X-Keywords: X-UID: 6992 Am 11.01.2012 22:16, schrieb Joseph Wright: > On 31/12/2011 23:09, Joseph Wright wrote: >> 1) How should we refer to catcode in documentation, both in terms of >> the text and the formatting (for example, do we want to say >> something line 'category code')? > > Unless I hear that there are strong objections, I propose to make a > change here as I indicate above, using the name of each category code as > described in the naming of \char_set_catcode_... and using formatting > > category code \meta{}~() well, I'm not sure I parse this line. To me "code" implies more a number than something like "other". I'm fine with statements like "character category " but less so with "category code " or is the above to read as category code \meta{other} (12) >> 2) What should we do for \char_show_value_catcode:n? 'show_value' is >> not the right name for showing a symbolic meaning. I guess we just >> use \prg_case_int:nnn to actually show the meaning. if you want to go for symbolic then you could have \char_show_category:n {x} -> and drop "code" from the cs name cheers frank