User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060710 Firefox/2.0b1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1b1) Gecko/20060710 Firefox/2.0b1 I installed Russian dictionary from here http://www.mozilla.com/thunderbird/dictionaries.html, but it didn't appear in the dictionary list under Languages of the textarea context menu. Having investigated the problem I found out that dictionaries got installed in FirefoxDir/components/myspell directory, but Firefox looks for them in FirefoxDir/dictionaries. After moving ru.aff and ru.dic files into FirefoxDir/dictionaries and restarting Firefox Russian did appear in the Languages menu, but no Russian spell check occurs. Only English words are underlined (with no spelling suggestions), but Russian (misspelled) are left untouched. Reproducible: Always Steps to Reproduce: 1. Install Russian dictionary from http://www.mozilla.com/thunderbird/dictionaries.html 2. Observe, that no Russian appeared under Languages 3. Move ru.aff and ru.dic from FirefoxDir/components/myspell to FirefoxDir/dictionaries 4. Observe, that Russian appeared under Languages, but no Russian spell check occurs. Actual Results: Installing and using new dictionaries seems broken Expected Results: New dictionary should have been installed into correct location and should work

Been like this since bug 216382 landed. Will be fixed for Firefox 2.0.

This is the equivalent of TB bug 343901 and SM bug 345612. Adding dependency and requesting blocking flag. Perhaps should be moved to Core: Spelling Checker

How is this (and bug 343901) not a dup of bug 343076? We need new dictionary packaging, period.

The summary for bug 343076 would need to be widdened to encompose this and the other bugs as duplicates but I suppose "Update" product isn't always the most obvious place for people to look.

Saying that, the various products might want to leave the bugs open so that they have the blocking-<product> flags set for each product.

bug 343076 will cover what we're going to do here, seems like.

*** This bug has been marked as a duplicate of 343076 ***