Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
What and Why
I want to add big versions of images to a blog post that exceed the default max width of 560 which is not enforced but suggested by the CSS layout.
This is a common pattern: when a big image is embedded in an article, show a thumbnail version or the maximum possible size in the blog post and offer the big version as a link. This way, the reader is able to decide whether or not he/she wants to open the link (as a new tab).
Without this feature, I am limited to the maximum size according to the CSS and/or I can't see all the details in the resized image. When I ignore the maximum size according to the CSS, I end up with a broken layout where the image is exceeding the column and potentially causes various CSS side-effects.
Following questions are to clarify for the concept:
And yes: lazyblorg really scales the images to their desired width/height so that you don't rely on browser scaling and minimize transferred data amount.
Therefore, I need something that might (or might not?) differ from the standard Org mode syntax to be able to define the desire to link the original image behind the embedded image.
The most Org-like way of enabling this feature would probably be inventing a new property that Org mode (hopefully) ignores:
Please note that
To be honest, I don't even know if there are boolean parameters that do not require a value, thus, omitting the "true" part of my example above.
The neat link-in-link approach will not do it for my requirements since it still doesn't allow me to define a different resolution for the linked image such as width=1000px. :-(
https://orgmode.org/worg/org-tutorials/images-and-xhtml-export.html and https://www.w3schools.com/tags/tag_img.asp do not list a potential useful candidate within the official Org mode or HTML attributes for images.
Currently, I am thinking of:
In any case, the image gets processed and EXIF data removed in order to get rid of meta-data such as GPS coordinates. This is a privacy-maintaining feature.
read more about it on https://karl-voit.at/2019/10/16/lazyblorg-linked-image-width/
Implemented the feature. Explained it on https://karl-voit.at/2019/10/16/lazyblorg-linked-image-width/