Mercurial > pidgin
annotate README.mingw @ 31167:060739bdc84d
Suppress msgfmt errors by removing c-format markers
This is unfortunate, but it's the best that I could come up with. The
translator, Khaled Hosny, informed me that C does not allow you to skip
positional format string arguments, and printf(3) on my system agrees.
It does work on glibc, but I'm not sure if gettext guarantees this. It
does make other guarantees about the printf implementation above those
from C, but this involves replacing the printf function if the native one
doesn't provide it. So, even assuming that gettext's printf allows this
like glibc's does, gettext may not replace the printf function if the
native C printf provides positional arguments but does not allow skipping
them.
Finally, intltool-update does not seem to put the c-format marker back,
which actually surprised me. So we'll see how this goes long-term.
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Wed, 26 Jan 2011 18:48:19 +0000 |
parents | 416a125b66ac |
children |
rev | line source |
---|---|
16209
416a125b66ac
Fix win32 build after autoreply was moved back to the plugin pack.
Daniel Atallah <daniel.atallah@gmail.com>
parents:
16039
diff
changeset
|
1 How to build Pidgin for Windows using MinGW |
416a125b66ac
Fix win32 build after autoreply was moved back to the plugin pack.
Daniel Atallah <daniel.atallah@gmail.com>
parents:
16039
diff
changeset
|
2 ============================= |
3630 | 3 |
16209
416a125b66ac
Fix win32 build after autoreply was moved back to the plugin pack.
Daniel Atallah <daniel.atallah@gmail.com>
parents:
16039
diff
changeset
|
4 For the latest build instructions, please refer to: |
3630 | 5 |
16209
416a125b66ac
Fix win32 build after autoreply was moved back to the plugin pack.
Daniel Atallah <daniel.atallah@gmail.com>
parents:
16039
diff
changeset
|
6 http://developer.pidgin.im/wiki/BuildingWinPidgin |