Received: by nummer-3.proteosys id <01C19443.9DC27324@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:27 +0100 Return-Path: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.9DC27324" x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: {1} Re: {?} more Refname's Date: Mon, 2 Mar 1992 17:52:46 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Frank Mittelbach" Sender: "LaTeX-L Mailing list" To: "Multiple recipients of" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 600 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.9DC27324 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > This is a request about Uppercase prompted by Yannis's request. > > In standard LaTeX sty's the use of contruct such as > \uppercase{\refname} is potentially problematic in > at least non-western languages. It is definitely so in > Turkish, for we have \i <-> I and i <->\.I. > I suggest we introduce some more control sequences > such as \Refname and replace \uppercase{\refname} with > \Refname in macros. > Such an approach unfortunately doesn't solve the general problem with uppercasing text. Currently we have to deal with the situation that arbitray text from the headings argument may be subject to uppercasing. therefore getting the word ``chapter'' right but the rest of the line wrong doesn't help very much. This would work only for those headings that don't have user supplied material. Therefore I think that a solution is only possible by using slow parsing of the argument and whether this is feasible is a different question. Frank ------_=_NextPart_001_01C19443.9DC27324 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable {1} Re: {?} more Refname's

> This is a request about Uppercase prompted by = Yannis's request.
>
> In standard LaTeX sty's the use of contruct such = as
> \uppercase{\refname} is potentially problematic = in
> at least non-western languages. It is definitely = so in
> Turkish, for we have \i <-> I and i = <->\.I.
> I suggest we introduce some more control = sequences
> such as \Refname and replace = \uppercase{\refname} with
> \Refname in  macros.
>

Such an approach unfortunately doesn't solve the = general problem with
uppercasing text. Currently we have to deal with the = situation that
arbitray text from the headings argument may be = subject to
uppercasing. therefore getting the word ``chapter'' = right but the rest
of the line wrong doesn't help very much. This would = work only for
those headings that don't have user supplied = material. Therefore I
think that a solution is only possible by using slow = parsing of the
argument and whether this is feasible is a different = question.

Frank

------_=_NextPart_001_01C19443.9DC27324--