Multi language C embedded - Revision history

Heth: /* Simple Example */

2021-03-27T06:43:41Z

‎Simple Example

2018-05-27T16:17:02Z

2018-05-27T15:40:55Z

2018-05-27T14:26:20Z

‎Design goals

2018-05-27T10:34:33Z

2018-05-27T10:32:29Z

2018-05-27T10:31:59Z

2016-10-25T08:02:26Z

‎Example

2016-10-17T03:52:01Z

2016-10-16T13:47:10Z

‎Design goals

@@ Line 18: / Line 18: @@
 In this small example both languages are in the same file. In a project, you should have a file called english.h where all your english messages should reside. When the project is internationalized send a copy of english.h to the translator with a new name. For example german.h
-'''Remember:''' The translator must keep the variables as indicated by %<TYPE> in all messages.
+'''Remember:''' The translator must keep the variables as indicated by %<TYPE> in all messages, in the same order.
 <source lang=c>
 char const * const danish[] = {
@@ Line 41: / Line 41: @@
 </source>
 The drawback of this method is that the array-members need to come in this exact order and if you delete one of the members, it’s necessary to leave an empty (“”) string as the array-member number is the reference to the string when used. For example textmes(2) references the battery warning.
 == Using array initialization with enum indices ==
 It is possible to initialize arrays – even const arrays – referencing members at compiletime.

@@ Line 45: / Line 45: @@
 <source lang=c>
-enum Errors {
+enum texts {
       ERR_NONEXCOM = 0,
       ERR_INVDATE,
       ERR_LOWBAT,
-  } err;
+  } ;
 char const * const danish[] = {

@@ Line 53: / Line 53: @@
 char const * const danish[] = {
      [ERR_NONEXCOM]  = "FEJL: Kommando eksisterer ikke: %s",
-     [ERR_INVDATE]        = "FEJL: Dato %s ugyldig",
+     [ERR_INVDATE]   = "FEJL: Dato %s ugyldig",
-     [ERR_LOWBAT]        = "Advarsel: Der er kun %u%% batteri tilbage!"
+     [ERR_LOWBAT]    = "Advarsel: Der er kun %u%% batteri tilbage!"
   };
 char const * const english[] = {
-     [ERR_NONEXCOM]   = "ERROR: Non-existing command: %s",
+     [ERR_NONEXCOM]  = "ERROR: Non-existing command: %s",
-     [ERR_INVDATE]         = "ERROR: Invalid Date %s",
+     [ERR_INVDATE]   = "ERROR: Invalid Date %s",
-     [ERR_LOWBAT]         = "Warning: Only %u%% battery left!"
+     [ERR_LOWBAT]    = "Warning: Only %u%% battery left!"
 };

@@ Line 6: / Line 6: @@
 *Easy to change language on-the-fly
 *No padding of strings to max length in arrays
-**In the example below the text strings '''yes''' and '''no''' use the same amount of memory as the long message.
+**In the example below the text strings '''yes''' and '''no''' use the same amount of memory as the long message and will be copied to RAM on a system with firmware.
 <source lang=c>
 char txt[3][] = {

@@ Line 51: / Line 51: @@
   } err;
-//      char const dan[] =  "FEJL: Kommando eksisterer ikke: %s";
+char const * const danish[] = {
 void example(void) {
    char **textmes;
          int i;
        textmes = (char **) &english; // Set english language

@@ Line 40: / Line 40: @@
+}
 </source>
 [[Category:C]]

@@ Line 15: / Line 15: @@
 </source>
-== Example ==
+== Simple Example ==
 In this small example both languages are in the same file. In a project, you should have a file called english.h where all your english messages should reside. When the project is internationalized send a copy of english.h to the translator with a new name. For example german.h

@@ Line 2: / Line 2: @@
 ==Design goals==
-*Should only exist in flash. (No copying to memory)
+*Should only exist in flash. (No copying to RAM)
 *Logical for translators to translate from english to other language.
 *Easy to change language on-the-fly
@@ Line 14: / Line 14: @@
 };
 </source>
 == Example ==
 In this small example both languages are in the same file. In a project, you should have a file called english.h where all your multi language messages should reside. When the project is internationalized send a copy of english.h to the translator with a new name. For example german.h