ec5f98abda
* commands/help.c: Include `<grub/i18n.h>'. (grub_cmd_help): Gettextizze. (GRUB_MOD_INIT): Likewise. * commands/i386/pc/play.c: Include `<grub/i18n.h>'. (GRUB_MOD_INIT): Gettextizze. * commands/search.c: Include `<grub/i18n.h>'. (options): Gettextizze. (GRUB_MOD_INIT): Gettextizze. * lib/arg.c: Include `<grub/i18n.h>'. (help_options): Gettextizze. (find_long): Likewise. (grub_arg_show_help): Likewise. * normal/dyncmd.c: Include `<grub/i18n.h>'. (read_command_list): Gettextizze. * po/POTFILES: Add `commands/i386/pc/play.c', `commands/search.c', `commands/help.c', `lib/arg.c' and `normal/dyncmd.c'. |
||
---|---|---|
.. | ||
POTFILES | ||
POTFILES-shell | ||
README |
If you checked out this source tree directly from GRUB Bazaar, 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: rsync -Lrtvz translationproject.org::tp/latest/grub/ po 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/modifiing 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!