© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi Chris. I asked around a bit for thoughts about this, and I try to summarize the various points of view here.
Firstly, since you talked about "all JS", I'm not sure if you missed that mozvoikko has a dependency on the libvoikko library, which then depends on the 7MB voikko-fi package. This would mean that while the Ubuntu's current mozvoikko component is not a binary itself, spreading it via addons.mozilla.org would mean spreading it in form of a ca. 8MB binary extension instead, duplicating libraries.
As mozvoikko is anyway part of language support, it could be argued that there are enough reasons that Finnish users should continue to be given optimal out of-the-box Ubuntu experience including spell-checking support in e-mail and browser, similar to other language users.
However, according to the voikko main developer, it may be possible to consider using addons.mozilla.org with only the mozvoikko component included (requiring user to have libvoikko already installed), but there would be three work items to be done:
- mozvoikko should be modified to support a broad selection of libvoikko versions, so that users of also older distro versions could use it, and also future API changes in libvoikko should be brought in in a way that doesn't break the extension.
- mozvoikko should have notification system and guidance about possibly missing libvoikko
- testing with various operating systems should be made easy and automated
Those could be possible to be done in the future (although that would still mean no out-of-the-box spell-checking support in Mozilla products for the end users).
There is then an additional potential problem that if eg. Fedora and Debian continue to ship mozvoikko in their default installs, while Ubuntu would want users to manually install the extension via a.m.o. This would then mean both maintaining the packaging in multiple distributions while also needing to maintain the a.m.o version.
I'm not aware how the disabled-by-default issue is going to be handled in the other distributions.