Multi-Language-Interface-design-approach: Difference between revisions
Jump to navigation
Jump to search
Embeddedrf (talk | contribs) |
Embeddedrf (talk | contribs) |
||
| Line 7: | Line 7: | ||
== Language Menus == | == Language Menus == | ||
*ADD NEW WORD | |||
*ADD NEW LANGUAGE | |||
*SELECT LANGUAGE | *SELECT LANGUAGE | ||
**ENGLISH | **ENGLISH | ||
**POLISH | **POLISH | ||
** .... | ** .... | ||
== Pages == | == Pages == | ||
Revision as of 16:10, 23 October 2009
Multiple Language Interface - The database approach
- Make list of Menu Items from a list in a database so they can be added dynamically
- MUST: Include code to create database file > because each language will be a database file of its own
Language Menus
- ADD NEW WORD
- ADD NEW LANGUAGE
- SELECT LANGUAGE
- ENGLISH
- POLISH
- ....
Pages
- Data Base full language selection
- 1st column = english
- 2nd column = *ADDED LANGUAGE*
Functional Examples
Example #1
- Header1=deg '-- set the header of a column on the temperature profile sheet to 'deg'...short for degrees
Change to:
- Header1= Translate(deg)
Translate will be a function that queries a database for a foreign language entry: Language='POLISH' Word='deg'
Example #2
Display function can be used to intercept all UserPrompt text messages > Translate(Message)
Example #3
- Design of language interface should learn. The user should be the source of the translation!
- Must have a language database interface that allows a user to input his language. Even allow an english respin on my terminology.