public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/31086] Errors in Tibetan, Dzongkha data Date: Mon, 08 Jan 2024 18:39:51 +0000 [thread overview] Message-ID: <bug-31086-131-e5Cwys57JY@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31086-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31086 Mike FABIAN <maiku.fabian at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2024-01-08 --- Comment #9 from Mike FABIAN <maiku.fabian at gmail dot com> --- I also converted the dz_BT and bo_CN locale sources to UTF-8: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=e171ad7d596878d0d4f21a0713d8dbb8d8788d7e -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-08 18:39 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-24 21:13 [Bug localedata/31086] New: " uwe at NetBSD dot org 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 [this message] 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-131-e5Cwys57JY@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).