Re: [dcplusplus-devel] Internationalization

[Jacek S. <arn...@gm...>]

> Did you mean that win32 doesn't have positional parameters? I'm not a 
> win32 developer, but what about printf_p? Doesn't seem that standard 
> though...
> 
> printf_p: http://msdn2.microsoft.com/en-us/library/bt7tawza(VS.80).aspx
> 
We're limited to using msvcrt.dll (essentially msvc 6.0) which is the only widely available c
library on windows (the others are restricted for redistribution and not supported by mingw), so no.

> Why just not use the syntax of printf's positional parameters? Since 
> gettext recognizes them. Also, translators are more likely to recognize 
> something that is commonly used.
Because then we'd have to reimplement the rest of printf (all other formatting flags) or limit the
support to %m$s (strings)...it's feasible but not optimal. At this point we might as well ship a
complete free implementation of printf (gettext includes one with a c++ wrapper which solves some of
the issues of normal printf), but IMHO if we're to ship a printf, we might as well use boost which
is widely supported and fits well with c++ in general (unlike the gettext wrapper which is not
typesafe and still requires that types be specified in the formatting string)...

> The gnutext manual is geared towards the use case where two packages are 
> merged. I would need to read further, but I think it's possible to 
> "sync" translations between win32/linux using msgcomm and msgcat 
> intelligently.
Automatically is better than intelligently...

> I'm glad to hear this talk about i18n... :)
talk in this case isn't enough though =)

/J