Translation and sync automation #29949
Replies: 0 comments 16 replies
-
|
Thanks for this nice purpose about translations diff 🙏 Does we really need For more detail, when the |
Beta Was this translation helpful? Give feedback.
-
|
I think it's a really good idea!! ❤️ This idea is based on docs syntax and requires Magic translation comments. |
Beta Was this translation helpful? Give feedback.
-
|
I like the idea as well. It is a nice in-between a key-translation pair that we see with typical i18n-related solutions that work very well for smaller scopes of translation but become harder when you have to translate multiple paragraphs in one go. question/hypothesis:
|
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.
-
This is a raw idea and RFC discussion.
With an inlined translation format, we can automatically sync languages with
enwithout the need for manual maintenance and ensure we have a markdown-native flow while being possible to integrate with cloud-based systems and docus for augmented improvements like showing translate button for each section!Example
[content/ja/intro.md]
Magic translation comments
Before each title and before its contents, the automated script adds a magic comment which is basically a snapshot of the latest reference language (
en) and a tag that specifies its status. This helps both automation and maintainers to quickly read, compare and do translations.Translation tags
There are 3 possible status tags determined during sync process by comparing latest reference to new one.
[translateme]: Content is either new or could not match or by fuzzy search has difference above the threshold[attention]: Difference between last reference and next sync, has some difference but below the threshold to be replaced with en[translated]: Last and next sync reference was same. Therefore if status was translated, it is still translated without need of attentionSync algorithm
en) content from all sourcestranslateme,attentionortranslated)enif the status istranslatemeMarkdown meta
The current idea is to support an object with each language.
Beta Was this translation helpful? Give feedback.
All reactions