all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Werner LEMBERG <wl@gnu.org>
Cc: philip@warpmail.net, 42064@debbugs.gnu.org
Subject: bug#42064: 28.0.50; German "Sharp S" is capitalized inconsistenly
Date: Mon, 19 Oct 2020 08:57:31 +0000	[thread overview]
Message-ID: <CADwFkmmJFLL17HN3OYt73BZ+BKEkTZbg6DFd8ss5cU=E3aqp+Q@mail.gmail.com> (raw)
In-Reply-To: <20201019.083145.1926465227104280220.wl@gnu.org>

tags 42064 + wontfix notabug
close 42064
thanks

Werner LEMBERG <wl@gnu.org> writes:

> AFAICS, the behaviour of the German postfix input method is fully
> correct.  The default lowercase/uppercase pairing is 'ß/SS'. 'ẞ'
> should not be a target of 'uppercase-fication'; its use is very
> special.[*]
>
>> Does that mean that this is a wontfix?
>
> I suggest so.

Thanks Werner, your explanation was both interesting and helpful.

Based on that, I'm closing this bug report now.

> [*] Mainly a solution to indicate 'ß' in names that have to be written
>     in uppercase letters.  Consider the names 'Strauss' and 'Strauß',
>     which both occur in German and have to be distinguished in
>     passports, where family names are to be written in uppercase:
>     'STRAUSS' and 'STRAUẞ'.  However, in every other context, they
>     should be both uppercased as 'STRAUSS'.





      reply	other threads:[~2020-10-19  8:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 18:44 bug#42064: 28.0.50; German "Sharp S" is capitalized inconsistenly Philip K.
2020-06-26 18:55 ` Eli Zaretskii
2020-06-26 19:08   ` Philip K.
2020-06-26 19:36     ` Eli Zaretskii
2020-10-18  1:39       ` Stefan Kangas
2020-10-19  3:42         ` Richard Stallman
2020-10-19  8:57           ` Stefan Kangas
2020-10-19  6:31         ` Werner LEMBERG
2020-10-19  8:57           ` Stefan Kangas [this message]

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='CADwFkmmJFLL17HN3OYt73BZ+BKEkTZbg6DFd8ss5cU=E3aqp+Q@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=42064@debbugs.gnu.org \
    --cc=philip@warpmail.net \
    --cc=wl@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 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.