Spaces in file paths
in The Archive
Hi @ctietze and others!
So far I had always assumed that The Archive can't handle spaces in file paths, so I either tried to avoid naming my files/folders with spaces or replaced the spaces with %20
in links.
Now I discovered by coincidence that that isn't true (anymore): If the link is enclosed with syntax like <URL>
or 
spaces in the path can don't destroy the link.
Do you still think it's good practice to continue replacing spaces with %20
(which also still works) for the sake of compatibility with other software/operating systems or can I abandon the practice for the sake of simplicity and aesthetics?
Best,
Vinho
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Comments
It depends!
<file://...>
is a URL, so you should use RFC 3986 URI encoding, which means replacing space (and commas and umlauts etc) with%20
.
loads images and depends on what the Markdown-to-whatever processor can handle, i.e. how liberal it is.
becomes<img src="path/to/image.png" alt="alt title" title="Image title" />
. Play with CommonMark to see how it breaks with spaces, for example.It's tricky to give a recommendation apart from "try not to use spaces". I use
-
and_
in my media file names for that reason.The Archive strives to be a robust app for the user,
... so we may accept more than others
Author at Zettelkasten.de • https://christiantietze.de/
@ctietze Okay, will continue using
Thanks for your reply!
%20
then