predictive text works weird with accented words

Bug #1560407 reported by Julia Palandri
This bug report is a duplicate of:  Bug #1430414: Auto-correction does not fix accents. Edit Remove
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Confirmed
Medium
Unassigned
ubuntu-keyboard (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I've seen this both in italian and spanish where there are accented words: if for example in spanish I write "mama", it doesn't suggest anything else. If, instead, I type "mam" (or if I go back and delete the last "a"), it does suggest "mamá" (which is the word I want but am too lazy to tap myself).

It's even more annoying in italian: writing "e" doesn't suggest "è" (which is the one I usually want) but in this case I cannot delete anything to get the suggestion offered and I need to long tap the e key everytime I want to type "è".

Could we make accented words "similar" to those same words without any accentuation so they get suggested?

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report. I agree, it's the same problem in French. When the user types a non accented letter, the keyboard should propose accented variants of the word.

Changed in canonical-devices-system-image:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-keyboard (Ubuntu):
status: New → Confirmed
Revision history for this message
Julia Palandri (julia-palandri) wrote :

Hi @michael-sheldon, I think these are two separate things (most surely related anyway, but different things: this bug is about not getting accentuated words suggested while writing when i write the same word without accents.
The other bug, as per what I understood, is about autocorrection, which might or might not be enabled in the phone at the same time as the suggestions I'm talking about here.

Revision history for this message
Michael Sheldon (michael-sheldon) wrote :

Hi Julia,

 The two actually have the same underlying cause, as the auto-correct simply replaces the user input with the first entry from the prediction engine (assuming it isn't too different from the original input). Unfortunately the current prediction engine (based on libpresage) treats accented forms of characters as being completely unrelated to the non-accented forms, so the predictions it generates (and which are then used for auto-correct) are often not very helpful.

 Thankfully however, we're currently in the process of improving the prediction engine through the use of libskeyer, which should drastically improve the quality of our predictions and part of that is handling accented characters correctly :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.