search

minutekey / ez-access-web

Automatically exported from code.google.com/p/ez-access-web
0 stars 0 forks source link

Support for different languages #45

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
I intend to have basic support for other languages, which means all english 
appended words (AKA 'button') need to be mapped to their equivalent in other 
languages in a JSON file. All files need to have an ISO filetype (or whatever 
to allow strange character codes).

I don't intend to worry about specific word positions at the moment -- that's a 
little too much work at the moment.

This will also allow for telling the Chrome TTS engine which language it's 
speaking.

I propose using the existing lang attribute on the html tag.
http://www.w3schools.com/tags/ref_language_codes.asp

Original issue reported on code.google.com by aeharding on 22 Jul 2013 at 11:05

GoogleCodeExporter commented 8 years ago 
This is good to do for internationalization. The <html lang> attribute is a 
good place to get this information. Note also that languages can be applied to 
particular elements on a page.

Do you envision the internationalization "dictionary" to key off of the English 
words we use for the different roles? Or do you see yourself having a constant 
which provides the index to the dictionary?
#1. ret = "button" then lookup "button" as the key to a different language.
#2. ret = ROLE_BUTTON (where ROLE_BUTTON is "button" in English)

Original comment by jbjor...@gmail.com on 24 Jul 2013 at 8:13

GoogleCodeExporter commented 8 years ago 
We may wish to look into XRegExp (http://xregexp.com/) with Unicode base to 
help with i18n. We use regex a few places, namely in speaking a string that is 
currently being entered (see issue 49) and the isMumboJumbo() function. With 
unicode support by XRegExp, then we can use broad character classes instead of 
trying to catch everything a char at a time.

Original comment by jbjor...@gmail.com on 23 Aug 2013 at 1:55