Bug 15025 - bogus characters for fetching files in Norwegian locale
bogus characters for fetching files in Norwegian locale
Product: Red Hat Linux
Classification: Retired
Component: wget (Show other bugs)
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Winston rc1
Depends On:
  Show dependency treegraph
Reported: 2000-08-01 14:22 EDT by Trond Eivind Glomsrxd
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:
Last Closed: 2001-01-30 19:19:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Trond Eivind Glomsrxd 2000-08-01 14:22:57 EDT
After fetching a file with http, I get this at the bottom:

14:13:54 (202.06 KB/s) - ?czslova.gz.2? lagret [6277304/6277304]

("lagret" means "saved"). The "?" around the file name should be "'"

To reproduce:

LANG=no_NO wget my_url_here
Comment 1 Bill Nottingham 2000-08-01 17:24:35 EDT
glibc thinks those quote characters aren't printable. Re-assigning there.
Comment 2 Bill Nottingham 2000-08-01 17:34:14 EDT
Whoops, never mind, wget is being stupid and running setlocale
for LC_MESSAGES, which leaves it with the old LC_CTYPE.

Will be fixed in next wget build.
Comment 3 Glen Foster 2000-08-04 10:57:36 EDT
This defect is considered MUST-FIX for Winston Release-Candidate #1
Comment 4 Trond Eivind Glomsrxd 2000-08-04 11:01:33 EDT
This was fixed right after Bill's message.
Comment 5 Trond Eivind Glomsrxd 2000-11-08 14:34:08 EST
But it showed up again in time for Red Hat Linux 7 :(
Comment 6 Bill Nottingham 2001-01-30 19:19:18 EST
The characters get lost in gettext somewhere; they're all
'?' by the time gettext returns.
Comment 7 Trond Eivind Glomsrxd 2001-01-30 19:41:03 EST
The error was in the locale files supplied with wget... for some weird reason,
Norwegian (and Danish) was marked as being iso-8859-2. Fixed in 1.6-2

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