From: "toregilhk at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/25868] New: Incorrect trailing spaces in weekday names for nn_NO
Date: Thu, 23 Apr 2020 17:08:54 +0000 [thread overview]
Message-ID: <bug-25868-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25868
Bug ID: 25868
Summary: Incorrect trailing spaces in weekday names for nn_NO
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: toregilhk at hotmail dot com
CC: libc-locales at sourceware dot org
Target Milestone: ---
For the locale nn_NO, the full weekday names (%A) have a trailing whitespace
that should, as far as I can tell, not be there.
In
https://sourceware.org/git/?p=glibc.git;a=blob;f=localedata/locales/nn_NO;h=c8da4ce086d0b8a9918b560b6588bf81e957b367;hb=refs/heads/master
you have the following:
91 % Full weekday names (%A)
92 day "sundag ";/
93 "m<U00E5>ndag ";/
94 "tysdag ";/
95 "onsdag ";/
96 "torsdag ";/
97 "fredag ";/
98 "laurdag "
which I believe should be corrected to
91 % Full weekday names (%A)
92 day "sundag";/
93 "m<U00E5>ndag";/
94 "tysdag";/
95 "onsdag";/
96 "torsdag";/
97 "fredag";/
98 "laurdag"
with the trailing spaces removed.
The locale file for nb_NO, in contrast, do not have the trailing whitespace,
which is correct.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-04-23 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 17:08 toregilhk at hotmail dot com [this message]
2023-11-29 9:41 ` [Bug localedata/25868] " maiku.fabian at gmail dot com
2023-12-07 7:54 ` cvs-commit at gcc dot gnu.org
2023-12-07 7:57 ` 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-25868-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).