From: Keld Simonsen <keld@keldix.com>
To: tiagosilva at hush dot com <sourceware-bugzilla@sourceware.org>
Cc: libc-locales@sourceware.org
Subject: Re: [Bug localedata/17565] New: Wrong (work-)week start for pt_PT
Date: Fri, 07 Nov 2014 21:52:00 -0000 [thread overview]
Message-ID: <20141107215253.GD25877@rap.rap.dk> (raw)
In-Reply-To: <bug-17565-716@http.sourceware.org/bugzilla/>
Sounds OK to me.
I was the first to submit a pt_PT locale to glibc,
but I am not sure I am still the primary author on the pt_PT
spec.
Best regards
Keld
On Fri, Nov 07, 2014 at 05:20:28PM +0000, tiagosilva at hush dot com wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=17565
>
> Bug ID: 17565
> Summary: Wrong (work-)week start for pt_PT
> Product: glibc
> Version: unspecified
> Status: NEW
> Severity: normal
> Priority: P2
> Component: localedata
> Assignee: unassigned at sourceware dot org
> Reporter: tiagosilva at hush dot com
> CC: libc-locales at sourceware dot org
>
> According to the default pt_PT definitions, the (work-)week start is set at
> Sunday, which is incorrect.
>
> The (work-)week start is Monday, because Portugal abides by EN 28601:1992,
> since it became an UE member 6 years prior to issue of that norm.
>
> pt_PT was the only EU locale that did not get the needed correction in these
> definitions.
>
> Therefore I request to have the first_weekday and first_workday entries entries
> set at LC_TIME with the default value of 2 for the pt_PT locale.
>
> Thank you.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
next prev parent reply other threads:[~2014-11-07 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 21:48 tiagosilva at hush dot com
2014-11-07 21:48 ` [Bug localedata/17565] " tiagosilva at hush dot com
2014-11-07 21:52 ` Keld Simonsen [this message]
2014-11-08 0:10 ` keld at keldix dot com
2016-02-19 10:49 ` [Bug localedata/17565] pt_PT: wrong (work-)week start vapier at gentoo dot org
2016-03-04 12:13 ` tiagosilva at hush dot com
2016-03-04 12:28 ` tiagosilva at hush dot com
2016-04-16 7:38 ` vapier at gentoo dot org
2016-04-23 7:10 ` vapier at gentoo dot org
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=20141107215253.GD25877@rap.rap.dk \
--to=keld@keldix.com \
--cc=libc-locales@sourceware.org \
--cc=sourceware-bugzilla@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).