all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Elias Oltmanns <oltmanns@uni-bonn.de>
Subject: Re: New buffer-case-table makes search_buffer painfully slow
Date: Fri, 12 May 2006 16:16:20 +0200	[thread overview]
Message-ID: <87hd3vs4zv.fsf@denkblock.local> (raw)
In-Reply-To: E1FcbOZ-0002Yz-Mj@fencepost.gnu.org

Richard Stallman <rms@gnu.org> wrote:
>     Emacs 22's EQUIVALENCES table relates i, and thus I as well, to
>     two more characters with character codes 331857 and 331856. On
>     www.unicode.org the character look up engine couldn't find a
>     match for U+51051 or U+51050 saying that most likely those codes
>     weren't assigned to any characters yet.
>
> I think this has to do with the special characters for Turkish,
> lower-case i without dot and upper-case I with dot. In Turkish,
> upcasing and downcasing preserve the dot, or the absence of the dot.
>
> I think these lines in characters.el are the cause of the problem.
>
>   (set-downcase-syntax ?? ?i tbl) (set-upcase-syntax ?I ?? tbl)
>
> They set up only half of what Turkish needs. They make dotless-i
> upcase into I, and they make I-with-dot downcase into i. They can't
> do vice versa because that would break things for other languages.
> So they are not really useful. We could simply delete them.
>
> We could also add a minor mode to set up the case table all the way
> for Turkish.

When I come to think of it, I'm not quite sure I understand what
exactly you have in mind with regard to the minor mode option.
Unfortunately, I don't know anything about Turkish at all, but I'd
imagine that while you're editing pure Turkish texts, you'd like to
have a matching pair of dotless and dotted up- and downcase i
respectively. That way up- and downcasing work properly and case
insensitive searches for an i would not match the dotless
versions---as expected, I suppose.

If you're editing mixed texts as, for instance, Turkish and English,
the current behaviour with i matching all four characters might be
more convenient; the same applies if you switch between Turkish and
other languages rather frequently.

The third option, which from my very biased point of view should be
the default, is that ASCII i should only match its ASCII upcase
counterpart.

How would you realise all these needs?

Regards,

Elias

  reply	other threads:[~2006-05-12 14:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 13:46 New buffer-case-table makes search_buffer painfully slow Elias Oltmanns
2006-05-06 19:10 ` Elias Oltmanns
2006-05-06 20:17   ` Andreas Schwab
2006-05-07  5:01   ` Richard Stallman
2006-05-12 14:16     ` Elias Oltmanns [this message]
2006-05-13  4:53       ` Richard Stallman

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=87hd3vs4zv.fsf@denkblock.local \
    --to=oltmanns@uni-bonn.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.