Bug 71926 - anaconda/po/timeconfig/timeconfig.pot should be updated.
Summary: anaconda/po/timeconfig/timeconfig.pot should be updated.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: timeconfig
Version: null
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks: 67217
TreeView+ depends on / blocked
 
Reported: 2002-08-20 10:05 UTC by Nakai
Modified: 2007-04-18 16:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-08-22 03:34:34 UTC
Embargoed:


Attachments (Terms of Use)

Description Nakai 2002-08-20 10:05:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020528

Description of problem:
anaconda/po/timeconfig/timeconfig.pot should be updated.
ja.po are fully translated, but still there are many
untranslated region strings in timezone. That is because
timeconfig.pot is outdated.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.See anaconda timezone
2.Many untranslated strings.
3.
	

Additional info:

Comment 1 Jeremy Katz 2002-08-21 05:18:57 UTC
Could you give an example of one which is untranslated?  Unless the zoneinfo in
glibc is changing, I wouldn't expect it to matter (we do merging of the
timeconfig .po files into anaconda's po files)

Comment 2 Nakai 2002-08-21 08:14:32 UTC
America/Danmarkshavn
America/North_Dakota_Center
America/Rio_Branco
Antarctica/Vostok
Asia/Choibalsan
Asia/Chongqing
Asia/Macau
Asia/Makassar
Asia/Oral
Asia/Pontianak
Asia/Qyzylorda
Asia/Sakhalin

Comment 3 Jeremy Katz 2002-08-22 03:34:28 UTC
I've updated timeconfig CVS -- Trond, could you make sure this gets built close
to final release and I'll also make sure to pull in any changes for anaconda.

Comment 4 Trond Eivind Glomsrxd 2002-08-28 22:01:58 UTC
Has been built now - timeconfig-3.2.8-3


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