<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Please make messages translatable" href="https://bugs.freedesktop.org/show_bug.cgi?id=88300#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Please make messages translatable" href="https://bugs.freedesktop.org/show_bug.cgi?id=88300">bug 88300</a> from <a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> Zbigniew Jedrzejewski-Szmek</a> <pre>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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>