Re: Internationalizing user interface

On Wed, Oct 23, 2013 at 12:10:44AM +0200, corvid wrote:
> Petr wrote:
> > I notice Dillo is in English only, so I prepared an example how to
> > internationalize the code using gettext.
> > 
> > The initial patch is quite huge due to standard m4 macros supporting the
> > gettext configuration:
> 
> [snip]
> 
> >  30 files changed, 5524 insertions(+), 39 deletions(-)
> > 
> > I don't know what everything you want to track in the hg.
> > 
> > The ABOUT-NLS, config.rpath m4/*, and maybe some files under po/ could get
> > installed through ./autogen.sh by calling gettextize --force --no-changelog.
> > 
> > My proof of concept shows internationalized and the localized into Czech
> > language the `dillo --help' usage and the `File' menu in the GUI.
> > 
> > Should I send the (possibly compressed) patch to this mailing list?
> > 
> > If you liked the patch, I'm willing to walk through all the sources and mark
> > all the stringing suitable for translation.
> 
> I looked in the archive to refresh my memory on where everyone stood on
> gettext. Jorge felt positively toward it in
> http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-August/008658.html
> I was curious about it and tried a small experiment in
> http://lists.auriga.wearlab.de/pipermail/dillo-dev/2011-August/008685.html
> And no one else expressed an opinion. So that's a good sign, anyway.

I like the idea, but we need man-power to create translations and
keep them up to date.
Do we have numbers how this affects the memory consumption and
install-size?
Do we need a compile-time switch to disable it?
How can we keep translation files in sync?

Cheers,
Johannes