LATEX-L Archives

Mailing list for the LaTeX3 project


Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Type: text/plain; charset=ISO-8859-1
Date: Sat, 31 Dec 2011 23:09:03 +0000
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
MIME-Version: 1.0
Message-ID: <[log in to unmask]>
Content-Transfer-Encoding: 7bit
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
From: Joseph Wright <[log in to unmask]>
Parts/Attachments: text/plain (22 lines)
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 <other>')?
 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