From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: One more string functions change
Date: Sat, 28 Jun 2014 20:19:56 +0300 [thread overview]
Message-ID: <83zjgx54ub.fsf@gnu.org> (raw)
In-Reply-To: <53AEEBA3.1030706@yandex.ru>
> Date: Sat, 28 Jun 2014 20:21:55 +0400
> From: Dmitry Antipov <dmantipov@yandex.ru>
> CC: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
>
> On 06/27/2014 11:46 PM, Eli Zaretskii wrote:
>
> > That's not enough. Currently, Emacs down-cases using the current
> > buffer's settings. This is TRT in some cases, but very wrong in
> > others. It is especially wrong when down-casing strings (as opposed
> > to portions of a buffer), because there's no reason to believe that a
> > particular string being processed has any relevance to the current
> > buffer and its defaults.
>
> What makes you think that the system locale is more relevant?
I didn't say it was. I said that we currently have no way of telling
Emacs to down-case in a locale-specific manner:
> > IOW, we don't have any good way of specifying language- or
> > locale-specific case-folding.
>
> What's wrong with case tables?
They are not locale- and/or language-specific. For example,
down-casing 'I' to 'i' is wrong for Turkish.
> If we're talking about Unicode only, is it enough/possible/desirable
> to have just one (huge) case table for all supported characters?
You can't, because language-specific rules interfere. See section
5.18 in the Unicode Standard, and the SpecialCasing.txt file in the
Unicode Character Database.
> > FWIW, I think _that_ is where we should concentrate our energy, not on
> > nano-improvements such as the one proposed here. But hey! 90% of
> > Emacs development energy goes to such changes, while important missing
> > features are being left unimplemented for years. So who am I to
> > complain?
>
> "Why are you being so harsh? We are not the enemy" (C).
Sorry about that.
> If you have a personal TOTO/wishlist/roadmap/whatever, please share.
In the department we are talking about, look at the links on this
page:
http://www.unicode.org/reports/
UAX#14, UAX#15, UTS#10, and UTS#18 should all be supported by Emacs.
(And yes, I should complete my work on bringing the bidirectional
editing support in line with the additions to UAX#9 in Unicode 6.3.)
Elsewhere, the recent IDE and WYSIWYG editing discussions suggest
major improvements in functionality that at least some users sorely
miss. The FFI stuff (see on-going discussions here) is yet another.
And that's just results of a 10-sec thought.
next prev parent reply other threads:[~2014-06-28 17:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 15:27 One more string functions change Dmitry Antipov
2014-06-27 15:35 ` Andreas Schwab
2014-06-27 16:46 ` Paul Eggert
2014-06-27 19:46 ` Eli Zaretskii
2014-06-27 20:46 ` Paul Eggert
2014-06-27 20:53 ` Eli Zaretskii
2014-06-28 16:21 ` Dmitry Antipov
2014-06-28 17:19 ` Eli Zaretskii [this message]
2014-06-29 2:53 ` Dmitry Antipov
2014-06-29 15:13 ` Eli Zaretskii
2014-06-29 16:38 ` Dmitry Antipov
2014-06-29 16:48 ` Eli Zaretskii
2014-06-30 6:21 ` Internationalize Emacs's messages [Was: Re: One more string functions change] Dmitry Antipov
2014-06-28 17:26 ` One more string functions change Yuri Khan
2014-06-27 22:46 ` Drew Adams
2014-06-28 3:48 ` Dmitry Antipov
2014-06-28 13:48 ` Drew Adams
2014-06-28 16:32 ` Dmitry Antipov
2014-06-30 13:18 ` Stefan Monnier
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=83zjgx54ub.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmantipov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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).