Status

Ready for review

Description of Changes

Our current i18n release management workflow gets everything right on the securedrop-i18n/i18n branch, but doesn't ensure that the PO template is updated back on the develop branch. This PR brings securedrop/translations/messages.pot up to date. A documentation update is pending to reduce the chance of this happening in the future.

Testing

Put this in a script called ckpo.py:

#!/usr/bin/env python3

import sys

from babel.messages.catalog import Catalog
from babel.messages.pofile import read_po

from sdconfig import config


catalogs = {}
pofiles = sorted(config.TRANSLATION_DIRS.glob("**/messages.po"))
for po in pofiles:
    catalog = read_po(open(str(po)))
    catalogs[str(catalog.locale)] = catalog

pot = config.TRANSLATION_DIRS / "messages.pot"
srccat = read_po(open(str(pot)))
for message in srccat:
    if "fuzzy" in message.flags:
        continue
    for locale, catalog in catalogs.items():
        translation = catalog.get(message.id)
        if translation is None:
            print("message not present in {}: {}".format(catalog.locale, message.id), file=sys.stderr)
        elif not translation.string:
            print("message not translated in {}: {}".format(catalog.locale, message.id), file=sys.stderr)

• git checkout develop
• In the root of your securedrop working copy, run PYTHONPATH=securedrop /path/to/ckpo.py
  The output should contain four WARNING lines which you can ignore, and quite a few "message not present" errors. Those are strings which no longer exist in our code.
• git checkout -b update-translation-messages origin/update-translation-messages
• Run ckpo.py again. This time there should only be the four ignorable WARNING lines, and 13 icon alt text strings that have not been translated to Hindi, which is accurate. If this matches what you see, the messages.pot file now matches the translatable strings in our source.

Deployment

This doesn't affect the production message catalogs.

Checklist

If you made non-trivial code changes:

• I have written a test plan and validated it for this PR

Choose one of the following:

• I have opened a PR in the docs repo for these changes, or will do so later
• I would appreciate help with the documentation
• These changes do not require documentation