Currently, when PulseAudio is running on a remote machine, or with different envvars, the name of inputs, outputs, devices, etc. will be translated by the daemon and passed on translated to the UIs. It would be nicer if the translations were handled in the PA library, so that running: LC_ALL=fr_FR.UTF-8 gnome-control-center sound would show all the translatable strings in the requested language, rather than a mish-mash of strings translated in 2 different languages. Original request: https://bugzilla.gnome.org/show_bug.cgi?id=682866
So the server should send untranslated strings with %s etc. placeholders and the associated parameters (and the parameters themselves may be translatable strings with further parameters), and the client should then match the string and its parameters with some translation database. That doesn't sound doable to me.
Whatever translations you're doing in the daemon could just as well be done in the PA library. It's probably not that easy to do, as the "translate in place" is so ingrained into PA. Think of an embedded PA, why should you restart the appliance on which it's running to get a new language in the client?
(In reply to comment #2) > Whatever translations you're doing in the daemon could just as well be done > in the PA library. Easier said than done. > It's probably not that easy to do, as the "translate in > place" is so ingrained into PA. Yep. > Think of an embedded PA, why should you restart the appliance on which it's > running to get a new language in the client? No other reason than that it's hard to implement. I'm not going to start working on this, so patches welcome, if you manage to come up with a sane solution.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/386.
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.