-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filenames with spaces don't render correctly on GitHub pages #73
Comments
It would not be too difficult to offer different "link encoding profiles" optimized for different markdown engines, with the current set being the default. If you let me know which characters should, and which should not, be encoded to play nice with Kramdown/Jekyll, I'd be happy to implement this. |
Also, was this on Jekyll/GitHub pages, or just GitHub's rendering of Markdown files when you browse a repository? |
the only thing i ran into was the %20 ... which, remarkably, I didn't see too much consternation about from users; my google skills may be lacking. |
specifically github pages ... i haven't tried standard github rendering of the results of an export |
filenames with spaces are converted to links with %20 in them, however kramdown/etc does not seem to properly recognize this and does not convert these links to proper html links, instead it keeps the .md extention, which fails to work (404) on github pages.
EDIT: I tested manually replacing the %20 with an actual space, and github's kramdown now renders it properly. (maybe this could be an option, as %20 "should" work (in my opinion) everywhere, github just has an issue maybe?)
The text was updated successfully, but these errors were encountered: