public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/18918] hu_HU: change time to HH:MM:SS format
Date: Sat, 17 Oct 2015 04:16:00 -0000	[thread overview]
Message-ID: <bug-18918-131-6N4EFNbt1G@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18918-131@http.sourceware.org/bugzilla/>

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

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  c7266a2d8204b1a105df1a1f11d56319f0093d13 (commit)
      from  8fe5f986c86c6505bd887e02135fa41bfde4f552 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c7266a2d8204b1a105df1a1f11d56319f0093d13

commit c7266a2d8204b1a105df1a1f11d56319f0093d13
Author: Egmont Koblinger <egmont@gmail.com>
Date:   Tue Oct 13 20:48:55 2015 +0200

    hu_HU: change time separator to colon [BZ #18918]

    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.

    Microsoft also uses and recommends a colon since at least May 2011:
   
http://download.microsoft.com/download/e/6/1/e61266b2-d8b4-4fe0-a553-f01dc3976675/hun-hun-StyleGuide.pdf
      The time format is different in common language and in the language of
      IT. In common texts we usually do not abbreviate, so the full forms are
      used: “7 óra 10 perckor csörgött a telefon”. However, the short format,
      consisting of numerals only, can also be used. In this case a period
      must be used between the two numbers and there must not be a space
      between them: “találkozzunk 10.45-kor”.

      However, in software mostly the short format is used, and the numbers
      are separated by a colon. An obvious example is the clock in the bottom
      right corner of your screen, thus 18:31.

-----------------------------------------------------------------------

Summary of changes:
 NEWS                     |   10 +++++-----
 localedata/ChangeLog     |    5 +++++
 localedata/locales/hu_HU |   10 +++++-----
 3 files changed, 15 insertions(+), 10 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-30202-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat Oct 17 04:17:33 2015
Return-Path: <glibc-bugs-return-30202-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 18841 invoked by alias); 17 Oct 2015 04:17:33 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 18775 invoked by uid 48); 17 Oct 2015 04:17:28 -0000
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/18918] hu_HU: change time to HH:MM:SS format
Date: Sat, 17 Oct 2015 04:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: localedata
X-Bugzilla-Version: 2.22
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: vapier at gentoo dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: 2.23
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-18918-131-prA3U0ogCw@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-18918-131@http.sourceware.org/bugzilla/>
References: <bug-18918-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg00239.txt.bz2
Content-length: 593

https://sourceware.org/bugzilla/show_bug.cgi?id\x18918

Mike Frysinger <vapier at gentoo dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |2.23

--- Comment #3 from Mike Frysinger <vapier at gentoo dot org> ---
should be pushed now in master.  thanks!

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


      parent reply	other threads:[~2015-10-17  4:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 14:04 [Bug localedata/18918] New: Change to HH:MM:SS format in Hungarian locale egmont at gmail dot com
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 [this message]

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-6N4EFNbt1G@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).