Add autocorrect for Breton (br) locale



Firefox OS
4 years ago
5 months ago


(Reporter: tchevalier, Unassigned)


Firefox Tracking Flags

(Not tracked)



(1 attachment)

Michel Nédélec pointed us to the Breton dictionary used on Desktop:

Would that be enough to add autocorrect to Breton on Firefox OS?

Latin dictionary are stored here
And I have no idea how the .xml files are generated.

Delphine, do you have any idea on who can help us here?
Flags: needinfo?(lebedel.delphine)
Hi Theo. Kevin Scannell would probably know how to help here. 
BTW we've spoken about working on auto-correction for all locales who don't have it yet, and have defined a list of locales sorted by priorities. Breton is in fact part of it.
Adding Kevin in CC so he can advise here as needed.
Flags: needinfo?(lebedel.delphine)

Comment 2

4 years ago
I have good data for Breton and can create a frequency list without too much trouble. I'll restrict to words accepted by the spell checker linked above, unless advised otherwise by Michel.

Comment 3

4 years ago
Here's my attempt; about 60,000 words in total:
Oops, looks like your link has expired, Kevin. Would you mind attaching it again? :)
Flags: needinfo?(kscanne)

Comment 5

3 years ago
Created attachment 8633258 [details]
Breton autocorrect frequency list

Attaching it this time!
Flags: needinfo?(kscanne)
Woops, seems like this has been ready for a while but no one took it over. 
Tim, can you help so someone can land this? thanks!
Flags: needinfo?(timdream)
Set the assignee to me. Will get to this bug eventually.
Assignee: nobody → timdream
Flags: needinfo?(timdream)
Unfortunately I no longer have time to work on this. Whoever interested should follow

and convert a dict file and put it to the correct place in the tree. Please also file an compete a bug like bug 1054902 to get the dict file on CDN too.
Assignee: timdream → nobody
Mentor: timdream
Mentor: timdream

Comment 9

5 months ago
Firefox OS is not being worked on
Last Resolved: 5 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.