From: "mbalk at mbalk dot de" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/20482] New: de_CH: abbreviated weekdays are incorrect
Date: Wed, 17 Aug 2016 21:13:00 -0000 [thread overview]
Message-ID: <bug-20482-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=20482
Bug ID: 20482
Summary: de_CH: abbreviated weekdays are incorrect
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: mbalk at mbalk dot de
CC: libc-locales at sourceware dot org
Target Milestone: ---
Currently weekdays are abbreviated with three letters. That is not correct.
According to chapter 5.3.3 in
https://www.bk.admin.ch/dokumentation/sprachen/04915/05016/index.html?lang=de&download=NHzLpZeg7t,lnp6I0NTU042l2Z6ln1acy4Zn4Z2qZpnO2Yuq2Z6gpJCHe393gWym162epYbg2c_JjKbNoKSn6A--
weekdays have to be abbreviated with two letters and without a dot, e.g.
"Mo" for Montag (Monday), "Di" for Dienstag (Tuesday) and so on.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-08-17 21:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 21:13 mbalk at mbalk dot de [this message]
2016-08-17 21:13 ` [Bug localedata/20482] " mbalk at mbalk dot de
2016-08-17 21:40 ` [Bug localedata/20482] de_CH: abbreviated weekdays should be two letters vapier at gentoo dot org
2016-08-18 8:39 ` fweimer at redhat dot com
2017-08-14 15:03 ` maiku.fabian at gmail dot com
2017-08-14 15:07 ` maiku.fabian at gmail dot com
2017-08-14 15:22 ` maiku.fabian at gmail dot com
2017-08-14 15:24 ` cvs-commit at gcc dot gnu.org
2017-08-14 16:50 ` maiku.fabian at gmail dot com
2017-08-30 13:04 ` maiku.fabian at gmail dot com
2017-08-30 13:04 ` 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-20482-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).