Path: csiph.com!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Stefan Reuther <stefan.news@arcor.de>
Newsgroups: comp.arch.embedded
Subject: Re: How to add the second (or other) languages
Date: Wed, 12 Feb 2025 18:14:26 +0100
Lines: 50
Message-ID: <voioe3.598.1@stefan.msgid.phost.de>
References: <voii3i$28jmm$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net C9wRBe7F4LS28nE1YvjeTwWnc7Z4L9bKNw/Zrxi+pQ5DL6WI5B
Cancel-Lock: sha1:77wgdWKxBzHBjvlp5NlRzs7llyY= sha256:u+0uN9hjxUNLS6zMAUAJGewW2NIG0L77gWUfuCFqvZA=
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 Hamster/2.1.0.1538
In-Reply-To: <voii3i$28jmm$1@dont-email.me>
Xref: csiph.com comp.arch.embedded:32332

Am 12.02.2025 um 17:26 schrieb pozz:
> #if LANGUAGE_ITALIAN
> #  define STRING123            "Evento %d: accensione"
> #elif LANGUAGE_ENGLISH
> #  define STRING123            "Event %d: power up"
> #endif
[...]
> Another approach is giving the user the possibility to change the
> language at runtime, maybe with an option on the display. In some cases,
> I have enough memory to store all the strings in all languages.

Put the strings into a structure.

  struct Strings {
      const char* power_up_message;
  };

I hate global variables, so I pass a pointer to the structure to every
function that needs it (but of course you can also make a global variable).

Then, on language change, just point your structure pointer elsewhere,
or load the strings from secondary storage.

One disadvantage is that this loses you the compiler warnings for
mismatching printf specifiers.

> I know there are many possible solutions, but I'd like to know some
> suggestions from you. For example, it could be nice if there was some
> tool that automatically extracts all the strings used in the source code
> and helps managing more languages.

There's packages like gettext. You tag your strings as
'printf(_("Event %d"), e)', and the 'xgettext' command will extract them
all into a .po file. Other tools help you manage these files (e.g.
'msgmerge'; Emacs 'po-mode'), and gcc knows how to do proper printf
warnings.

The .po file is a mapping from English to Whateverish strings. So you
would convert that into some space-efficient resource file, and
implement the '_' macro/function to perform the mapping. The
disadvantage is that this takes lot of memory because your app needs to
have both the English and the translated strings in memory. But unless
you also use a fancy preprocessor that translates your code to
'printf(getstring(STR123), e)', I don't see how to avoid that. In C++20,
you might come up with some compile-time hashing...

I wouldn't use that on a microcontroller, but it's nice for desktop apps.


  Stefan