I have seen other posts about changing the size of the images but this is not what I need. The document contains an enormous quantity of images and I don’t want to download all of them and insert them manually in the document. So, is it possible to change the size these images will be viewed in the document (output as PDF)?
So here are three methods which works to scale, and one which doesn’t.
This last one can also be written: !
In short, using either the double brackets or the combination of [ ]( ), it’s easy to scale the image. Your syntax, I don’t really know what is, but it seems like more of a placeholder (or strange variant of a footnote), and it doesn’t accept scaling options.
It also seems like instead of the ![ ] you could also write just !, but it still doesn’t allow for scaling, it seems. Where did you find that syntax for writing an embedded link?
PS! Your variant was the one which wasn’t working…
Thanks Holroy. So, this document comes from a webpage which I converted to markdown using a Devonthink extension that allows you to save web pages in different formats. The Markdown coding is not mine. The page is correctly viewed in Obsidian, though.
Actually, the problem is not solved. The list of URLs linking to the images is at the end of the document. As if they were notes or references. The numbers in ![ ], ![ ], etc. that you find in the document point to those URLs. If I do:
I think you need to look at your converter, and make it convert into something better handled by Obsidian. And given that you don’t want to download the images, I guess your best option is to get it to be of the format: ![|100](http://your.com/url)
OK. I will do that but wouldn’t this be an Obsidian problem?
I mean, this extension seems to create a markdown document that is perfectly rendered in Obsidian and in other markdown compatible applications. That would mean that this is well formed markdown. But if this is well formed markdown, shouldn’t Obsidian be capable of working with it?
So you are indeed (even if I didn’t now that beforehand) using valid commonmark code for your images, so you shouldn’t need to change due to that.
However, Obsidian has made extensions to allow for resizing images, and they’re based on parsing the alternate text options, and in the example above only the first (with cat.png) picks out the resizing text. For the dog, the text in either alt2 or title3 does survive into the DOM in reading mode, but it’s not handled as a resizing attribute. And that could be considered a bug, possibly.
So I’ll write a post in the Bug report section, and maybe it’ll get fixed sometime in the future.
Thanks holroy! I’m new to both markdown and Obsidian so I appreciate all the help I can get.
I have posted a question in the forum for the app that I use to translate the webpages into markdown. I’ll see what they answer. I’d like to continue working with Obsidian, though, so if this gets fixed, I’d be happy.
Thanks. No, that wouldn’t work because it really depends on the document. There are documents where the size of all the images should be reduced or increased whereas in other documents only some images should change in size.
Thanks, holroy. From the kinds of documents I’m converting so far, I can see the solution to set a given size for all images won’t work. In the meantime, someone pointed me to a reference that seemed to be relevant. I don’t really know whether it is actually relevant to solve my problem. Perhaps someone more well-versed than me in markdown could tell me if this could be put to use in the case at hand: