Myles English <mylesengl...@gmail.com> writes: > e...@...net writes: > >>>> I've often thought it would be nice to link to images in an org file >>>> with http: links, then at some arbitrary point in time call a >>>> hypothetical org-localize-external-resources command. That command would >>>> wget all the external resources, put them somewhere local, and switch >>>> the links to the file: type. Just a thought. > > How about a derived export backend with a filter that does a wget and > rewrites the links? > > One problem could be what if a wget fails? As I am finding with my > implementation, some websites only allow browserlike access.
That's kind of why I think it would be better as a standalone interactive function, rather than an export preprocessing thingummy. You'd run it first, with timeouts and error messages, etc, and then export when you're done.
