agama-project / agama / 21139095269 / 3 – web

73%

master: 73%

push

github

translate strings originating in Rust code (#2949)

## Problem

We do not have a mechanism to translate strings originating in the Rust
code yet

-
https://trello.com/c/DSk54XYG/5303-research-localized-strings-in-rust-code

## Solution

- Translation works for strings originating in Rust code
  (tested on a "Pattern summary" string that was added and reverted)
- Translation of format strings works, via
  https://lib.rs/crates/i18n-format
- Added the appropriate CI Weblate jobs for `../agama-weblate`:
  to put the POT file there and get the PO files from there.
- A new Weblate component to be souced from
`agama-weblate/rust/agama.pot`, :warning: TODO: set it up on
https://l10n.opensuse.org/
- Introduced `agama_l10n::helpers::gettext_noop`,
  marks a string for translation but does not translate it
- `QuestionSpec` instantiation simplified with a new `with_action_ids`
fn


## Testing

Tested manually: with `/testing_using_container.sh` which exposes Agama
at `localhost:10443`, on an artificially added string that is
prominently visible in the Software page.

## Screenshots

This screenshot shows a successful translation of a Czech string (added
in 2ecb16334 and later reverted, because
it is actually useless). The useful strings occur mostly in error cases
and are hard to trigger.


![agama-cs-pattern-summary2u](https://github.com/user-attachments/assets/b913ddd2-28bd-4777-8363-c856687d82cc)

## Documentation

- added `rust/po/README.md` and an identical copy,
`service/po/README.md`
- https://github.com/agama-project/agama-project.github.io/pull/137

2743 of 5099 branches covered (53.79%)

Branch coverage included in aggregate %.

12166 of 17340 relevant lines covered (70.16%)

49.11 hits per line