My guess (I only provide online docs) is that it would have to be same as HTML -> PDF conversion, ie download the image at PDF creation time and embed in PDF. But perhaps authors who support docs in PDF format would just never want to use such an option.
On Sep 1, 5:00 pm, Guenter Milde <[email protected]> wrote: > On 2010-09-01, Schollii wrote: > > That makes sense, but in some cases you expect the docs to be used > > online (as with doxygen docs) and WANT to refer to some images on > > other site (like updated stats from sourceforge) and want latest, not > > downloaded version. In this case a broken image box (what browsers put > > when they can't get an image) with alt text would be quite ok if image > > not accessible. > > So how about the following: > > * add an option to "image" role: ":remote:" > > * this flags the image as being remote, so no warning (except if the > > image path is a local file!) > > * when this flag is set, the ":alt:" should be set, otherwise warning > > Alternately, create a new role: remote-image with > > * same semantics as image but file is URL > > * and no warning about remote URI > > * but have warning (or better, error) if URL is local! > > How would you handle remote images with PDF and printed output? > > Günter -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
