Discussion:
[Bug-wget] [bug #53884] Can wget (and any GNU projects) avoid spitting non-ASCII on the command line???
anonymous
2018-05-12 08:52:56 UTC
Permalink
URL:
<http://savannah.gnu.org/bugs/?53884>

Summary: Can wget (and any GNU projects) avoid spitting
non-ASCII on the command line???
Project: GNU Wget
Submitted by: None
Submitted on: Sat 12 May 2018 08:52:55 AM UTC
Category: User Interface
Severity: 3 - Normal
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Name: bliako
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: None
Operating System: GNU/Linux
Reproducibility: Every Time
Fixed Release: None
Planned Release: None
Regression: None
Work Required: None
Patch Included: None

_______________________________________________________

Details:

The problem is when I am using wget (many thanks for providing this excellent
and free software) from the console of my Fedora/Linux machine (console, no
X-server running) it prints various messages which contain non-ASCII
characters, for example the saved filename is enclosed in some form of
quotations. Apart from the horrible aesthetics of such decision, copying and
pasting what is inside the quotation marks (via mouse double-click) is a mess
because the marks are included in the text and when pasting to the console or
to a file, the non-ASCII characters are copied too, thus polluting my files
and making running a command via pasting fail.

In my opinion, a program using non-ASCII characters in its reporting is a
decision not to be taken lightly. There is no point to enclose a filename in
inverted commas rather than the traditional double quote. In my own aesthetics
book, this is a faux-pas but usually programmers get rid of it after
graduating primary school, circa 10 years old.

At least make printing non-ASCII characters optional via a switch.

Best wishes,

bliako.




_______________________________________________________

Reply to this item at:

<http://savannah.gnu.org/bugs/?53884>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
Dale Worley
2018-05-14 03:00:06 UTC
Permalink
Follow-up Comment #1, bug #53884 (project wget):

I've noticed this before but never really thought about it. However, it seems
likely that this behavior might be modulated by the LANG* environment
variables.

I checked in an Emacs shell window, and wget did use non-ASCII quote
characters. But also,
$ printenv | grep LANG
LANG=en_US.UTF-8
GDM_LANG=en_US.UTF-8
$

If I do
$ LANG=en_US wget google.com
wget limits itself to ASCII quotes.

So it seems likely that the LANG variable is specified to tell what character
set the program may use, and the relevant libraries respect that.


_______________________________________________________

Reply to this item at:

<http://savannah.gnu.org/bugs/?53884>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
Darshit Shah
2018-11-12 22:10:32 UTC
Permalink
Update of bug #53884 (project wget):

Status: None => Invalid
Open/Closed: Open => Closed


_______________________________________________________

Reply to this item at:

<https://savannah.gnu.org/bugs/?53884>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Loading...