Does gettext assume/require POSIX printf behaviour?

[Pierre Ossman]

Hi,

I wanted to follow up on this thread in the bug tracker, as it seems to 
have got overlooked there:

https://savannah.gnu.org/bugs/?64006

Context: gettext includes printf replacements on platforms that don't 
have POSIX behaviour, sometimes unconditionally.

My question is if gettext does something internally that requires these 
functions? Or are they just a convenience because the POSIX behaviour is 
very useful when translating?

The reason for my question is that we have constructs where gettext's 
replacement functions might not be used. Do we have hidden bugs there?

Regards
--
Pierre Ossman           Software Development
Cendio AB               https://cendio.com
Teknikringen 8          https://twitter.com/ThinLinc
583 30 Linköping        https://facebook.com/ThinLinc
Phone: +46-13-214600

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?