Sharing between The Archive and Obsidian
I've followed the directions of another poster and shared my Archive Notes as an Obsidian Vault, letting me have the best of both worlds.
The one problem I've found is that Obsidian won't open the graphics (.png, etc) that The Archive has saved in its "media" folder. Both programs use the same Markdown commands to include graphics, so it seems to me that they ought to work "out of the box".
Can anyone suggest how I might solve the problem?
Howdy, Stranger!
Comments
Found the solution. While The Archive will accept spaces in the file names of inserted graphics, Obsidian will not. Obsidian requires either that spaces be replaced with the HTML "%20" space symbol or that the entire file name be enclosed between "<...>" brackets. Of course neither solution will work within The Archive.
So, can The Archive be configured to accept either the "%20" symbol or "<...>" brackets? I believe the "<...>" usage is standard Markdown, so that would seem the best way to go.
Finally, I'm new to both Markdown and The Archive, so I apologize if this is well-known to those who know it well.
Thank you.
%20
in place of spaces should work just fine in The ArchiveAuthor at Zettelkasten.de • https://christiantietze.de/
I've also noticed that Obsidian seams to search the image not only in the vault folder but also at least[1] in the default image folder, The Archive does not.
For example: if the image is in the subfolder "media", Obsidian will display an image indicated as
![](imagename.jpg)
but The Archive will require![](media/imagename.jpg)
[1]: I've not checked if it works also with other subfolders or subsubfolders so I'm not sure of the logic followed
Thank you to both ctietze and APG. I've tried using the
%20
symbol but without success. I expect that it may be a case of CUE (Catastrophic User Error).May I submit a possible change request? Would it be possible to allow the
<file name with spaces>
syntax mentioned in https://www.markdownguide.org/basic-syntax/ under the URLs and Email Addresses heading? (It's the syntax I used in the URL above.)Finally, although I'm new to both Zettelkasten and
The Archive
, they've already helped me become more productive. Thank you.The Archive supports that already, but not inside inline or reference-style link declarations. 🤔 It's not violating any other specs I know, so I'll add this to the list of Markdown things to investigate when I come around to doing that!
Author at Zettelkasten.de • https://christiantietze.de/
Thanks!