And the <$img > command need the binder name of the picture.
By example, if i drop an image named FLOWER in a Binder folder, the image will be stock inside the Project file but rename with a number.
If the image is dropped on inspector, then another file is created with the number of the related document followed by “icImage”.
So I conclude that only Scrivener creators can add a command to allow us to place the inspector image on the related file.
I hope they will read this, until then i will drop the image manually on the inspector and after on the file.
Can’t quite see why it wouldn’t work, given your description. If you drop the image in the inspector, it is given a special project-internal filename, but that shouldn’t be a barrier, you just use that filename in the img tag in the doc. Of the path/filename is right Scriv should fetch the right image at compile time. Do you have any thoughts on why that is not working?
gr
P.s. By the way, how is it that your binder file names match the project-internal filenames scriv uses? That is highly unusual (and I don’t know how you would keep up with it). Have you made this happen by manually renaming the items in the Binder or something?