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:
Fri, 24 Feb 2006 13:18:28 +0100
Content-Disposition:
inline
Reply-To:
Mailing list for the LaTeX3 project <[log in to unmask]>
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
In-Reply-To:
Content-Type:
text/plain; charset="iso-8859-1"
From:
Philipp Lehman <[log in to unmask]>
Parts/Attachments:
text/plain (22 lines)
Am Freitag, 24. Februar 2006 11:21 schrieb Frank Mittelbach:

> again the lc/uc is not really only a property of the inputenc it is
> formost a property of the output encoding due to the unfortunate
> overloading with hyphenation.

Well, that renders my whole argument moot. Because...

>  b) the problem really only exists because of using those two
> primitives which are explicitly forbidden in LaTeX
>  c) that the model used by inputenc to manage this is actually fine

...I didn't mean to imply that there's anything wrong with inputenc. I 
was merely wondering if it could be made more robust with respect to 
primitive upper/lowercasing -- provided that there are no side 
effects!

I suppose there's no point in pursuing this further.

-- 
Philipp Lehman <[log in to unmask]>

ATOM RSS1 RSS2