You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you wrote [Home](/home) inside mdx, it would automatically create a url to localhost:3000/en/home if you were on the English version, and localhost:3000/de/home, if you were on the German version.
In v3
We don't have the same i18n capability, but workaround it with optional middleware.
If you don't have this middleware, you would have to create [Home](/en/home) for the English mdx page and [Home](/de/home) for the German page.
When ideally, you'd only want to use the relative path without having to include the locale.
I'm sorry for leaving this hanging.
In my context I export the next app statically to github pages, so the middleware is not an option for me.
I remembered this issue, as I was writing on the documentation, used a link and it worked as expected. I will have to test it again more in depth, but I don't have the time for that right now. I'll try to do it this weekend.
Describe the bug
Links in a localized documentation require manual editing when translating.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to
happen.
I want that the language in a markdown link gets inferred by next, so that I don't have to keep this change in mind when translating.
The text was updated successfully, but these errors were encountered: