From: "Eli Zaretskii" <eliz@elta.co.il>
To: ezannoni@redhat.com
Cc: gdb@sources.redhat.com, jimb@redhat.com
Subject: Re: charset.c problem with non-en_US locales
Date: Wed, 23 Apr 2003 09:45:00 -0000 [thread overview]
Message-ID: <7826-Wed23Apr2003124156+0300-eliz@elta.co.il> (raw)
In-Reply-To: <16037.41011.517603.566953@localhost.redhat.com> (message from Elena Zannoni on Tue, 22 Apr 2003 16:04:03 -0400)
> From: Elena Zannoni <ezannoni@redhat.com>
> Date: Tue, 22 Apr 2003 16:04:03 -0400
>
> When the locale is set to Turkish (or any other non-Latin), the
> tolower/toupper functions don't work as they would in English. The
> lowercase version of 'I' is not 'i', for instance but some other
> chracter ('i' w/o the dot).
Right, that's one peculiarity of the Turkish language.
> So, I think the whole case-insensitive approach for the names of the
> charsets and the translation tables should probably be removed.
I'm not sure.
> What was the reason behind it? Was it that the user could type
> upper/lower case charset names at the command line?
Yes, that's the reason.
> This patch works, but I am not confident that this it's enough.
How about having our own clang_tolower function, which modifies only
7-bit ASCII characters in its argument? Wouldn't this be a better
solution than requesting the user to type in a certain letter-case?
next prev parent reply other threads:[~2003-04-23 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 19:59 Elena Zannoni
2003-04-23 9:45 ` Eli Zaretskii [this message]
2003-04-23 17:00 ` H. J. Lu
2003-04-23 19:45 ` Andrew Cagney
2003-04-24 2:35 ` Jim Blandy
2003-04-24 20:07 ` Elena Zannoni
2003-04-24 20:26 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7826-Wed23Apr2003124156+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).