There's a couple of places which use varients on "0x%u" in format strings;
that's almost always wrong - you either want 0x%x or just %u. In libmount's
case it's flags, so I'm assuming the intention really is hex. In the ja.po
case it's %u in the original msgid.
Signed-off-by: Dr. David Alan Gilbert <dave@treblig.org>
if (!optstr || !map)
return -EINVAL;
- DBG(CXT, ul_debug("applying 0x%08lu flags to '%s'", flags, *optstr));
+ DBG(CXT, ul_debug("applying 0x%08lx flags to '%s'", flags, *optstr));
maps[0] = map;
next = *optstr;
#: libfdisk/src/sun.c:163
#, c-format
msgid "Detected sun disklabel with wrong vtoc.nparts [%u]."
-msgstr "間違った vtoc.nparts 値 [0x%u] の sun ディスクラベルを検出しました。"
+msgstr "間違った vtoc.nparts 値 [%u] の sun ディスクラベルを検出しました。"
#: libfdisk/src/sun.c:168
msgid "Warning: Wrong values need to be fixed up and will be corrected by w(rite)"