| Summary: | Messages.sh is missing for pavucontrol | ||
|---|---|---|---|
| Product: | PulseAudio | Reporter: | jtux <juliette.tux> |
| Component: | pavucontrol | Assignee: | pulseaudio-bugs |
| Status: | RESOLVED FIXED | QA Contact: | pulseaudio-bugs |
| Severity: | normal | ||
| Priority: | medium | CC: | lennart |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
jtux
2013-09-18 17:11:47 UTC
Sorry for taking so long to respond. I have never heard of Messages.sh. Can you explain briefly what it is, and preferably also explain how I could create a "fresh" Messages.sh? Hello, generally speaking, this is the script which tells xgettext what sources have to be translated, where to find the strings marked for translations. In KDE and many other projects it is called Messages.sh, see for example http://techbase.kde.org/Development/Tutorials/Localization/i18n_Build_Systems#Writing_a_Messages.sh_script . Lots of projets make such a script publicly available in the source code tree to facilitate the generation of .pot from updated code, which is very useful for translators (no need to bother the developers every time the code is updated, saves a lot of time etc) Generally speaking what I meant is that the pot-generating script is missing for pavucontrol, whatever you like to call it. Or I was unable to find it. Does this do what you'd expect a Messages.sh script to do?
cd po
make pavucontrol.pot
Oh, well, yes it does :) although using the standalone script does not require making lots of additional steps and installing additional packages. Ok, thanks a lot for replying and the issue is resolved for now. It would be nice to know if pavucontrol is meeting the usual expectations of translators. I'm personally pretty clueless about how translators do their work. Apparently the process is not obvious at least for translators who are used to a KDE workflow. I wonder if translators who are used to Autotools based projects find the process more familiar, or is it unobvious for everyone. (In reply to comment #5) > Apparently the process is not obvious at least for translators who are > used to a KDE workflow. Quite right. > I wonder if translators who are used to Autotools > based projects find the process more familiar, or is it unobvious for > everyone. Clear and explicit TRANSLATORS_README.txt somewhere in /po would help a lot really :) I sent a patch to the mailing list: http://thread.gmane.org/gmane.comp.audio.pulseaudio.general/19910 Thanks a lot for the attention payed to the localizators issues! Very kind, indeed. |
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.