[pacman-dev] HELP! - plurals in translation files
It looks like "make update-po" is not adding the plural translations to the po files. e.g. Looking at the removed strings that are stored at the bottom of theses files I see: src/pacman/po/en_GB.po: #~ msgid "%s: %jd total file, " #~ msgid_plural "%s: %jd total files, " #~ msgstr[0] "%s: %jd total file, " #~ msgstr[1] "%s: %jd total files, " #~ msgid "%jd missing file\n" #~ msgid_plural "%jd missing files\n" #~ msgstr[0] "%jd missing file\n" #~ msgstr[1] "%jd missing files\n" Those strings are still needed (all the rest are genuinely removed). Does anyone have any idea why these are not being added to the translation files? Allan
On 15/03/13 21:27, Allan McRae wrote:
It looks like "make update-po" is not adding the plural translations to the po files. e.g. Looking at the removed strings that are stored at the bottom of theses files I see:
src/pacman/po/en_GB.po:
#~ msgid "%s: %jd total file, " #~ msgid_plural "%s: %jd total files, " #~ msgstr[0] "%s: %jd total file, " #~ msgstr[1] "%s: %jd total files, "
#~ msgid "%jd missing file\n" #~ msgid_plural "%jd missing files\n" #~ msgstr[0] "%jd missing file\n" #~ msgstr[1] "%jd missing files\n"
Those strings are still needed (all the rest are genuinely removed). Does anyone have any idea why these are not being added to the translation files?
Well... poop... I have figured this out. Better now I suppose. The POTFILES.in files were not updated, so a few files are not flagged for translation. Sigh - fixing. Allan
We are almost done with the .de version, but there are at least two show-stoppers - I simply cannot figure out what it means. "%s optionally requires %s\n" I assume that we are talking about packages, but even if I should be wrong, I do not really see how something optional can be required. And in libalpm we find: "could not stat file %s: %s\n" Maybe this is very transparent to programmers, but to me, it is not. Are we talking about statistics, about static links, or anything I don't even ever heard about? Devs could be a little more verbose, at times. Any comment will be appreciated.
On Fri, Mar 15, 2013 at 04:28:09PM +0100, Matthias Gorissen wrote:
We are almost done with the .de version, but there are at least two show-stoppers - I simply cannot figure out what it means.
"%s optionally requires %s\n" I assume that we are talking about packages, but even if I should be wrong, I do not really see how something optional can be required.
Things that aren't needed for the core functionality, but can optionally be installed for extra functionality. An example, systemd previously required two python2 packages optionally, because systemd and everything would work fine, except one command, which was not part of the core of systemd. This made those two optional dependencies.
And in libalpm we find: "could not stat file %s: %s\n" Maybe this is very transparent to programmers, but to me, it is not. Are we talking about statistics, about static links, or anything I don't even ever heard about?
`could not stat` is Linux slang for `could not find`, since the `stat` command is used to get status information on a file. "Kann %s nicht stat: %s\n" pardon my very beginner German, it's been too long since I've used it.
Devs could be a little more verbose, at times. Any comment will be appreciated.
Thanks, -- William Giokas | KaiSforza GnuPG Key: 0x73CD09CF Fingerprint: F73F 50EF BBE2 9846 8306 E6B8 6902 06D8 73CD 09CF
Am 15.03.2013 16:42, schrieb William Giokas:
On Fri, Mar 15, 2013 at 04:28:09PM +0100, Matthias Gorissen wrote:
We are almost done with the .de version, but there are at least two show-stoppers - I simply cannot figure out what it means.
"%s optionally requires %s\n" I assume that we are talking about packages, but even if I should be wrong, I do not really see how something optional can be required.
Things that aren't needed for the core functionality, but can optionally be installed for extra functionality. An example, systemd previously required two python2 packages optionally, because systemd and everything would work fine, except one command, which was not part of the core of systemd. This made those two optional dependencies.
And in libalpm we find: "could not stat file %s: %s\n" Maybe this is very transparent to programmers, but to me, it is not. Are we talking about statistics, about static links, or anything I don't even ever heard about?
`could not stat` is Linux slang for `could not find`, since the `stat` command is used to get status information on a file.
"Kann %s nicht stat: %s\n"
pardon my very beginner German, it's been too long since I've used it.
Devs could be a little more verbose, at times. Any comment will be appreciated.
Thanks,
many thanks for your hint at "status information". I was completly on the wrong track. libalpm.de is up to 100%, and we'll clean up the rest over WE.
participants (3)
-
Allan McRae
-
Matthias Gorissen
-
William Giokas