Multi-Language-Interface-design-approach: Difference between revisions
Jump to navigation
Jump to search
Embeddedrf (talk | contribs) |
Embeddedrf (talk | contribs) |
||
| Line 8: | Line 8: | ||
*ADD NEW LANGUAGE | *ADD NEW LANGUAGE | ||
* Make list of Menu Items from a list in a database so they can be added dynamically | <hr> | ||
*Make list of Menu Items from a list in a database so they can be added dynamically | |||
*Include code to create database file in case it gets destroyed in users machine? or just include with install? | |||
== Functional Examples == | == Functional Examples == | ||
Revision as of 12:56, 23 October 2009
Multiple Language Interface - The database approach
- SELECT LANGUAGE
- ENGLISH
- POLISH
- ....
- ADD NEW WORD
- ADD NEW LANGUAGE
- Make list of Menu Items from a list in a database so they can be added dynamically
- Include code to create database file in case it gets destroyed in users machine? or just include with install?
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.