Update message catalogs for next round of translations - #2639
Open
emilyanndavis wants to merge 7 commits into
Open
Update message catalogs for next round of translations#2639emilyanndavis wants to merge 7 commits into
emilyanndavis wants to merge 7 commits into
Conversation
…atalog. Fix typos in source of a few English-language messages.
…es, zh (.po) catalogs.
emilyanndavis
marked this pull request as draft
July 10, 2026 20:37
…st into feature/1951-translation-update-2026-july
…ng received translations.
…st into feature/1951-translation-update-2026-july
emilyanndavis
marked this pull request as ready for review
July 28, 2026 16:45
claire-simpson
requested changes
Jul 29, 2026
| spec.Option(key="square"), | ||
| spec.Option(key="hexagon") | ||
| spec.Option(key="square", display_name=gettext("square")), | ||
| spec.Option(key="hexagon", display_name=gettext("hexagon")) |
Contributor
There was a problem hiding this comment.
Should all display_names be wrapped in gettext? I see several models with Options that do not wrap the display_name, e.g., wave energy, HRA, UNA, CBC preprocessor. And other models where the options only have about text (not display_name) and that text isn't wrapped in gettext. Not sure how extensive this PR needs to be but wanted to mention it
| 8. If you are preparing translation files for multiple languages, repeat steps 2 through 7 for each remaining language. | ||
|
|
||
| ``` | ||
| 9. Delete remaining temp files: `tmp.json` (if you generated a new one by following step 8), `main-messages.json`, and `renderer-messages.json`. |
Contributor
There was a problem hiding this comment.
Suggested change
| 9. Delete remaining temp files: `tmp.json` (if you generated a new one by following step 8), `main-messages.json`, and `renderer-messages.json`. | |
| 9. Delete `main-messages.json` and `renderer-messages.json`. |
Since deleting tmp.json is already referenced in step 7
| pybabel update \ | ||
| --locale $LL \ | ||
| --input-file src/natcap/invest/internationalization/messages.pot \ | ||
| --output-file src/natcap/invest/internationalization/locales/$LL/LC_MESSAGES/messages.po |
Contributor
There was a problem hiding this comment.
Suggested change
| --output-file src/natcap/invest/internationalization/locales/$LL/LC_MESSAGES/messages.po | |
| --output-file src/natcap/invest/internationalization/locales/$LL/LC_MESSAGES/messages.po \ |
| Human-readable message catalog file. Messages are added to this file from the PO template, and translations for the messages are added by the translator. | ||
| Human-readable message catalog file. Messages are added to this file from the PO template (`.pot` file), and translations for the messages are added by the translator. | ||
|
|
||
| Messages in `.po` files may be annotated with flags (comma-separated strings immediately preceding a `msgid`). Some flags are defined by the translation tooling and built into its automated processes; others may be custom, with special meaning and processes defined by a particular project or dev team. |
Contributor
There was a problem hiding this comment.
Might be helpful to provide an example of this?
comma-separated strings immediately preceding a
msgid
| * Linux: "\~/.config/invest-workbench/logs/" | ||
| * Windows: `C:\Users\dmf\AppData\Roaming\invest-workbench\logs\` | ||
| * Mac: `\~/Library/Logs/invest-workbench/` | ||
| * Linux: `\~/.config/invest-workbench/logs/` |
Contributor
There was a problem hiding this comment.
Suggested change
| * Linux: `\~/.config/invest-workbench/logs/` | |
| * Linux: `~/.config/invest-workbench/logs/` |
| * Mac: "\~/Library/Logs/invest-workbench/" | ||
| * Linux: "\~/.config/invest-workbench/logs/" | ||
| * Windows: `C:\Users\dmf\AppData\Roaming\invest-workbench\logs\` | ||
| * Mac: `\~/Library/Logs/invest-workbench/` |
Contributor
There was a problem hiding this comment.
Suggested change
| * Mac: `\~/Library/Logs/invest-workbench/` | |
| * Mac: `~/Library/Logs/invest-workbench/` |
| InVEST models, and to be extensible to future models or InVEST-relevant auxiliary workflows. | ||
|
|
||
| ## To develop and launch this app | ||
| 1. From ``invest/``: |
Contributor
There was a problem hiding this comment.
Suggested change
| 1. From ``invest/``: | |
| 1. From `invest/`: |
|
|
||
| ## Summary of files | ||
| None of the translations files (.pot, .po, .mo) should be manually edited by us. | ||
| None of the translation files (`.pot`, `.po`, `.mo`) should be manually edited by us. |
Contributor
There was a problem hiding this comment.
This is a bit confusing to me, because later on the doc says "change python-format to no-python-format" and remove the incorrect python-format tags in the .po files?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Update message catalogs in preparation for the next (upcoming) round of translations. Specifically:
Checklist
- [ ] Updated HISTORY.rst and link to any relevant issue (if these changes are user-facing)- [ ] Updated the user's guide (if needed)- [ ] Tested the Workbench UI (if relevant)