Reuben Thomas
Reuben Thomas
Fixed in my friendly fork: I have taken over the project at https://github.com/rrthomas/
This is in general not possible (how would recode know which bits are in which encoding?).
I have taken over the project at https://github.com/rrthomas/ and the bug is fixed in current git there; release shortly.
If I escape the URL on the command line (adding %20 and %27 in the relevant places), I still get the internal error, so I presume the problem is caused...
Thanks very much for the suggestion, which fixes things for me. I sympathise with this being a delicate issue to fix, so if you agree that at least it's not...
I just had a quick look into this. Forgive me if I'm telling you things you already know! RFC 3986 seems to be relevant here. There's a nice [summary](https://perishablepress.com/stop-using-unsafe-characters-in-urls/). `'`...
Thanks for the workaround. I don't quite understand *why* it works: I'm indeed not using `--check-extern`, so how come changing (indeed, enlarging) the set of URLs considered to be internal...
Thanks for the explanation!
I just realised that I hadn't actually tried your workaround on an unpatched version of linkchecker. It doesn't seem to work. I am using the following linkcheckerrc: ``` [filtering] internlinks=^https://boyde\.ithaky\.net/.*...
Thanks, I hadn't understood that adding the trailing slash was needed on top of the `internlinks` setting. However, running with that setting still gives me internal errors.