If you've told jAlbum not to URL-encode the links, the links should not be encoded by the skin. That would be like the skin forcing the inclusion of widget code even if you've turned off widgets in the jAlbum settings, just because the skin designer thinks you should always include it.
Granted, one should always choose to have jAlbum URL-encode the links. Offhand, I can't think of a situation in which you would not want to do that. But the jAlbum setting should control what happens, not the skin.
If I set it the spaces problem disappears, but new problems with the cell spacing are displayed....
Those errors have nothing to do with the URL encoding. It's just that Base is still using HTML tables for layout, and using the old-style table attributes instead of CSS to style the tables. They still work, of course, but should be changed for HTML5 compliance. You could easily do it yourself.
I think jAlbum should as default set the 'URL-encode links'check-mark!
I believe that has changed. You can't set both - if you choose URL-encode links, the option to Generate web-safe file names is grayed out, implying that it's ineffective. And a quick test indicates that as long as URL-encode links is chosen, the status of the other checkbox makes no difference - it never generates web-safe file names.
I believe once you've chosen to URL-encode the links, the web-unsafe file names is not an issue anymore, that's why it's grayed out.
So whether an album made with a skin is html compliant or not depends on 'URL-encode the links' setting of the skin user!
That is weird, the skin should produce always html compliant code!
I think the 'URL-encode the links' should be removed and jAlbum should always URL-encode the links (see this thread).
I don't see the point why one would turn off URL-encode links, but anyway, why shouldn't we let jAlbum manage it centrally? In the case of more complex skins it's not a big thing adding the URL-encoding, that's true, but think of Minimal skin. Why the skin should take care of the folder links?
I've now changed the default for "URL encode links" from off to on. The reason why it has been set to off until now has been that some browsers (read IE) didn't allow local browsing when using URL encoded links. As we now have an embedded browser, I think we shouldn't regard that issue anymore. It's better to follow the URL encoding rules.