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 pBVNBfrQ018235 for ; Sun, 1 Jan 2012 00:11:42 +0100 Received: (qmail 11816 invoked by alias); 31 Dec 2011 23:11:35 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 31 Dec 2011 23:11:35 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx036) with SMTP; 01 Jan 2012 00:11:35 +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 pBVN9LLT013674 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 1 Jan 2012 00:09:21 +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 pBVN16Qm023662; Sun, 1 Jan 2012 00:09:20 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 1923979 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 1 Jan 2012 00:09:20 +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 pBVN9KcP024189 for ; Sun, 1 Jan 2012 00:09:20 +0100 Received: from lon1-msapost-1.mail.demon.net (lon1-msapost-1.mail.demon.net [195.173.77.180]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id pBVN93Ax025722 for ; Sun, 1 Jan 2012 00:09:08 +0100 Received: from morningstar2.demon.co.uk ([80.176.134.7] helo=palladium.local) by lon1-post-1.mail.demon.net with esmtpsa (AUTH morningstar2) (TLSv1:AES256-SHA:256) (Exim 4.69) id 1Rh82x-0000mH-YU for latex-l@listserv.uni-heidelberg.de; Sat, 31 Dec 2011 23:09:03 +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 X-Enigmail-Version: 1.3.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <4EFF960F.6010407@morningstar2.co.uk> Date: Sat, 31 Dec 2011 23:09:03 +0000 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: How to describe category codes: documentation and \char_show_value_catcode:n To: LATEX-L@listserv.uni-heidelberg.de 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: 6979 Hello all, I was asked recently about the documentation of category codes in the LaTeX3 docs. Currently, we say things like "category code 12 ('other')" when describing what codes are active. We also provide \char_show_value_catcode:n, which is just a wrapper around \showthe\catcode. However, for setting catcode we use symbolic names, for example \char_set_catcode_other:N. While knowing catcode meanings is a required TeX programming skill, it seems more in keeping with the LaTeX3 approach to talk about these by their meaning. That raises two questions 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 ')? 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. -- Joseph Wright