Hello,
I've just updated pl.po file for xfsprogs 3.1.6.
It's available at http://qboosh.pl/pl.po/xfsprogs-3.1.6.pl.po
I also found some mistakes in messages used as msgid strings;
they are marked with "# XXX msgid bug:" in the above file.
There are two places with "n" instead of "\n" at the end of file:
#: .././repair/dinode.c:1442
#, c-format
msgid ""
"mismatch between format (%d) and size (%<PRId64>) in symlink inode %<PRIu64>n"
#: .././libxfs/freebsd.c:129
#, c-format
msgid "%s: Not a device or file: \"%s\"n"
one <PRIu64> without leading '%':
#: .././repair/phase6.c:2074
#, c-format
msgid "entry \"%s\" in directory inode %<PRIu64> points to free inode <PRIu64>"
one extra "u" after <PRIu64>:
#: .././repair/dir2.c:1177
#, c-format
msgid "corrected entry count in directory %<PRIu64>u, was %d, now %d\n"
and a few "0x" prefixes to %<PRIu64> (these values used to be printed
with %llx, so either <PRIu64> should be changed to <PRIx64>, or "0x" prefix
removed (I think the second version is better, as the value referred is
inode number, which in all other cases is printed decimal).
#: .././repair/scan.c:292
#, c-format
msgid "inode 0x%<PRIu64>bmap block 0x%<PRIu64> claimed, state is %d\n"
#: .././repair/scan.c:299
#, c-format
msgid "inode 0x%<PRIu64> bmap block 0x%<PRIu64> claimed, state is %d\n"
#: .././repair/scan.c:314
#, c-format
msgid "bad state %d, inode 0x%<PRIu64> bmap block 0x%<PRIu64>\n"
#: .././repair/scan.c:341 .././repair/scan.c:391
#, c-format
msgid "inode 0x%<PRIu64> bad # of bmap records (%u, min - %u, max - %u)\n"
--
Jakub Bogusz http://qboosh.pl/
|