Bug 186421
Summary: | Cannot install / use en_GB dictionary | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | simon |
Component: | thunderbird | Assignee: | Christopher Aillon <caillon> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | dwlegg, olivier.lelain |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-09-25 15:46:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
simon
2006-03-23 14:34:15 UTC
I used to have the same problem but it's the permission. You need to install the dictionary while running thunderbird as root and then go to your thunderbird install folder/components/myspell and chmod the contents to 755. Start thnderbird as a normal user and you now have the dictionary. Ah, great that worked. So is this thunderbird not setting the correct perms, or is it the dictionary .xpi? It's because the dictionary is installed into the program folder not the /home profile folder so requires root access, I believe this is a known thunderbird dictionary problem and will be changed sometime in the future, but no idea when. Is it worth having a set of dictionary RPMs like the openoffice.org-langpack ones? Alternatively since the OpenOffice dictionaries can be used, language packs which create appropriate symlinks in components/myspell as described by <http://www.mozilla.com/thunderbird/dictionaries.html> and pull in the corresponding openoffice.org-langpack as a dependency? With the latest thunderbird update (thunderbird-1.5.0.2-1.1.fc5) my dictionary is broken again. I tried reinstalling it and resetting the permissions and it does appear in the dictionary list. However *every* word in my email is flagged as being spelt incorrectly. This in fact happened with the default dictionary before I reinstalled the uk one. Updates typically change the directory name, so now you need the dictionaries under something like /usr/lib/thunderbird-1.5.0.2/components/myspell, I've just done the symlink OpenOffice dictionaries thing again as described above. This is a pretty good argument for having the dictionaries under the FC package management system somehow (or, more simply, dictionaries installable under /home) It all breaks dont to two different possibilites: a) user the OpenOffice.org myspell b) install when run application as root. Both do not present a long term solution. One suggestion would be to have a location like /usr/lib/mozilla/components that has no changing name of the parent folder. The other solution would be that OpenOffice.org and Thunderbird both would use an extra myspell package as a dependency. I think the latter qwould be the better solution as then additional applications could use this. Another thing is the the dictionaries should install into $HOME/thunderbird or at least Thunderbird should extend its PATH to look there also. this bug is related. What I do every time a new thunderbird RPM appears is this: 1. Install the new thunderbird (using yum update.) 2. Find the old version of the dictionaries in /var/.../myspell 3. Cd to the new myspell directory. 4. Create soft links that point to wherever the old version's dictionary files were. I would have thought that the RPM installer script could do that with a little bit of ingenuity :) However, that would mean giving every user the same dictionaries. So the idea of simply making thnderbird look in $HOME/.thunderbird for extra dics seems like the right solution to me (writing merely as a user.) Yeah, thunderbird will look in the profile directory in 2.0 but dictionaries also need to be updated to install there. It is a rather major effort that is ongoing upstream... but unfortunately it means the fix won't make it to fc5. It'll be fixed in FC7 for sure, but probably not FC6. |