[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#808143: bg_BG locale should use colon as time separator, not comma



Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=19385

-=| Aurelien Jarno, 16.12.2015 14:35:56 +0100 |=-
> On 2015-12-16 12:43, Damyan Ivanov wrote:
> > Package: locales
> > Version: 2.21-4
> > Severity: normal
> > Tags: upstream patch
> > 
> > The time format specified in the bg_BG locale is:
> > 
> >  $ locale -k t_fmt t_fmt_ampm date_fmt
> >  t_fmt="%k,%M,%S"
> >  t_fmt_ampm="%l,%M,%S"
> >  date_fmt="%a %b %e %H:%M:%S %Z %Y"
> > 
> > t_fmt[_ampm] should use colons instead of commas, like date_fmt already does.
> 
> Do you have a source saying the format you suggest is the correct one?
> Is it something that has changed recently? The format you suggest was
> the one in use prior to commit fa13c459, so I would like to understand
> why it has been changed at that time.

The only source is a dictionary of the official Bulgarian language 
(available only in paper form), which in its 2012 edition allows 
comma, colon and dot for separating, without stating any preference.

In 2001, when fa13c459 was made, there were no official permission to 
use anything but a comma for time separator. I'd argue that no one 
used comma at that time either, but the author of the change followed 
the official papers.

Later the dictionary was adapted to reality to also permit colon and 
dot.

I am pretty sure the colon is used everywhere and the comma only leads 
to confusion, because it is the official decimal separator.

> Ideally it would be nice if you can send the patch upstream, so that you
> can give the arguments for the change directly there, instead of having
> us to proxy them.

Understood. I filed a request upstream, after gathering some formal 
support along the translators of free software in Bulgarian.


Cheers,
    dam

Attachment: signature.asc
Description: Digital signature


Reply to: