Rocket U2 | UniVerse & UniData

Many years ago we changed our web-based software to support prompts, menu items, and help to support multiple languages. We did that by using a number for the prompt like 2300 was "Customer Name". Depending on the language you would go to the matching language file to translate the 2300 number to "Nombre cliente" for Spanish and "Nom du client" in French for example.

In the 18 years we have demoed this to United States-based companies nobody expressed any interest until last week. This  client would like to have code files like 

• Code A1 equals Apple or Pomme in Spanish
• Code Z1 equals Avacado or Avocat in Spanish

Our Universe database has a file called Fruits in this example. So my questions for those who have done this are:

• Do you add a field for every language?
• Do you add a multivalue field for every language?
• Do you change the value in the file to a number and translate it to a language field?
• Do you add a file called Fruit_ES for Spanish?
• Depending on the method chosen, how does a SELECT Fruits work for each language?

Regards,

Doug

Last auto-saved at 09-06-2024 15:06

------------------------------
Doug Averch
Owner
U2 Logic
------------------------------

Many years ago we changed our web-based software to support prompts, menu items, and help to support multiple languages. We did that by using a number for the prompt like 2300 was "Customer Name". Depending on the language you would go to the matching language file to translate the 2300 number to "Nombre cliente" for Spanish and "Nom du client" in French for example.

In the 18 years we have demoed this to United States-based companies nobody expressed any interest until last week. This  client would like to have code files like 

• Code A1 equals Apple or Pomme in Spanish
• Code Z1 equals Avacado or Avocat in Spanish

Our Universe database has a file called Fruits in this example. So my questions for those who have done this are:

• Do you add a field for every language?
• Do you add a multivalue field for every language?
• Do you change the value in the file to a number and translate it to a language field?
• Do you add a file called Fruit_ES for Spanish?
• Depending on the method chosen, how does a SELECT Fruits work for each language?

Regards,

Doug

Last auto-saved at 09-06-2024 15:06

------------------------------
Doug Averch
Owner
U2 Logic
------------------------------

Many years ago we changed our web-based software to support prompts, menu items, and help to support multiple languages. We did that by using a number for the prompt like 2300 was "Customer Name". Depending on the language you would go to the matching language file to translate the 2300 number to "Nombre cliente" for Spanish and "Nom du client" in French for example.

In the 18 years we have demoed this to United States-based companies nobody expressed any interest until last week. This  client would like to have code files like 

• Code A1 equals Apple or Pomme in Spanish
• Code Z1 equals Avacado or Avocat in Spanish

Our Universe database has a file called Fruits in this example. So my questions for those who have done this are:

• Do you add a field for every language?
• Do you add a multivalue field for every language?
• Do you change the value in the file to a number and translate it to a language field?
• Do you add a file called Fruit_ES for Spanish?
• Depending on the method chosen, how does a SELECT Fruits work for each language?

Regards,

Doug

Last auto-saved at 09-06-2024 15:06

------------------------------
Doug Averch
Owner
U2 Logic
------------------------------

Manu,

Just another option, have a multi-flle where each sub-file is for a specific language. Using this technique with a  PRODUCT file you could open and re-use the language-specific sub-file without having langiage-specific code scattered - e.g. "PRODUCT_CODES,FRENCH" or "PRODUCT_CODES,SPANISH" and read the required.data with the same record key.

For example, if the language is FRENCH then the code envelope could be something like:

LANGUAGE="FRENCH"
OPEN "PRODUCT_ NAMES,":LANGUAGE TO F.PRODUCTNAMES ELSE ......
...
...

READV R.PRODUCT.NAME FROM F.PRODUCTNAMES,PRODUCTCODE,1 ELSE.....

in this example the product code is the key to the langiage subfile to be used for all canned text such as the product name, and attribute 1 is the text name.

Regards

JJ

Many years ago we changed our web-based software to support prompts, menu items, and help to support multiple languages. We did that by using a number for the prompt like 2300 was "Customer Name". Depending on the language you would go to the matching language file to translate the 2300 number to "Nombre cliente" for Spanish and "Nom du client" in French for example.

In the 18 years we have demoed this to United States-based companies nobody expressed any interest until last week. This  client would like to have code files like 

• Code A1 equals Apple or Pomme in Spanish
• Code Z1 equals Avacado or Avocat in Spanish

Our Universe database has a file called Fruits in this example. So my questions for those who have done this are:

• Do you add a field for every language?
• Do you add a multivalue field for every language?
• Do you change the value in the file to a number and translate it to a language field?
• Do you add a file called Fruit_ES for Spanish?
• Depending on the method chosen, how does a SELECT Fruits work for each language?

Regards,

Doug

Last auto-saved at 09-06-2024 15:06

------------------------------
Doug Averch
Owner
U2 Logic
------------------------------

Hi John,

Yes, of course.
It's the method used by  SB+ Multi-Language of the app's texts. 
But for data's texts, we evaluated it much more cumbersome to execute, maintain, copy, transfer, update if all  are multilingual.

There is a many road to go to Rome

With kind regards
Manu 

Manu,

Just another option, have a multi-flle where each sub-file is for a specific language. Using this technique with a  PRODUCT file you could open and re-use the language-specific sub-file without having langiage-specific code scattered - e.g. "PRODUCT_CODES,FRENCH" or "PRODUCT_CODES,SPANISH" and read the required.data with the same record key.

For example, if the language is FRENCH then the code envelope could be something like:

LANGUAGE="FRENCH"
OPEN "PRODUCT_ NAMES,":LANGUAGE TO F.PRODUCTNAMES ELSE ......
...
...

READV R.PRODUCT.NAME FROM F.PRODUCTNAMES,PRODUCTCODE,1 ELSE.....

in this example the product code is the key to the langiage subfile to be used for all canned text such as the product name, and attribute 1 is the text name.

Regards

JJ

Many years ago we changed our web-based software to support prompts, menu items, and help to support multiple languages. We did that by using a number for the prompt like 2300 was "Customer Name". Depending on the language you would go to the matching language file to translate the 2300 number to "Nombre cliente" for Spanish and "Nom du client" in French for example.

In the 18 years we have demoed this to United States-based companies nobody expressed any interest until last week. This  client would like to have code files like 

• Code A1 equals Apple or Pomme in Spanish
• Code Z1 equals Avacado or Avocat in Spanish

Our Universe database has a file called Fruits in this example. So my questions for those who have done this are:

• Do you add a field for every language?
• Do you add a multivalue field for every language?
• Do you change the value in the file to a number and translate it to a language field?
• Do you add a file called Fruit_ES for Spanish?
• Depending on the method chosen, how does a SELECT Fruits work for each language?

Regards,

Doug

Last auto-saved at 09-06-2024 15:06

------------------------------
Doug Averch
Owner
U2 Logic
------------------------------