Open
Bug 355066
Opened 18 years ago
Updated 2 years ago
app-neutral location to store dictionaries (share dictionaries between Mozilla products)
Categories
(Core :: Spelling checker, enhancement)
Tracking
()
REOPENED
People
(Reporter: kuno.meyer, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060918 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20060918 Firefox/2.0
I've just detected that the spell checker of FF 2.0 uses it's own copy of dictionaries placed in the <FF>/dictionaries/ subfolder. Thunderbird on the other hand stores them in <TB>/components/myspell. (Needless to say that each program saves the personal dictionaries at their own places, resulting in the user adding over and over again the same words to dictionaries.)
Isn't it possible to share at least those common runtime infrastructure (like spell checking or the gecko engine) that are used by all apps of the mozilla platform (firefox+thunderbird at least) in a common place?
Similar: There's bug 310285 about sharing dictionaries between TB and OpenOffice.
Reproducible: Always
Comment 1•16 years ago
|
||
Not a bad idea, should be in Core though.
Status: UNCONFIRMED → NEW
Component: General → Spelling checker
Ever confirmed: true
Product: Firefox → Core
QA Contact: general → spelling-checker
Summary: sharing dictionaries+user-provided entries between firefox and thunderbird → use an app-neutral location to store dictionaries
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Comment 3•15 years ago
|
||
Sorry, that was a mistake.
Bug 226699 is about personal dictionaries.
This is about sharing the main dictionary between Firefox and Thunderbird.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Summary: use an app-neutral location to store dictionaries → app-neutral location to store dictionaries (share dictionaries between Mozilla products)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•