mirror of
https://github.com/moparisthebest/pacman
synced 2024-12-23 08:18:51 -05:00
7eaad2f2a9
Currently xgettext apparently attempts to autodetect c format strings (eg a string with a %s) to decide whether to use c-format flag or not. If we use --flag=_:1:c-format instead of --flag=_:1:pass-c-format, the c-format will be applied everywhere. I couldn't find this documented anywhere though. But the pass prefix is mentioned here : http://www.gnu.org/software/gettext/manual/html_node/xgettext-Invocation.html#xgettext-Invocation "Specifies additional flags for strings occurring as part of the argth argument of the function word. The possible flags are the possible format string indicators, such as ‘c-format’, and their negations, such as ‘no-c-format’, possibly prefixed with ‘pass-’." And c-format is documented there : http://www.gnu.org/software/gettext/manual/html_node/c_002dformat-Flag.html#c_002dformat-Flag "This situation happens quite often. The printf function is often called with strings which do not contain a format specifier. Of course one would normally use fputs but it does happen. In this case xgettext does not recognize this as a format string but what happens if the translation introduces a valid format specifier? The printf function will try to access one of the parameters but none exists because the original code does not pass any parameters." And that's exactly what happened with FS#9658. So using c-format for every string will prevent this issue from happening again. Signed-off-by: Chantry Xavier <shiningxc@gmail.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| cs.po | ||
| de.po | ||
| en_GB.po | ||
| es.po | ||
| fr.po | ||
| hu.po | ||
| it.po | ||
| LINGUAS | ||
| Makefile.in.in | ||
| Makevars | ||
| pacman.pot | ||
| pl.po | ||
| POTFILES.in | ||
| pt_BR.po | ||
| remove-potcdate.sin | ||
| ru.po | ||
| zh_CN.po | ||