public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "keld at keldix dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/17692] Wrong currency_symbol for da_DK
Date: Tue, 09 Dec 2014 23:27:00 -0000	[thread overview]
Message-ID: <bug-17692-716-Jp4JrfDW8O@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17692-716@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17692

--- Comment #2 from keld at keldix dot com <keld at keldix dot com> ---
On Tue, Dec 09, 2014 at 08:19:28PM +0000, glibc at chsc dot dk wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=17692
> 
>             Bug ID: 17692
>            Summary: Wrong currency_symbol for da_DK
>            Product: glibc
>            Version: unspecified
>             Status: NEW
>           Severity: normal
>           Priority: P2
>          Component: localedata
>           Assignee: unassigned at sourceware dot org
>           Reporter: glibc at chsc dot dk
>                 CC: libc-locales at sourceware dot org
> 
> The currency_symbol for da_DK should be changed from "kr" to "kr." (i.e. with a
> trailing period).
> 
> "kr." is the official spelling[1,2] according to Retskrivningsordbogen[3]
> published by the Danish Language Council (Dansk Sprognævn) that is the official
> regulatory body of the Danish language.
> 
> "kr" is sometimes used informally, but I believe "kr." is much more widespread.
> To get an impression, see e.g. [4].
> 
> 
> AFAICT "kr" is the preferred spelling in Norway[5] and Sweden[6]. Perhaps this
> is how "kr" made its way into da_DK also (it has been unchanged since da_DK was
> added to Git/CVS in 1997).
> 
> 
> I raised this issue to the contact person for da_DK, Keld Simonsen, in January
> 2014. He responded that he would look into it, but so far I have not received
> any feedback.
> 
> 
> [1] http://sproget.dk/lookup?SearchableText=kr
> [2]
> http://sproget.dk/raad-og-regler/retskrivningsregler/retskrivningsregler/a7-40-60/a7-41-43-punktum/a7-42-forkortelsespunktum/
> [3] https://en.wikipedia.org/wiki/Retskrivningsordbogen
> [4] https://www.google.dk/search?q=priser+kr+site:dk
> [5] http://www.korrekturavdelingen.no/K4Forkortelser.htm
> [6] http://www.regeringen.se/content/1/c6/13/15/83/7be35768.pdf#page=55

I cheked it once more and I can verify that it is both the official  rule and
also widespread current practice.

Keld

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2014-12-09 23:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09 20:24 [Bug localedata/17692] New: " glibc at chsc dot dk
2014-12-09 20:25 ` [Bug localedata/17692] " glibc at chsc dot dk
2014-12-09 20:25 ` glibc at chsc dot dk
2014-12-09 23:05 ` [Bug localedata/17692] New: " Keld Simonsen
2014-12-09 23:27 ` keld at keldix dot com [this message]
2015-02-09 21:59 ` [Bug localedata/17692] " glibc at chsc dot dk
2015-02-09 21:59 ` glibc at chsc dot dk
2015-02-16 21:19 ` siddhesh at redhat dot com
2015-04-11 19:51 ` glibc at chsc dot dk
2015-04-13 13:42 ` cjlhomeaddress at gmail dot com
2015-05-07  6:30 ` siddhesh at redhat 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-17692-716-Jp4JrfDW8O@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).