From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16731@debbugs.gnu.org
Subject: bug#16731: 24.3.50; Latin small letter sharp s is not considered lower-case
Date: Thu, 13 Feb 2014 18:58:04 +0100 [thread overview]
Message-ID: <CAAeL0SQPTchZQ8NGnU-WLk2K8o8iPSPQ9VjomWMiW0ecsOpy=g@mail.gmail.com> (raw)
In-Reply-To: <83y51fq8fy.fsf@gnu.org>
On Thu, Feb 13, 2014 at 5:33 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> If the approach below is accepted, a related question is how to treat
> letters whose category is Lt, i.e. "titlecase" -- do we consider such
> letters upper case or don't we?
No Unicode expert, but this suggest they are uppercase, sort of:
http://www.unicode.org/faq/casemap_charprop.html
"Q: What is titlecase? How is it different from uppercase?
A: Titlecase takes its name from the case format used when forming a
title, in which the initial letter in a word is capitalized and the
rest are not. Titlecase is also used in forming a sentence by
capitalizing the first word, and for forming proper names. The
titlecase mapping in the Unicode Standard is the mapping applied to
the initial character in a word.
The titlecase mapping in Unicode differs from the uppercase mapping in
that a number of characters require special handling. These are
chiefly ligatures and digraphs such as 'fl', 'dz', and 'lj', plus a
number of polytonic Greek characters. For example, U+01C7 (LJ) maps to
U+01C8 (Lj) rather than to U+01C9 (lj)."
next prev parent reply other threads:[~2014-02-13 17:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 17:29 bug#16731: 24.3.50; Latin small letter sharp s is not considered lower-case Jorgen Schaefer
2014-02-12 17:55 ` Glenn Morris
2014-02-12 19:31 ` Andreas Röhler
2014-02-12 19:49 ` Eli Zaretskii
2014-02-12 20:10 ` Andreas Röhler
2014-02-12 20:16 ` Eli Zaretskii
2014-02-12 20:33 ` Andreas Röhler
2014-02-12 20:57 ` Juanma Barranquero
2014-02-13 3:46 ` Eli Zaretskii
2014-02-13 8:27 ` Andreas Röhler
2014-02-13 15:53 ` Eli Zaretskii
2014-02-13 13:37 ` Stefan Monnier
2014-02-13 16:33 ` Eli Zaretskii
2014-02-13 17:10 ` Stefan Monnier
2014-02-13 17:39 ` Eli Zaretskii
2014-02-13 18:02 ` Andreas Röhler
2014-02-13 18:17 ` Eli Zaretskii
2014-02-13 18:10 ` Stefan Monnier
2014-02-13 18:16 ` Eli Zaretskii
2014-02-13 19:15 ` Stefan Monnier
2014-02-13 20:24 ` Eli Zaretskii
2014-02-14 17:22 ` Stefan Monnier
2014-02-14 18:16 ` Eli Zaretskii
2014-02-14 20:59 ` Stefan Monnier
2014-02-15 7:12 ` Eli Zaretskii
2014-02-17 3:09 ` Stefan Monnier
2014-02-17 5:29 ` Eli Zaretskii
2014-02-13 17:58 ` Juanma Barranquero [this message]
2014-02-13 18:18 ` Eli Zaretskii
2014-02-13 18:22 ` Juanma Barranquero
2014-02-13 18:47 ` Glenn Morris
2014-02-13 20:16 ` Eli Zaretskii
2014-02-14 16:20 ` bug#16731: 24.3.50; , " Paul Eggert
2021-07-16 12:32 ` bug#10576: Subject: 23.4; char class [:lower:] misses latin small letter sharp s Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAeL0SQPTchZQ8NGnU-WLk2K8o8iPSPQ9VjomWMiW0ecsOpy=g@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=16731@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).