-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
[v2] Couldn't link to static assets with Chinese characters under sub-dir #3471
Comments
no answer so closing |
Sorry, on vacation... Please check https://github.com/niheaven/docusaurus-debug, and output on my machine likes:
|
Thanks, let's reopen. The repro looks valid to me and I don't have windows to test the repro, unfortunately, but people have reported that using other shells (like PowerShell) could solve problem. Can you try some other Windows shell if possible? |
What I use is PowerShell 7, and I also tried PowerShell 5.1, CMD and nu shell. Unfortunately, the same error...
It seems like parsing engine treat Double or quadruple backslash can't work, too... |
The same error. Failed to compile
|
Should be fixed by #4736 Please let me know if you still have an issue |
🐛 Bug Report
When linking to static assets (pdf or xlsx, etc.) directly from markdown files, and if the file is under some co-locate subdir and has Chinese characters in its path name (filename or dirname), then the parsing engine will give some error as following:
Have you read the Contributing Guidelines on issues?
YES
To Reproduce
测试/test.pdf
,test/测试.pdf
,0202/测试.pdf
doc2.md
, using markdown's syntax (Link to [subdir with Chinese path name 1](test/测试.pdf)
) (Webpack's works well<a ... require('./0202/测试.pdf').default ... /a>
)doc2.md
Expected behavior
No error, move these files to
assests
and create clickable linksActual Behavior
Oh, line breaks got wrong, too...
Your Environment
Reproducible Demo
(Paste the link to an example repo, including a
siteConfig.js
, and exact instructions to reproduce the issue.)Just add some Chinese named files and dirs...
The text was updated successfully, but these errors were encountered: