From: Florian Mösch <fmoesch_at_web.de>
Date: Mon, 16 Sep 2002 12:42:32 +0200

> This is an issue of compactness in the rather small memory space and
> CPU speed which we have, not just source code compactness and
> readability. We're talking about an order of magnitude of more CPU
> and memory usage here.

I know what you are talking about. I'm a software developer programming
(Texas Instruments) DSPs with only little memory, well still a little
more thah the Archos' SH DSP...

And I wrote more than once that I don't want to implement the gettext
*library* on the SH but use the gettext *.po file format* in favor to a
proprietary one. Instead of building a lang.h header file from the
lang.txt file using (at this point very limited) perl scripts you could
also substitute the _("some string") occurences in the souces to
constants - even to your preferred str(SOME_STRING) - automagically. I
believe that you could archieve the same as in daniels design with the
same effort

  - (human-readable) source files

  - a perl (or whatever you like) script to produce (machine-readable)
    source files with constants instead of strings

  - existing GNU gettext tools to produce the .po files for the
    translator (to be edited with existing tools)

  - a 2nd perl script to get the translated string from the .po file
    and write a lang.h header file with your defines.

Bye,
   Florian
Received on 2002-09-16