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 61586 - gen_util_clock terminology
gen_util_clock terminology
Status: RESOLVED NOTABUG
Product: gnome-panel
Classification: Other
Component: clock
1.5.x
Other All
: Normal trivial
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on: 57153
Blocks:
 
 
Reported: 2001-10-02 14:39 UTC by Calum Benson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Calum Benson 2001-10-02 14:39:28 UTC
(Submitted on behalf of the GUP team):

In the Clock (gen_util_clock) properties dialog, change "Unix" to "UNIX"
for consistency with the documentation style guide.
Comment 1 Calum Benson 2001-10-02 14:41:59 UTC
Also, time is currently displayed using "AM" and "PM".  Correct usage
(according to current doc styleguide) is "a.m." and "p.m.".

(Although I'm personally not sure this would work so well on-screen--
perhaps we could compromise on "am" and "pm" for the screen version?)
Comment 2 John Fleck 2002-02-11 00:09:55 UTC
adding GNOME2 keyword
Comment 3 Gediminas Paulauskas 2002-02-20 22:56:40 UTC
these are strings, and now we are in string freeze. will it be ok to
change that?

am/a.m./AM should be represented as it is by default in locale, i.e.
strftime ("%p")

In my locale, there is no such thing as 12 hour format or AM/PM
strings. It would be nice if programs did not offer such option at all
(as Evolution does -- if locale does not define am/pm strings, does
not use 12-hour formats)
Comment 4 Luis Villa 2002-02-28 16:10:47 UTC
Gediminas: I assume that a patch for this would be accepted by the
release team and docs people if you wrote to release team and
requested it.
Comment 5 Gediminas Paulauskas 2002-03-09 18:27:16 UTC
I'll fix UNIX

I guess no locales use a.m. and p.m., everywhere is AM/PM or just
nothing. It's strange that styleguides suggest different thing than
used in real clocks and other coputer clocks.

using am/pm vs. AM/PM is just a matter of strftime ("%P") vs strftime
("%p"), so I can change that if desired.

so the question is: do we want to use locale-defined strings (i.e.
nothing) or hardcode a.m./p.m. for all locales?

the whole AM abbreviation comes from latin or from sailors' slang, so
doesn't mean anything to most people in the world..
Comment 6 Patrick Costello 2002-03-11 14:37:47 UTC
The reasoning for the recommendation of a.m. and p.m. is as follows: 

These are the standard abbreviations that are recommended in the
American Heritage Dictionary, and Merriam-Websters International
Dictionary. 

Whereas it is true that a.m. and p.m. are abbreviations of Latin
terms, that does not mean that we should use incorrect versions of the
abbreviations, such as AM and PM. Also, if a locale does not use a 12
hour clock, then the problem does not lie with the abbreviations a.m.
and p.m., the problem lies with the availability of a 12 hour clock
for those locales. 

In locales where a 12 hour clock is used, the correct abbreviations to
indicate the day median are a.m. and p.m., as recommended in the GNOME
Documentation Style Guide. 

Also, other applets, applications and documentation may mention the 12
hour clock. Therefore, everyone needs to follow a standardized
approach, so that there is consistency across applications, manuals
and the desktop.
Comment 7 Mark McLoughlin 2002-03-27 16:49:33 UTC
Gediminas is correct in what he's saying. If we want a.m. instead of
p.m. we need to get our libc changed. We are just using the result
from strftime and its there the work would have happened to get time
formats correct for different locales.