LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Forum View

Use Monospaced 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:
Mon, 16 May 2011 23:24:28 +0200
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=us-ascii
From:
Frank Mittelbach <[log in to unmask]>
Parts/Attachments:
text/plain (23 lines)
Bruno Le Floch writes:
 > > \foo [arg]   has the standard 'argument meaning'
 > >
 > > \foo
 > > [Paranthetical text starts here. ...
 > 
 > The problem is that the two are treated identically by TeX, except if
 > catcodes have not yet been assigned, and one changes the catcode of
 > eol or space.

or alternatively building out the command names yourself by putting letters on
catcode 13. that might be in fact an easier approach and then explicitly
deciding when to gobble for spaces

 > Proposal: to ban trailing optional arguments entirely.

well we can't do that with document level dtd's that provide some level of
backward compatibility and for xparse I wouldn't attempt for formally ban it
(though any discussion about use of optional arguments should make it clear
that putting them at the end is not a good idea in general).

frank

ATOM RSS1 RSS2