Red Hat Bugzilla – Bug 103415
Weird string in date printing
Last modified: 2007-11-30 17:10:31 EST
This shows up with a locale of cy_GB.UTF-8. If I run rpm -qi desktop-printing
(or anything else for that matter) it displays a date string of
Dydd Gwener 29 a viz Awst 2003 22:21:01 BST
The [a viz] is weird and nothing to do with Welsh at all and other things appear
In locale C I get
Build Date: Wed Jul 23 .... 2003\n
Install Date: Fri Aug 29 22:21:01 2003
In locale cy_GB.UTF-8 I get (rpm has not been localised yet)
Install Date: Dydd Gwener 29 a viz Awst 2003 22:21:01 BST
which is the wrong format, the build date has vanished. The signature date lower
down is present but mangled in the same way.
(other apps all appear to be sane but I can't see anything that makes rpm
Still seen in FC2
LC_ALL=cy_GB.UTF-8 rpm -qi desktop-printing
Name : desktop-printing Relocations: (not relocatable)
Version : 0.1.10 Vendor: Red Hat, Inc.
Release : 26 Build Date: Dydd Mercher 05 a viz Mai 2004 16:56:00 CEST
Install Date: Dydd Llun 10 a viz Mai 2004 11:25:55 CEST Build Host: perf87.perf.redhat.com
Group : Applications/File Source RPM: desktop-printing-0.1.10-26.src.rpm
a viz there comes from:
which is translated to ASCII:
d_t_fmt "Dydd %A %d a viz %B %Y %T %Z"
Ping Mr Cox. Works for me, too. Please close the bug if you concur.
# LC_ALL=cy_GB.UTF-8 rpm -qi glibc
Name : glibc Relocations: (not relocatable)
Version : 2.3.3 Vendor: Red Hat, Inc.
Release : 46 Build Date: Dydd Sadwrn 21
a viz Awst 2004 07:00:06 PDT
Install Date: Dydd Sul 22 a viz Awst 2004 23:44:33 PDT Build
One last time: do we have to remove the "a viz" from the locale
specification or is it a feature of the language you don't know yet?
There is neither a 'v' nor a 'z' in the language. Having dug around
it seems somehow a random bit of cornish has been pasted into the cy
file by someone wel before the cy translation project ever took off
and all will be happy.
Fixed in CVS.
An errata has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.