LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Condense Mail Headers

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

Print Reply
Mime-Version:
1.0 (Apple Message framework v1081)
Content-Type:
text/plain; charset=iso-8859-1
Date:
Tue, 15 Feb 2011 19:40:52 +1030
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
Re: Expandable versions of \uppercase, \MakeUppercase, \lowercase, \MakeLowercase
From:
Will Robertson <[log in to unmask]>
Message-ID:
<[log in to unmask]>
In-Reply-To:
<[log in to unmask]>
Content-Transfer-Encoding:
8bit
Sender:
Mailing list for the LaTeX3 project <[log in to unmask]>
Parts/Attachments:
text/plain (23 lines) 
On 15/02/2011, at 6:52 PM, Bruno Le Floch wrote:

>> My personal opinion on uppercasing/lowercasing is that it should be a
>> property of the font;
> 
> Both Will and Frank agree on this, but currently, in many fonts that's not
> possible.

Right :(


> Also, it is in fact possible to have an algorithm to produce
> expandably
> the result of {replacing some tokens by a corresponding macro} in a given tl.

This code you're written sounds interesting.

Does anyone have any idea what other sort of expansion-replacement code there is on CTAN?
I know of Uwe Lück's fifinddo.sty code, as part of the nicetext bundle:
  <http://ctan.unsw.edu.au/macros/latex/contrib/nicetext/>

-- Will

ATOM RSS1 RSS2