8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
English version of document (which is the default) behaves correct, but i18n (zh-hans) may show page-not-found in some cases.
Docusaurus i18n translate should be successful if expected.
Currently, there are two ways to achieve i18n translation (from en to zh-hans):
This unexpected behavior seems not happen on my local deployment (which uses npm run serve).
npm run serve
The text was updated successfully, but these errors were encountered:
Hrm, interesting. It seems that Docusaurus does something behind the scenes that I'm not sure to understand.
Watch this video
So, Docusaurus is doing something between 3 and 4. We should understand that and check what's happening in the server.
Sorry, something went wrong.
No branches or pull requests
Details
English version of document (which is the default) behaves correct, but i18n (zh-hans) may show page-not-found in some cases.
Expected Result
Docusaurus i18n translate should be successful if expected.
Actual Result
Currently, there are two ways to achieve i18n translation (from en to zh-hans):
This unexpected behavior seems not happen on my local deployment (which uses
npm run serve
).The text was updated successfully, but these errors were encountered: