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 q0BLKSNO022196 for ; Wed, 11 Jan 2012 22:20:29 +0100 Received: (qmail 1866 invoked by alias); 11 Jan 2012 21:20:23 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 11 Jan 2012 21:20:23 -0000 Received: from relay2.uni-heidelberg.de (EHLO relay2.uni-heidelberg.de) [129.206.210.211] by mx0.gmx.net (mx014) with SMTP; 11 Jan 2012 22:20:23 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id q0BLGdNd032298 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jan 2012 22:16:39 +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 q0BG4ngC014785; Wed, 11 Jan 2012 22:16:38 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 1968811 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 11 Jan 2012 22:16:38 +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 q0BLGcZi026305 for ; Wed, 11 Jan 2012 22:16:38 +0100 Received: from anchor-msapost-1.mail.demon.net (anchor-msapost-1.mail.demon.net [195.173.77.164]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id q0BLGRbd032247 for ; Wed, 11 Jan 2012 22:16:30 +0100 Received: from cremornelane.demon.co.uk ([80.177.25.195] helo=palladium.local) by anchor-post-1.mail.demon.net with esmtpsa (AUTH morningstar2) (TLSv1:AES256-SHA:256) (Exim 4.69) id 1Rl5X1-0004kK-gJ for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 11 Jan 2012 21:16:27 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 References: <4EFF960F.6010407@morningstar2.co.uk> X-Enigmail-Version: 1.3.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <4F0DFC2A.1020804@morningstar2.co.uk> Date: Wed, 11 Jan 2012 21:16:26 +0000 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: How to describe category codes: documentation and \char_show_value_catcode:n To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <4EFF960F.6010407@morningstar2.co.uk> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (Sender is in whitelist: joseph.wright@MORNINGSTAR2.CO.UK); Detail=5D7Q89H36p4L00VTXC6D4q0N+AH0PUCnBi0P5cROEGjO+pG7NAH/K+tf9SrVFtpLrKONl 2T9EL4W4U4jgzLbnCcGpk1z/zwmKT/K1fv3lD0=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: 6991 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{}~() > 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. I will also make a change here in the same vein unless there are objections. -- Joseph Wright