Received: by nummer-3.proteosys id <01C19443.9B0B1E9C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:22 +0100 Return-Path: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.9B0B1E9C" 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: {2} Re: {1} URGENT Date: Thu, 20 Feb 1992 09:51:29 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Mustafa Akgul" Sender: "LaTeX-L Mailing list" To: "Multiple recipients of" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 576 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.9B0B1E9C 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. best regards ------_=_NextPart_001_01C19443.9B0B1E9C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable {2} Re: {1} URGENT

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.

best regards

------_=_NextPart_001_01C19443.9B0B1E9C--