[OTR-users] @developers, may I create a german OTR website?

[Thomas B.]

Speaking of compiling gaim-otr from CVS, there's one thing I forgot in
my instructions for applying my internationalisation patch:

If you want to compile with my patch, you'll have to run "intltoolize
--force --copy" at some point, which will copy files necessary for
intltool into the gaim-otr directory. This is either done automatically
when running "makedist" (as I have put that command into the makedist
script) or you have to execute it manually.

This is also a thing that will only affect users building from CVS,
because the intltool files will be distributed with the tarballs created
by "makedist", so that users building from that tarballs won't need to
have intltool installed.

Thomas


Thomas B. schrieb:
> If you want to test it, here's how to do it (at least for Linux users, I
> haven't tried compiling gaim-otr under Windows or other platforms yet):
> Get the CVS source of gaim-otr (e.g. from Sourceforge), extract the
> attached tarball into the gaim-otr directory, apply the patch and
> configure gaim-otr, for example with "makedist" (you'll need intltool
> installed in addition to the packages usually needed to compile gaim-otr
> >from CVS). You should then be able to compile gaim-otr (hopefully
> without errors).
> If that works so far, you can then add new translations with the
> following steps: Go to the "po" subdirectory and execute
> "../intltool-update --pot". That will extract all translateable messages
> >from the gaim-otr source and put it into a PO template file called
> "gaim-otr.pot". You can then copy that file to a new PO file for your
> language (e.g. "de.po") and start translating. If you want the
> translation to be built with the rest of the package, put that PO file
> into the "po" directory, add the language code to the ALL_LINGUAS
> variable in configure.ac, do a "autoreconf" and rebuild gaim-otr.
>
> Thomas
>
>