public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egmont at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/18918] New: Change to HH:MM:SS format in Hungarian locale
Date: Thu, 03 Sep 2015 14:04:00 -0000	[thread overview]
Message-ID: <bug-18918-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 18918
           Summary: Change to HH:MM:SS format in Hungarian locale
           Product: glibc
           Version: 2.22
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: localedata
          Assignee: unassigned at sourceware dot org
          Reporter: egmont at gmail dot com
                CC: libc-locales at sourceware dot org
  Target Milestone: ---

Created attachment 8576
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8576&action=edit
Use colon instead of dot

Could you please apply the attached patch? It changes the time format from
HH.MM.SS to HH:MM:SS in the Hungarian locale.

The previous (11th) version of the Hungarian spelling rules (released in 1984)
said that the separator had to be a dot, e.g. 10.35 meaning 10 o'clock 35
minutes. glibc correctly implements this.

The brand new (12th) version, in effect since September 1, 2015 adopts to the
common use of colon (especially in the digital world) and allows to use either
separator, without even expressing a preference.

For computer systems, using colons is way more typical and probably easier to
recognize. Dot is typically used in printed materials.

It also avoids an almost ambiguous situation where a space makes a difference,
e.g. "10.15-ig" means "until 10 o'clock 15 minutes" whereas "10. 15-ig" means
"until 15th of October". So I believe using the colon as the separator is not
only more frequent in the computer world, but is also easier and quicker to
recognize for the brain that it's about hour:minute rather than month and day.
And luckily it's now equally correct according to the official rules.

11th edition: http://helyesiras.mta.hu/helyesiras/default/akh11

12th edition: http://helyesiras.mta.hu/helyesiras/default/akh12

In both editions it's the very last (299th and 300th, respectively) rule.

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


             reply	other threads:[~2015-09-03 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 14:04 egmont at gmail dot com [this message]
2015-09-08 17:38 ` [Bug localedata/18918] [Patch] " egmont at gmail dot com
2015-09-13  1:07 ` [Bug localedata/18918] hu_HU: change time to HH:MM:SS format vapier at gentoo dot org
2015-09-13  1:07 ` [Bug localedata/18918] [Patch] Change to HH:MM:SS format in Hungarian locale vapier at gentoo dot org
2015-10-13 18:45 ` [Bug localedata/18918] hu_HU: change time to HH:MM:SS format egmont at gmail dot com
2015-10-17  4:16 ` cvs-commit at gcc dot gnu.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=bug-18918-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).