LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Proportional Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Date:
Wed, 11 Jan 2012 21:16:26 +0000
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Message-ID:
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
Content-Type:
text/plain; charset=ISO-8859-1
From:
Joseph Wright <[log in to unmask]>
Parts/Attachments:
text/plain (19 lines)
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 <other>')?

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{<description>}~(<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.

I will also make a change here in the same vein unless there are objections.
-- 
Joseph Wright

ATOM RSS1 RSS2