admin/Azure-co-op-translator
1
0
Fork 0
mirror of https://github.com/Azure/co-op-translator synced 2026-08-09 12:00:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarify translation management in README

Browse Source 
Enhanced clarity and consistency in the README regarding how Co-op Translator manages translations and metadata.
This commit is contained in:
Minseok Song
2026-02-04 17:43:06 +09:00
committed by GitHub
parent 2f6c3f06fc
commit c359329880
1 changed files with 12 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+12 -9
View File
@@ -52,21 +52,24 @@ Example of how translated content is organized:
## How translation state is managed
Co-op Translator manages translated content as versioned artifacts,
not static files.
Co-op Translator manages translated content as **versioned software artifacts**,
not as static files.
Co-op Translator tracks the freshness of translated Markdown,
images, and notebooks using language-scoped state metadata.
The tool tracks the state of translated Markdown, images, and notebooks
using **language-scoped metadata**.
This design allows the tool to:
This design allows Co-op Translator to:
- Reliably detect outdated translations
- Treat Markdown, images, and notebooks consistently
- Avoid fragile inline markers inside content
- Scale safely across large, multi-language repositories
- Scale safely across large, fast-moving, multi-language repositories
By modeling translations as managed artifacts,
translation workflows align naturally with modern
software dependency and artifact management practices.
→ [How translation state is managed](https://techcommunity.microsoft.com/blog/azuredevcommunityblog/rethinking-documentation-translation-treating-translations-as-versioned-software/4491755)
This approach aligns translation workflows with modern software
dependency and artifact management practices.
## Quick start