GitHub user glaterza added a comment to the discussion: Proposal: a translation guide, with shared principles and per-language conventions
Thanks @goldjee, good to hear from someone who has corrected the backfill output by hand. Part of this is in review in #[44397](https://github.com/apache/superset/pull/44397): a developer note next to a string in the source reaches every catalog, and `backfill_po.py` passes it to the model. That only clarifies one string at a time, though. A per-language glossary plugged into the backfill would cover what a single string can't show, and its format is still open. Since you've done those corrections: what went wrong most often? A few real examples would help pin down what the glossary needs to hold. GitHub link: https://github.com/apache/superset/discussions/43562#discussioncomment-18715396 ---- 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]
