Bug 67054 – [RFE] in TZ sel, UTC explanation

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 67054 - [RFE] in TZ sel, UTC explanation

Summary:	[RFE] in TZ sel, UTC explanation

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Public Beta
Classification:	Retired
Component:	anaconda-help (Show other bugs)
Sub Component:
Version:	limbo
Hardware:	i386 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Sandra Moore
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-06-19 13:28 EDT by James Manning
Modified:	2014-08-04 18:23 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-07-12 00:09:53 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description James Manning 2002-06-19 13:28:44 EDT

a tad pedantic, but the help in TZ sel says Universal Coordinated Time (UTC) but
never really explains why it's UTC instead of UCT (why the letters reverse). 
I'm like 90% sure that it's like FIFA and the reversal is because it's natively
in a diff language, but it'd be a nice touch if it said something like that
and/or showed the real "source".

Also, many sites seem to think that the real name is "Coordinated Universal
Time" - a google search makes it obvious, such as

http://aa.usno.navy.mil/faq/docs/UT.html

maybe it's best done by just saying "Universal Time, Coordinated" (UTC)

Comment 1 Sandra Moore 2002-07-12 10:22:00 EDT

Help text will now say: Universal Time, Coordinated  (UTC)

Thanks for the feedback.  The updated help text will be available in the next
release.

Note You need to log in before you can comment on or make changes to this bug.