Comment 25 for bug 927931

Here are some more ideas:

1. Dialog window on first run that asks whether you want RTL or not
2. Detect whether user is accustomed to RTL using webcam and eyeball processing logic (only joking)
3. Turn on RTL according to user's geographic location (simply a bad idea)
4. Determine whether user uses RTL by going through his files and browser history (might draw some headlines around the webs)
5. Determine whether user is RTL by listening on the microphone and detecting spoken langauges (I didn't think I'd think of this many ways to do this)

Are there significant GUI elements added for RTL support?

If CTL has more to it than RTL and enabling it adds a significant amount of GUI elements which are not RTL then perhaps CTL can be broken into RTL and other different independent features. That way turning RTL on would only add the RTL GUI elements thus having it on by default for everyone could be considered OK.

If there are indeed significant additions of RTL related elements in the GUI when RTL is on, then perhaps they can be made more discrete or less confusing somehow for non-RTL users, thus RTL could be turned on by default.

What about a dialog window popping up at the first occurrence of a character being typed in where that character originates in a RTL language? That window would ask whether to turn RTL support on. How about skipping the window and just enabling RTL in that case? Or how about popping up a window that just mentions that RTL support has been enabled because an RTL language was detected and that RTL support can be turned off in the settings. On second thought, this can be triggered by the editing of a document that has RTL in it.

Perhaps if it is only viewing a document with RTL then nothing will happen; when editing one a window asking whether to turn RTL on will appear; and when an RTL character is typed, then it would be turned on with or without a dialog window.

Thanks,
Shahar