From: JOSE MARIA GARCIA VALDECASAS BERNAL <jmgvb_at_fedro.ugr.es>
Date: Tue, 03 Sep 2002 19:00:38 +0200 (MET DST)

What i used was a LANG_********** macro in each string
For example if you have to change a text string in a function called id3show, i
used LANG_ID3SHOW_1 for the first string to change, and so on...
maybe it's not the best way, but... that's what i've done :)

Jose

Mensaje citado por: perterm <perterm_at_vce.de>:

> Daniel Stenberg wrote:
>
>
> > #define HELLO_WORLD_ID "hello world"
> > #define BYE_BYTE_WORLD_ID "bye bye world"
>
>
> Do you think it might be a good idea to make a rule that each of these
> macros should have a defined prefix like
>
> #define STR_HELLO_WORLD_ID "hello world"
> #define STR_BYE_BYTE_WORLD_ID "bye bye world"
>
> That might make it easier to write template generators for the
> language-meta-files from the source code.
>
> > My described system is also open for further modifications of the
> format, as
> > we might need to introduce "maximum string length" for specific
> strings etc
> > in the future.
>
>
> In characters or in pixel? I see the necessity but with propfonts that
> will be a difficult task. A simple editable text file will be not an
>
> option any more. It might be necessary to write an
> translation-editor-application that can calculate the real string widths
>
> as they would appear on the Jukebox. That's a bit of overkill
> considering that this translation-editor will be used only every now and
>
> than when a new string/language is added to rockbox.
>
> Phil
>
>
>
>
Received on 2002-09-03