Skip to content
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

GET /%E8%AE%A1%E7%AE%97/HTTP/1.1" code 404 does not support Chinese name md documents #2463

Closed
quinntwohao opened this issue Jun 15, 2021 · 3 comments · Fixed by #2464
Closed

Comments

@quinntwohao
Copy link

quinntwohao commented Jun 15, 2021

Questions are as follows:
I have encountered a problem when using Chinese to set the navigation, click on the navigation bar to prompt the page to display: 404-Not found

The CLI error is as follows: "GET /%E8%AE%A1%E7%AE%97/ HTTP/1.1" code 404

The mkdocs.yml configuration file is as follows:

site_name: My Docs
site_url: https://example.com/
theme:
name: material
nav:
- 首页: index.md
- 测试1: 测试1.md
- 测试2: 测试2.md

I tried windows system, ubuntu system, mac system, and I can’t quote markdown documents with using Chinese to set the navigation but I see other people’s blogs support Chinese, but theirs is not the latest version, the author is in the latest version. Do you choose not to support Chinese markdown documents?

I checked the historical problem records, but did not find a clear instruction, if you know, please help me, thank you very much

@oprypin
Copy link
Member

oprypin commented Jun 15, 2021

Sorry, my recent change broke serving files with non-English letters. The problem is not only for Chinese. I have suggested a fix for the code.

@quinntwohao
Copy link
Author

Sorry, my recent change broke serving files with non-English letters. The problem is not only for Chinese. I have suggested a fix for the code.

Thank you, hope to solve this issues

@oprypin
Copy link
Member

oprypin commented Jul 18, 2021

The fix is now included in the latest release.

cc @144026 @earthman123

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants