From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] wget - This version does not have support for IRIs
Date: Sun, 10 Jan 2021 22:23:03 +0100 [thread overview]
Message-ID: <20210110212303.xWAWhVI66tMFJq-q_RTM6nZ6NeVV0IcsgVLYQfFoBtg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27813@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
Closed issue by jirib on void-packages repository
https://github.com/void-linux/void-packages/issues/27813
Description:
Hi,
I used `wget` to do mirror of a web and owner created probably some filenames with windows-1252 encoding, this caused problem and it seems way to go is to use "IRI" support in wget for convertion.
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
```
Void 5.9.14_1 x86_64 GenuineIntel notuptodate rrrdFFF
```
* package:
```
wget-1.21_1
```
### Expected behavior
IIUC IRI support is must if handling issues with filenames encoding. `+ivi` should be part ov `wget -V`.
### Actual behavior
```
$ wget -V | head -4
GNU Wget 1.21 built on linux-gnu.
-cares +digest -gpgme +https +ipv6 -iri +large-file -metalink +nls
+ntlm +opie -psl +ssl/openssl
$ wget --local-encoding=utf-8 --restrict-file-names=nocontrol https://www.google.com
This version does not have support for IRIs
```
### Steps to reproduce the behavior
```
$ wget --local-encoding=utf-8 --restrict-file-names=nocontrol https://www.google.com
This version does not have support for IRIs
$ wget -V | head -4 # should be with +iri
```
prev parent reply other threads:[~2021-01-10 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 20:41 [ISSUE] " jirib
2021-01-10 21:11 ` ericonr
2021-01-10 21:23 ` ericonr [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210110212303.xWAWhVI66tMFJq-q_RTM6nZ6NeVV0IcsgVLYQfFoBtg@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).