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/31221] Add localedata for ISO code "tok" (Toki Pona) Date: Mon, 08 Jan 2024 09:35:42 +0000 [thread overview] Message-ID: <bug-31221-131-1OuRRa1Nee@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31221-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31221 Mike FABIAN <maiku.fabian at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2024-01-08 Assignee|unassigned at sourceware dot org |maiku.fabian at gmail dot com CC| |maiku.fabian at gmail dot com Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Mike FABIAN <maiku.fabian at gmail dot com> --- This new locale contains: +LC_MESSAGES +yesexpr "^[+1wW]" +noexpr "^[-0aA]" +yesstr "wile" +nostr "ala" +END LC_MESSAGES Most locales have yY and nN added to teh yesexpr and noexpr, except when there is a conflict. For example the sw_KE locale does not have nN in noexpr because there seems to be a conflict: $ grep expr sw_KE yesexpr "^[+1nNyY]" noexpr "^[-0hHlL]" What do you think in the case of Toki Pona, should yY and nN be in the yesexpr and noexpr or not? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-08 9:35 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-07 2:41 [Bug localedata/31221] New: " uhhadd at gmail dot com 2024-01-08 9:35 ` maiku.fabian at gmail dot com [this message] 2024-01-08 15:12 ` [Bug localedata/31221] " uhhadd at gmail dot com 2024-01-09 11:08 ` cvs-commit at gcc dot gnu.org 2024-01-09 11:09 ` 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-31221-131-1OuRRa1Nee@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).