GitHub user rusackas added a comment to the discussion: Proposal: a translation guide, with shared principles and per-language conventions
In general, I appreciate this kind of thinking/effort SO much, and much of it sounds like the right move. My worry is that the glossaries won't be maintained, as we've already seen to be the case by the translations themselves... I worry it'll play second fiddle to an already-undermaintained feature. Anything that improves the _automation_ of translations (always in flux) would be amazing. I wonder if the .pot file can include some structured comments that get passed through to the .po files or at least be leveraged by the AI translation backfill script, so more of the strings are "contextualized" with context, and we avoid at least these term ambiguity problems you pointed out (I always talk about "turkey" being a bird, a country, and an insult, but yours are more practical). I.e. if there was a .pot "way" to add comments like: ``` #: src/foo.js:42 # context: "slug refers to the unique identifier in a URL" msgid "slug" msgstr "XXXXXX" ``` Then that might provide enough context for AI (or humans) to know what to drop there. As for policies, I agree, standards are needed. I'd be supportive of a docs site entry covering these. Things like tu/usted framing in spanish, or how we standardize on gendered languages (presumably preferring gender-neutral). Until there is a rule, nobody's breaking the rule. GitHub link: https://github.com/apache/superset/discussions/43562#discussioncomment-18168464 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
