Add a Bulgarian spellcheck dictionary. ...

Add a  Bulgarian spellcheck dictionary. 

dic/aff files were taken from http://bgoffice.sourceforge.net and bdic file
was generated using our convdict tool. 
The version 4.2 for firefox/seamonkey/thunderbird is used instead of one
for Openoffice. They're almost identical, but the former has 'conditions' for
SFX rules while the latter does not. I also copied MAP entries from 
the OpenOffice version. In the process, I removed Latin letters from MAP
entries because the way we use them, it's not useful. In the future, we may
consider adding them back when we support cross-script spellchecks. 


BUG=33327
TEST=1. Copy bg_BG-2-0.bdic to Dictionaries directory (under the folder where
chrome.exe is on Windows or profiles directory on Linux/Mac) and launch Chrome.
2. Go to a page with an text area. 
3. Switch the spellcheck lang to Bulgarian
4. Copy some Bulgarian text and add or delete a letter or two from words and see if original words pop up in the suggestion. 



Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=46150

[jungshik at Google, 2010-04-29 00:27:24]

dic file is included in the CL, but is not uploaded due to the size.

[Mark Larson, 2010-04-29 05:42:41]

Please rename the README to README.chromium.

+cc Evan. He's working on a tool to harvest license info from third_party stuff
and I want to make sure we support that tool here.

http://codereview.chromium.org/1759010/diff/6001/10001
File third_party/hunspell/dictionaries/README_bg_BG.txt (right):

http://codereview.chromium.org/1759010/diff/6001/10001#newcode1
third_party/hunspell/dictionaries/README_bg_BG.txt:1: The
Firefox/Thunderbird/Seamonkey Bulgarian dictionary
Can you please include

Name: Bulgarian Dictionary
URL: http://bgoffice.sourceforge.net/
License File: <path to MPL-1.1.txt>

See /trunk/src/third_party/ffmpeg/README.chromium as an example.

This helps conform to the license-checking tool (/trunk/src/tools/licenses.py)
that Evan M. has been working on.

http://codereview.chromium.org/1759010/diff/6001/10001#newcode18
third_party/hunspell/dictionaries/README_bg_BG.txt:18: For details read file
GPL-2.0.txt, LGPL-3.0.txt and MPL-1.1.txt.
Shouldn't we include one of these files (LGPL-3.0.txt or MPL-1.1.txt) in our
tree?

[Hironori Bono, 2010-04-29 12:58:54]

LGTM when the comments from Mark are fixed.
By the way, would it be possible to add the original "bg_BG.dic" file so we can
see the source? (If it is hard to add it to this change because of the size
restriction of Rietveld, it would be welcome to add it directly or create a
separate change.)
Thank you so much for your change.

Regards,

Hironori Bono

[jungshik at Google, 2010-04-29 16:24:26]

On 2010/04/29 12:58:54, hbono wrote:
> LGTM when the comments from Mark are fixed.
> By the way, would it be possible to add the original "bg_BG.dic" file so we
can
> see the source? 

Yes, that file IS a part of this CL, but it's not uploaded here because it's too
large (I do want to upload it, but Rietveld wouldn't let me :-) ). When I check
in the CL, it'll be added. 


> Thank you so much for your change.
> 
> Regards,
> 
> Hironori Bono

[jungshik at Google, 2010-04-29 16:30:08]

On 2010/04/29 05:42:41, Mark Larson wrote:
> Please rename the README to README.chromium.
> 
> +cc Evan. He's working on a tool to harvest license info from third_party
stuff
> and I want to make sure we support that tool here.

I'm not sure how to deal with  README files for hunspell dictionaries. At the
moment, there are separate README files for each dictionary. README.ll_RR.  We
didn't even bother to change the character encodings of those files (which are
often in legacy encodings). We can convert them all to UTF-8 and combine them to
a single README.chromium. 

As for LGPL, MPL, and GPL files, other dictionaries also refer to them. So, I
think we have to include copies of those license files if they're not elsewhere
in the tree. 

To Evan: combining README.ll-RR's to a single README.chromium works with your
tool?  Or, is it better to have README.ll-RR.chromium (like.
README.en-US.chromium, README.fr-FR.chromium, etc)?

[Mark Larson, 2010-04-29 21:24:17]

On Thu, Apr 29, 2010 at 09:30, <jshin@chromium.org> wrote:

> On 2010/04/29 05:42:41, Mark Larson wrote:
>
>> Please rename the README to README.chromium.
>>
>
>  +cc Evan. He's working on a tool to harvest license info from third_party
>>
> stuff
>
>> and I want to make sure we support that tool here.
>>
>
>
OK. If we have a bunch of README.lang_LOCALE.txt files, let's stick with
that to be consistent.


> I'm not sure how to deal with  README files for hunspell dictionaries. At
> the
> moment, there are separate README files for each dictionary. README.ll_RR.
>  We
> didn't even bother to change the character encodings of those files (which
> are
> often in legacy encodings). We can convert them all to UTF-8 and combine
> them to
> a single README.chromium.
>
> As for LGPL, MPL, and GPL files, other dictionaries also refer to them. So,
> I
> think we have to include copies of those license files if they're not
> elsewhere
> in the tree.
>
> To Evan: combining README.ll-RR's to a single README.chromium works with
> your
> tool?  Or, is it better to have README.ll-RR.chromium (like.
> README.en-US.chromium, README.fr-FR.chromium, etc)?
>
>
>
>
> http://codereview.chromium.org/1759010/show
>

[jungshik at Google, 2010-04-29 23:29:52]

It turned out that MPL file is in third_party/hunspell (COPYING.MPL). 

I added a header (as in README.chromium files) to README_bg_BG.txt although
it'll not be used by Evan's tool.

[djevrek, 2010-05-07 09:58:27]

Can this be "enabled" for
http://code.google.com/p/chromium/issues/detail?id=43011 too ?