| Summary: | RFE: Please make messages translatable | ||
|---|---|---|---|
| Product: | systemd | Reporter: | Samuel Thibault <samuel.thibault> |
| Component: | general | Assignee: | systemd-bugs |
| Status: | NEW --- | QA Contact: | systemd-bugs |
| Severity: | normal | ||
| Priority: | medium | CC: | piotrdrag |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Samuel Thibault
2015-01-11 20:08:17 UTC
I was thinking about that too. Recently a bunch of new translations for systemd (as far as it is translatable) were added, so it seems that there's a healthy community of translators who would do the translations if the functionality were provided. We should use gettext. Systemd is a large project, and translating all messages that can be emitted is a huge amount of work for little gain. I'd pick a few areas that are the most important (useful to casual users), and concentrate on that. Anything that is below log_info would not be translated. In some rough order of priority: - stuff that systemd prints to the console - systemd-tty-ask-password-agent - systemctl, hostnamectl, timedatectl, journalctl, localectl For the tools the order does not really matter. I'd probably be good to start with the smaller ones. I'd be really careful with adding gettext support to PID 1 itself. I am fine with adding it to the client-side tools, but all that i18n complexity from PID 1 makes me feel very uncomfortable. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.