GNUCash translation status

[Derek Atkins]

Claude Paroz <claude at 2xlibre.net> writes:

> Because in GNOME/intltool standard toolchain, all string extraction are
> done with a pure SVN checkout, without any build step or any additional
> dependencies. It's a design choice, and it clearly has its advantages
> (maybe drawbacks too), because you don't have to build anything to
> translate a program.
> Basically, here's the steps necessary to translate any standard GNOME
> program:
> - checkout SVN
> - intltool-update LANG
> - translate
> - msgfmt -o LC_MESSAGES_DIR/LANG.mo LANG.po
> and there it is !

Well, that's effectively all you need to do for GnuCash, but in our
case you just need to add one more step:

  make -C intl-scm -f Makefile.am abs_top_srcdir=`pwd` srcdir=. \
  GUILE=/usr/bin/guile guile-strings.c

Note that you do NOT need to run autogen.sh or configure in order
to do this.  So just run this after the checkout and before
the "intltool-update" and you're done.

> We have also have a request for Damned Lies to consider a
> maintainer-provided .pot file [1]. We may implement this in the future,
> but we clearly want to push forward the procedure described above,
> because it simplifies work for translators.

I dont think we need to do that.  I just hope that your process
is flexible enough that you can add a project-specific "special
case" pre-intltool step.

Actually, if you could add this step then we could even remove
POTFILES.in from SVN again and have you run the generation script
as well.  Again, doesn't require any "building", just a little
bit of preprocessing.

Is your process flexible enough to add this kind of step?

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available