From: Benno Schulenberg via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org
Subject: [PATCH] manual: replace an obsolete collation example with a valid one
Date: Mon, 12 Oct 2020 17:11:47 +0200 [thread overview]
Message-ID: <20201012151147.4647-1-bensberg@telfort.nl> (raw)
In the Spanish language, the digraph "ll" has not been considered a
separate letter since 1994:
https://www.rae.es/consultas/exclusion-de-ch-y-ll-del-abecedario
Since January 1998 (commit 49891c106244888123557fca7fddda4fa1f96b1d),
glibc's locale data no longer specifies "ch" and "ll" as separate
collation elements. So, it's better to not use "ll" in an example.
Also, the Czech "ch" is a better example as it collates in a more
surprising place.
---
manual/string.texi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/manual/string.texi b/manual/string.texi
index 23f516439a..ad11519377 100644
--- a/manual/string.texi
+++ b/manual/string.texi
@@ -1422,9 +1422,9 @@ This is an obsolete alias for @code{memcmp}, derived from BSD.
In some locales, the conventions for lexicographic ordering differ from
the strict numeric ordering of character codes. For example, in Spanish
most glyphs with diacritical marks such as accents are not considered
-distinct letters for the purposes of collation. On the other hand, the
-two-character sequence @samp{ll} is treated as a single letter that is
-collated immediately after @samp{l}.
+distinct letters for the purposes of collation. On the other hand, in
+Czech the two-character sequence @samp{ch} is treated as a single letter
+that is collated between @samp{h} and @samp{i}.
You can use the functions @code{strcoll} and @code{strxfrm} (declared in
the headers file @file{string.h}) and @code{wcscoll} and @code{wcsxfrm}
--
2.25.4
next reply other threads:[~2020-10-12 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 15:11 Benno Schulenberg via Libc-alpha [this message]
2020-10-13 13:00 ` [PATCH] manual: replace an obsolete collation example with a valid one Florian Weimer via Libc-alpha
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/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201012151147.4647-1-bensberg@telfort.nl \
--to=libc-alpha@sourceware.org \
--cc=bensberg@telfort.nl \
/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).