> Done, use link=somepage --[[Joey]]
It would be handy if the `class` and `id` tags were passed through to the surrounding `table` in the case of `caption` being present. Would this break anything? --[[neale]]
+
+> Seems unlikely to break *too* much. I can imagine css that styles the img
+> unexpectedly applying the table. --[[Joey]]
+
+[[!template id=gitbranch branch=kjs/img-sharpen author="[[Kalle Söderman|kjs]]"]]
+
+I have created a patch that allows the image to be sharpened when resampled.
+There is also an additional option to interlace the image using plane for
+progressive display. --[[kjs]]
+
+---
+
+Is it possible to give an external image URL, must the image be local? One use case would be displaying *badges*, like [[the number of stars|https://img.shields.io/github/stars/joeyh/ikiwiki.svg]] of a [[github project|http://github.com/joeyh/ikiwiki]], but ``\[[!img https://img.shields.io/github/stars/joeyh/ikiwiki.svg]]`` does not work: [[!img https://img.shields.io/github/stars/joeyh/ikiwiki.svg]]. --[[Louis|spalax]]
+
+> Eventually wrote my own plugin: [[plugins/contrib/rimg]]. --[[Louis|spalax]]
+
+>> All the markup formats supported by ikiwiki can do raw HTML (possibly
+>> filtered), so you can use `<img>` for basic remote images; or you can
+>> use your chosen markup format's image syntax, like
+>> !\[some stars](https://img.shields.io/github/stars/joeyh/ikiwiki.svg)
+>> for Markdown. I don't think ikiwiki directives should duplicate markup
+>> formats' features unless it makes a significant difference to functionality
+>> or usability. --[[smcv]]
+
+>>> I totally agree. I never think about using HTML in my markdown documents,
+>>> and I did not know the `!\[Alt text](image url)`. Anyway, this plugin took
+>>> me less than one hour to write and publish; I will delete it soon.
+>>>
+>>> Anyway, thanks for your answer. --[[Louis|spalax]]