Replies: 4 comments 4 replies
This comment was marked as off-topic.
This comment was marked as off-topic.
-
Tweaks to the English mess up translationsWith default crowdin settings, we get this scenario:
We think we can solve this by doing two things:
The idea is, once a file is full translated and approved, we have that version in the repo so that we can keep publishing it while we wait for someone to go to Crowdin to either do cleanup or make actual new translations (in case there really is new material). A significant con of this approach is that absolutely every last thing must be translated and approved, including image links that Crowdin would normally hide from that translator. Has anyone else faced this problem? How did you solve it? |
Beta Was this translation helpful? Give feedback.
-
|
I am a happy docusaurus user, (currently on v2.4.3 and soon-to-be on v3). Our documentation website is written in French, then translated in English and German with a Crowdin+DEEPL combo.
So, unless the MT engine is markdown-aware (and deepl is not), this behaviour breaks docusaurus websites. Is there something I am missing? For instance: this string "[page d'accueil](/ma-page(d'accueil)" is translated "home", and this breaks docusaurus i18n workflow as the page name should not be translated. I can't be the only one using crowdin with MT: how do you deal with this? |
Beta Was this translation helpful? Give feedback.
-
|
FYI it's possible to force a specific Crowdin parser version, as I explain here:
For example, if you want to use a specific MDX parser version: - source: /website/docs/**/*.mdx
translation: /website/i18n/%two_letters_code%/docusaurus-plugin-content-docs/current/**/%original_file_name%
type: mdx_v2_4The parser version of your files can be retrieved by inspecting the "file type icon" with browser devtools on the Crowdin UI. Not convenient UX, but it works:
As of today, we have migrated the Docusaurus website to use the latest # Crowdin regularly update their MDX parser, leading to subtle breakage.
# Freezing the parser to a specific version is helpful to ensure things keep
# working when they upgrade their MDX parser.
# See https://github.com/facebook/docusaurus/pull/11432
#
# Note: you can find the parser version of a Crowdin file using browser DevTools
# and inspecting the MDX file icon, it should have a class ".file_type_mdx_v1_2"
# Find the latest version: manually upload a new .mdx file, then inspect it
#
# How to upgrade the parser version?
# - Rename /docs to /docs_backup on Crowdin UI (same for other mdx folders)
# - Update the parser version of this config file
# - Use the CLI to re-upload the MDX source files: they should now have the new parser version
# - Use the CLI to download the translations
# - Build the full i18n site to ensure it still works (the new parser might break things)
# - Make sure the site content remains translated (normally /docs & /docs_backup share the translation strings)
# - If things work well, you can merge the config update and delete the mdx backup folders on Crowdin UI
mdx_file_type: &mdx_file_type mdx_v2_4
#
# Files configuration
#
files:
- source: /website/i18n/en/**/*
translation: /website/i18n/%two_letters_code%/**/%original_file_name%
languages_mapping: *languages_mapping
- source: /website/docs/**/*.mdx
translation: /website/i18n/%two_letters_code%/docusaurus-plugin-content-docs/current/**/%original_file_name%
languages_mapping: *languages_mapping
type: *mdx_file_type
- source: /website/docs/**/*
translation: /website/i18n/%two_letters_code%/docusaurus-plugin-content-docs/current/**/%original_file_name%
languages_mapping: *languages_mapping
ignore: [/**/*.mdx]
- source: /website/versioned_docs/**/*.mdx
translation: /website/i18n/%two_letters_code%/docusaurus-plugin-content-docs/**/%original_file_name%
languages_mapping: *languages_mapping
type: *mdx_file_type
- source: /website/versioned_docs/**/*
translation: /website/i18n/%two_letters_code%/docusaurus-plugin-content-docs/**/%original_file_name%
languages_mapping: *languages_mapping
ignore: [/**/*.mdx]
- source: /website/community/**/*
translation: /website/i18n/%two_letters_code%/docusaurus-plugin-content-docs-community/current/**/%original_file_name%
languages_mapping: *languages_mapping
- source: /website/blog/**/*
translation: /website/i18n/%two_letters_code%/docusaurus-plugin-content-blog/**/%original_file_name%
languages_mapping: *languages_mapping
- source: /website/src/pages/**/*
translation: /website/i18n/%two_letters_code%/docusaurus-plugin-content-pages/**/%original_file_name%
ignore: [/**/*.js, /**/*.jsx, /**/*.ts, /**/*.tsx, /**/*.css]
languages_mapping: *languages_mappingThe parser version gets set the first time you upload a given file to Crowdin. After that, it stays the same. To upgrade the parser version (or transition type from md to mdx), what worked for us is to rename If your Crowdin site "shares duplicate strings" (configurable), normally, most of your translations will be preserved on your newly uploaded source files, and you'll later be able to delete the I can't guarantee this strategy will work for your site, so make sure to do various backups on Crowdin before running such a process (download a translation archive, translation memory, etc.) in case you lose translations. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Crowdin questions, issues, tips, feedbacks...
As the i18n support is now available in Docusaurus 2
Let's have this issue to discuss anything about Crowdin so that the community can help each other.
Discuss other SaaS translation softwares here
Disclaimer
Docusaurus 2 does not force you to use Crowdin, and you are free to use another SaaS if you want.
Crowdin is not a silver bullet but it gets the job done successfully for some websites like Jest and Docusaurus.
Like any SaaS software, it has its own release lifecycle, bugs, missing features, legacy, weird behaviors.
The Docusaurus team has absolutely 0 control over Crowdin apart from being in touch with their support team and suggesting possible improvements.
Beta Was this translation helpful? Give feedback.
All reactions