Bug 2555 - locale data for de_DE is outdated
locale data for de_DE is outdated
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
6.0
All Linux
low Severity low
: ---
: ---
Assigned To: Cristian Gafton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-05 00:38 EDT by tim.landscheidt
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-07-28 21:05:34 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)

  None (edit)
Description tim.landscheidt 1999-05-05 00:38:27 EDT
/usr/share/i18n/locales/de_DE is pretty outdated - it still
has the old German date format ("DD.MM.YYYY"). GNU's
glibc-localedata-2.0.6.tar.gz seems to have it right since
at least 1997-12-28. Pristine sources? :-)

Easy solution: Edit de_DE and re-run localedef. But the
right way (TM) should of course be modifying the .src.rpm.
Comment 1 Cristian Gafton 1999-07-28 02:09:59 EDT
I am told by the glibc maintainers that there has not been any
official decision on this, so the format glibc uses is still the
active one.
Comment 2 tim.landscheidt 1999-07-28 20:52:59 EDT
In localedata/locales/de_DE (timestamped: 1997-03-05) from
<URI:ftp://ftp.gnu.org/gnu/glibc/glibc-localedata-2.0.6.tar.gz>
(timestamped: 1997-12-29), line #2200 says:

| d_fmt   "<%><Y><-><%><m><-><%><d>"

That seems to be an "official" decision by the glibc maintainers, and
it is also perfectly correct according to EN 28601 and DIN 5008 which
apply to the Federal Republic of Germany (cf.
<URI:http://www.cl.cam.ac.uk/~mgk25/iso-time.html>). I may be missing
some point.
Comment 3 Cristian Gafton 1999-07-28 21:05:59 EDT
Please report it to the glibc maintainers. this is not the kind of
change we can do unilaterally.

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