Re: [Monotone-devel] Translations revisited

[Patrick Georgi]

Richard Levitte - VMS Whacker schrieb:
> I'm looking at the translations done until now, and this is what I get:
>   
I'm currently looking at what functionality the Makefile in po/ has to 
provide for devs (besides .po -> .gmo/.mo parsing), because I intend to 
remove the dependency on gnu gettext there.

Currently, the Makefile in po/ is created by autopoint, a component of 
gettext. I already rewrote the autoconf tests (as they're also provided 
by gnu gettext - see nvm.portable-gettext-support), but they still need 
some work, and now making that Makefile.in static is my next step.

so, what's necessary?
- .po -> .gmo/.mo compilation, with using LINGUAS and Makevars as 
appropriate
- autoconf tests to figure out which tools to use and which features 
they provide (eg. most of Makevars is utterly useless with solaris' 
gettext variant)
- xgettext runs to extract new versions of .po (into .pot, it seems)
- run of msgmerge where available to merge .po and .pot into a new version

anything else? or is any of these not actually in use?

Also, if the Makefile.in.in in po/ exists, the branch mentioned above 
should compile just fine - at least the configure step runs through and 
creates all variables (with the single known issue, that ENABLE_NLS 
isn't disabled if HAVE_GETTEXT and the like are disabled because the 
libraries can't be found)
However there was no testing on non-solaris platforms yet, reports if 
there are any differences on other platforms are more than welcome!


Regards,
Patrick Georgi