Multi-Language-Interface-design-approach: Difference between revisions
Jump to navigation
Jump to search
Embeddedrf (talk | contribs) |
Embeddedrf (talk | contribs) |
||
| Line 16: | Line 16: | ||
== Pages == | == Pages == | ||
*Data Base full language | *add a menu in the upper bar for LANGUAGE | ||
*ADD A LANGUAGE: PopUp a small window to enter a new language name | |||
**adds language name to the language database | |||
**creates a new database table for that language | |||
*ADD TRANSLATIONS: Data Base full language display & entry > works with language tables | |||
**1st column = english KeyWord | **1st column = english KeyWord | ||
**2nd column = *ADDED LANGUAGE* | **2nd column = *ADDED LANGUAGE* | ||
**behavior - highlight the untranslated column rows? | |||
**limit length of translation | |||
== Functional Examples == | == Functional Examples == | ||
Revision as of 17:33, 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
- add a menu in the upper bar for LANGUAGE
- ADD A LANGUAGE: PopUp a small window to enter a new language name
- adds language name to the language database
- creates a new database table for that language
- ADD TRANSLATIONS: Data Base full language display & entry > works with language tables
- 1st column = english KeyWord
- 2nd column = *ADDED LANGUAGE*
- behavior - highlight the untranslated column rows?
- limit length of translation
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.
Example #4
- page captions should be translated