2e246b6fec
When running make dist, I hit this error: rm -f en@arabic.gmo && /usr/bin/gmsgfmt -c --statistics --verbose -o en@arabic.gmo en@arabic.po en@arabic.po:5312: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: The character that terminates the directive number 3 is not a valid conversion specifier. /usr/bin/gmsgfmt: found 1 fatal error This was caused by "%m" being replaced with foreign Unicode characters. For example: msgid "cannot rename the file %s to %s: %m" msgstr "ﺹﺎﻨﻧﻮﺗ ﺮﻌﻧﺎﻤﻋ ﺖﻬﻋ ﻒִﻴﻠﻋ %s ﺕﻭ %s: %ﻡ" Mimic the workaround used for "%s" by reversing the replacement of "%m" at the end of the sed programs. Signed-off-by: Mike Gilbert <floppym@gentoo.org> Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com> |
||
---|---|---|
.. | ||
gettext-patches | ||
arabic.sed | ||
boldquot.sed | ||
cyrillic.sed | ||
en@boldquot.header | ||
en@piglatin.header | ||
en@quot.header | ||
exclude.pot | ||
greek.sed | ||
grub.d.sed | ||
hebrew.sed | ||
insert-header.sin | ||
piglatin.sed | ||
quot.sed | ||
README | ||
remove-potcdate.sin | ||
Rules-piglatin | ||
Rules-swiss | ||
Rules-translit | ||
Rules-windowsdir | ||
swiss.sed |
If you checked out this source tree directly from GRUB Git, you might be wondering where are the POT and PO files. Here are some instructions that will hopefully clarify the situation. - If you're a user or a distributor, simply fill the po directory by importing translations from the Translation Project: ./linguas.sh GRUB's build system will automatically detect those and include them in your install. - If you're a translator and want to add a new translation or improve an existing one, get in touch with the Translation Project (http://translationproject.org/). The GRUB project doesn't interact with translators directly (but we dearly appreciate your work!). - If you're a developer adding/removing/modifying translatable strings, you can check that these turn into a sane POT file by using the `po/grub.pot' make rule. - If you're the maintainer of GNU GRUB preparing a new release, don't forget to include the latest PO files in your source tarball!