glaterza commented on code in PR #44397: URL: https://github.com/apache/superset/pull/44397#discussion_r4214671028
########## scripts/translations/babel_update.sh: ########## @@ -40,11 +40,18 @@ cat <<'EOF'> "$LICENSE_TMP" EOF cd $ROOT_DIR +# --add-comments=i18n:: carry translator context from the source into the +# catalogs. A comment tagged `i18n:` immediately above a translatable string is +# extracted as a `#. i18n: ...` comment on that entry, and (like the +# do-not-translate marker below) propagates into every language catalog on the +# `pybabel update` further down. Only `i18n:`-tagged comments are extracted, so +# ordinary code comments near a string are not published to translators. pybabel extract \ -F superset/translations/babel.cfg \ -o superset/translations/messages.pot \ --no-location \ --sort-output \ + --add-comments=i18n: \ Review Comment: A correction to the live-run numbers in my reply above. A run on 2026-10-08 with the same default model did not reproduce them. - With five misleading references, `Backend` came back as `Драйвер` in 6 of 6 runs without the note, and in 5 of 6 with it. - With the references from the 29 other catalogs, it came back as `Бэкенд` in 6 of 6 runs, with or without the note. The note informs human translators, but it does not override unanimous references in the backfill prompt. `c9b30d6e4f` removes the howto's claim that it takes precedence. The PR description has the full table. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
