Closed Bug 1026309 Opened 10 years ago Closed 6 years ago

[Sora]Word prediction & Word correction are not supported for Greek.

Categories

(Firefox OS Graveyard :: Gaia::Keyboard, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sync-1, Unassigned)

References

Details

Firefox OS v1.3
 Mozilla build ID:20140422024003
 
 
 REPRODUCING PROCEDURES:
 Description: 
 In keypad, Word prediction & Word correction are not supported for Greek
 
 
 Customer Impact Statement: 
 Inconvenient for the Greek customer. Very difficult to type. Rather poor impression for a Smartphone
 
 
 Expected Behaviour: 
 Word prediction & Word correction must be supported for Greek
Greek dictionary file is included in 1.3, see https://github.com/mozilla-b2g/gaia/blob/v1.3/keyboard/layouts/el.js and https://github.com/mozilla-b2g/gaia/blob/v1.3/keyboard/dictionaries/el_wordlist.xml.

Where does this build come from?
Status: NEW → UNCONFIRMED
Ever confirmed: false
Flags: needinfo?(sync-1)
(In reply to Jan Jongboom [:janjongboom] (Telenor) from comment #1)
> Greek dictionary file is included in 1.3, see
> https://github.com/mozilla-b2g/gaia/blob/v1.3/keyboard/layouts/el.js and
> https://github.com/mozilla-b2g/gaia/blob/v1.3/keyboard/dictionaries/
> el_wordlist.xml.
> 
> Where does this build come from?

This issue is occur on typing sms. 
When you create a sms with Greek keyboard, you will find Word prediction & Word correction are not supported for Greek.
Flags: needinfo?(sync-1)
Any pointers on where to look for a fix here?
Status: UNCONFIRMED → NEW
Ever confirmed: true
As far as I can see, the SMS-specific Greek keyboard layout, from bug 914454, uses ASCII-7 uppercase English chars in place of several uppercase Greek chars. For example, ε (uppercase: Ε) in the normal Greek layout [1] becomes E in the SMS layout [2]. As such chars are lexicographically different, naively dropping in the dictionary information (by appending |autoCorrectLanguage: 'el'| at [3]) won't work.

[1] https://github.com/mozilla-b2g/gaia/blob/master/apps/keyboard/js/layouts/el.js#L26
[2] https://github.com/mozilla-b2g/gaia/blob/master/apps/keyboard/js/layouts/el.js#L58
[3] https://github.com/mozilla-b2g/gaia/blob/master/apps/keyboard/js/layouts/el.js#L51

I think the most "correct" way to fix this (if the original reason of bug 914454 still stands and we want to keep the separate, ASCII-7 chars layout) is to implement a transformation layer in front of the prediction engine that does uppercase-English to uppercase-Greek transformation when transmitting user input to the engine, and the reverse when transmitting prediction results to the list-of-suggestions panel (and subsequently to the SMS field). If that's not applicable then we'll want a second Greek dictionary that uses those uppercase-English chars (which is quite messy if you ask me).

Not sure how much sense this all makes for real use, and how much work it's gonna be, though.
link all Fire C (codename: Sora) bugs to a meta one.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.