From: "uwe at NetBSD dot org" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/31086] New: Errors in Tibetan, Dzongkha data
Date: Fri, 24 Nov 2023 21:13:53 +0000 [thread overview]
Message-ID: <bug-31086-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31086
Bug ID: 31086
Summary: Errors in Tibetan, Dzongkha data
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: uwe at NetBSD dot org
CC: libc-locales at sourceware dot org
Target Milestone: ---
Created attachment 15227
--> https://sourceware.org/bugzilla/attachment.cgi?id=15227&action=edit
Spelling errors in Dzongha data
Tibetan/Dzongkha locale data have multiple typos, primarily in LC_TIME data.
Some names have incorrect "pha" instead of "pa" at the end.
"First" is "dang po", not "dang pa".
Weirdly, some superscribed "sa" was reordered with the next subscribed letter
(in "spyi", "skar", "snga")
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-11-24 21:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 21:13 uwe at NetBSD dot org [this message]
2023-11-24 21:20 ` [Bug localedata/31086] " uwe at NetBSD dot org
2023-11-24 21:21 ` uwe at NetBSD dot org
2023-11-24 22:14 ` uwe at NetBSD dot org
2023-11-24 22:31 ` uwe at NetBSD dot org
2023-11-24 22:40 ` uwe at NetBSD dot org
2024-01-08 14:50 ` maiku.fabian at gmail dot com
2024-01-08 18:33 ` cvs-commit at gcc dot gnu.org
2024-01-08 18:33 ` cvs-commit at gcc dot gnu.org
2024-01-08 18:33 ` cvs-commit at gcc dot gnu.org
2024-01-08 18:33 ` cvs-commit at gcc dot gnu.org
2024-01-08 18:39 ` maiku.fabian at gmail dot com
2024-01-08 18:40 ` maiku.fabian at gmail dot com
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=bug-31086-716@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sourceware.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.
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).