public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "berend at deschouwer dot co.za" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/31462] en_NA: new locale Date: Tue, 12 Mar 2024 10:11:24 +0000 [thread overview] Message-ID: <bug-31462-131-pyk6bQqs9p@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31462-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31462 --- Comment #5 from berend de schouwer <berend at deschouwer dot co.za> --- (In reply to Florian Weimer from comment #3) > Created attachment 15398 [details] > en_NA converted to UTF-8 > > Please use UTF-8 instead of <U00…> escapes. > > I'm attaching a semi-automatic conversion. Please double-check it. Is > country_name really what you intend? Thank you for converting it. I've checked and made two small fixes. The country_name mistake is extremely embarrassing. > The license terms should permit modification, they currently don't. If you > could disclaim copyright in the same way that the FSF does, that would be > fine. LGPL licensing terms like the rest of glibc would be acceptable as > well. I've added a similar header to the rest of the glibc source. I have no objection. I can also provide af_NA and de_NA, but not the other official languages. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-03-12 10:11 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-08 9:47 [Bug localedata/31462] New: " berend at deschouwer dot co.za 2024-03-08 19:53 ` [Bug localedata/31462] " carlos at redhat dot com 2024-03-11 5:23 ` berend at deschouwer dot co.za 2024-03-12 7:48 ` fweimer at redhat dot com 2024-03-12 10:08 ` berend at deschouwer dot co.za 2024-03-12 10:11 ` berend at deschouwer dot co.za [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=bug-31462-131-pyk6bQqs9p@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).