#7 Allow to install dictionaries separately

Petr Mladek

The size of the extension, version 0.9.9 is about 14MB. It think that the framework takes only 2MB. The rest are dictionaries. We might expect more and more dictionaries in the future.

Do you have any plans to distribute the dictionaries separately as optional extensions?


I started to pack the dictionaries separately for openSUSE and got the following RPMs:

2.0M OpenOffice_org-LanguageTool-0.9.7-1.noarch.rpm
4.2M OpenOffice_org-LanguageTool-cs-0.9.7-1.noarch.rpm
1.1M OpenOffice_org-LanguageTool-de-0.9.7-1.noarch.rpm
1.6M OpenOffice_org-LanguageTool-en-0.9.7-1.noarch.rpm
332K OpenOffice_org-LanguageTool-es-0.9.7-1.noarch.rpm
299K OpenOffice_org-LanguageTool-fr-0.9.7-1.noarch.rpm
252K OpenOffice_org-LanguageTool-it-0.9.7-1.noarch.rpm
1.6M OpenOffice_org-LanguageTool-nl-0.9.7-1.noarch.rpm
2.5M OpenOffice_org-LanguageTool-pl-0.9.7-1.noarch.rpm
395K OpenOffice_org-LanguageTool-ro-0.9.7-1.noarch.rpm
999K OpenOffice_org-LanguageTool-ru-0.9.7-1.noarch.rpm
265K OpenOffice_org-LanguageTool-sv-0.9.7-1.noarch.rpm

The lang-specific packages include only the .dict and .info files. In addition, I use the attached JLanguageTool-0.9.7-package-dicts-separately.diff to disable the non-installed dictionaries in OOo.

It is a dirty hack. I am sure that you would find/suggest a more clear solution.


  • Marcin Miłkowski

    Hi Petr, yes, this is a feature request that seems to recur. Your hack is actually quite dirty and it could break OpenOffice.org - you need also to automatically change description.xml to adjust the language list to the ones contained in the package.

    There are more things which are language-specific:

    - rule files (grammar.xml files and all other language-specific files that are needed for Java rules);
    - Java code (we conventionally language codes to show that some parts are language-specific), and all Java code related to languages should be loaded by reflection (we have reflection classes already).

    Moreover, in case of the .oxt distribution, you should make sure that if the user wants to use certain language, he will receive a link, and somehow new parts will be merged with the existing install. We don't know if that's possible to merge using OOo infrastructure and we don't want to install multiple copies of the same infrastructure for all languages (it's enough to have two "separate" extensions installed to have some problems as only one will be active in OOo - we make sure that there is only one checker class - so only one language would be actually supported). So you would need to see how merging would be made possible.

    As these things are time-consuming, we are not planning to implement them right now. Feel free to contribute code if you think that 16 MB is unbearable for you, but it's still quite tiny if you look at how cheap is disk space today.

    (BTW, distributing 0.9.7 is a BAD idea, it's very buggy and using OOo dialog window can be hard with it).

  • Marcin Miłkowski

    • milestone: 899267 -->
    • assigned_to: milek_pl --> nobody
    • labels: 1169513 -->
    • status: open --> pending-accepted
  • SourceForge Robot

    • status: pending-accepted --> closed-accepted
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

  • Marcin Miłkowski

    • status: closed-accepted --> open
  • Marcin Miłkowski

    reopening, of course

    btw, we have first ideas how to implement it :)

    stay tuned on our mailing list

  • Daniel Naber

    Daniel Naber - 2014-09-23

    Nobody has been working on this, although it's still an issue. If someone wants to work on it, feel free to open a new issue at github.

  • Daniel Naber

    Daniel Naber - 2014-09-23
    • status: open --> closed
    • Group: --> 2.2

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks