public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cjlhomeaddress at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug localedata/14522] New: fy_DE locale query Date: Mon, 27 Aug 2012 05:36:00 -0000 [thread overview] Message-ID: <bug-14522-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14522 Bug #: 14522 Summary: fy_DE locale query Product: glibc Version: 2.15 Status: NEW Severity: normal Priority: P2 Component: localedata AssignedTo: unassigned@sourceware.org ReportedBy: cjlhomeaddress@gmail.com CC: libc-locales@sources.redhat.com Classification: Unclassified Something seems amiss with the description in fy_DE locale. title "Sater Frisian and North Frisian Locale for Germany" However West Frisian language is ISO 639-1 lang-fy (and ISO 639-2 lang-fry) http://en.wikipedia.org/wiki/West_Frisian_language Saterland (or Eastern) Frisian language is ISO 639-2 lang-frs http://en.wikipedia.org/wiki/Saterland_Frisian_language North Frisian language is ISO 639-2 lang-frr http://en.wikipedia.org/wiki/North_Frisian_language It does not appear to make sense to use ISO 639-1 lang-fy unless the language is West Frisian, but the description in the fy_DE locale seems to state otherwise. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-08-27 5:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-27 5:36 cjlhomeaddress at gmail dot com [this message] 2012-08-27 5:39 ` [Bug localedata/14522] " cjlhomeaddress at gmail dot com 2014-06-17 4:48 ` fweimer at redhat dot com 2024-01-03 19:50 ` [Bug localedata/14522] fy_DE: LC_IDENTIFICATION data looks weird maiku.fabian at gmail dot com 2024-01-03 20:31 ` cvs-commit at gcc dot gnu.org 2024-01-03 20:32 ` maiku.fabian at gmail dot com 2024-01-03 21:40 ` fweimer at redhat dot com 2024-01-04 10:37 ` 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-14522-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).