After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 57153 - Localize clock applet defaults
Localize clock applet defaults
Status: RESOLVED FIXED
Product: gnome-core
Classification: Deprecated
Component: gen_util
1.4.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-core Maintainers
gnome-core Maintainers
Depends on:
Blocks: 61586
 
 
Reported: 2001-07-06 03:44 UTC by Havoc Pennington
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Havoc Pennington 2001-07-06 03:44:24 UTC
See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=15395, 
choose 24h vs AM/PM according to locale. (More or less, use AM/PM only in
locales C, POSIX, and en_US)
Comment 1 Kjartan Maraas 2002-03-09 17:14:22 UTC
The bugreport isn't viewable by the public. Here's the original request:

As far as I know, it's only the US that uses AM/PM-clock as a standard
nowadays.

I think the default clock applet on the panel should default to 24h-clock
format, as it is probably what most users want.

At the very least, it should honor the locale settings in that aspect
(LC_TIME), that has a setting for AM/PM use.

Comment 2 Gediminas Paulauskas 2002-03-09 18:02:39 UTC
so I'll use nl_langinfo(AM_STR) to check if current locale has AM
string, and if yes, make 12 hour the default.

currently default format is determined from translation, but if
program is not translated, it will choose 12 hour, which is wrong.

But then, if locale does not define AM/PM strings (i.e. most of them),
the whole 12/24 setting does not make sense. what to do then? show AM
regardless of locale, or remove this option altogether?
Comment 3 Havoc Pennington 2002-03-09 21:10:41 UTC
To me the options should be the same regardless of locale, the locale
should change only the default.

I'm not sure anyone's ever tested it, but in your gconf schema you can 
in principle put the <default> entry inside the <locale> tag with 
the short/long description; that way we avoid hardcoding defaults in 
the C code, which is good. This way things keep working via gconf as
expected.

I would specify a <locale
name="en_US"><default>whatever</default></locale> for am/pm, and have
"C" use 24-hour time - that way you don't need a <locale> entry for
every language, they will all fall back to "C" - using the C locale is
broken anyway.
Comment 4 Gediminas Paulauskas 2002-03-19 07:21:52 UTC
will be in 1.5.15