Hi Tobias
Anything to do with encodings is liable to be a little mindbending.
The key here is to look at the actual static files themselves, rather than the URLs that are used to access them. For example, the link to the static tiddler
http://tiddlywiki.com/static/Working%2520with%2520TiddlyWiki.html ends up at the following file:
Again, there’s the double, encoding, but if you visit the URL you’ll see the file path given as
jermolene.github.io/static/Working%20with%20TiddlyWiki.html.
What’s going in is that:
a) TiddlyWiki uses URI encoding to ensure that troublesome filename characters like the colon and slash are safely escaped
b) The browser uses a further level of URI encoding to encode unsafe URI characters like the percentage sign. This encoding affects the URI, not the underlying file path
As I say, it’s mindbending stuff.
Best wishes
Jeremy.