https://bugs.documentfoundation.org/show_bug.cgi?id=144915

Stéphane Guillou (stragu) <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW
             Blocks|                            |108728
                 CC|                            |stephane.guillou@libreoffic
                   |                            |e.org
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=15
                   |                            |2110
            Summary|problem with vocabulary     |"The dictionary is already
                   |replenishment               |full" when adding new word
                   |                            |to dictionary

--- Comment #3 from Stéphane Guillou (stragu) 
<[email protected]> ---
I assume the string is "The dictionary is already full" in English.

It is defined here:
https://opengrok.libreoffice.org/xref/core/include/editeng/editrids.hrc?r=f7f0f399#308
And it is only used here:
https://opengrok.libreoffice.org/xref/core/editeng/source/misc/unolingu.cxx?r=91fef4a4#738

This is triggered if the dictionary has 30,000 or more entries.
Size is checked in DictionaryNeo::isFull() here:
https://opengrok.libreoffice.org/xref/core/linguistic/source/dicimp.cxx?r=3d236177#920

DIC_MAX_ENTRIES limit of 30,000 is defined here:
https://opengrok.libreoffice.org/xref/core/linguistic/source/dicimp.hxx?r=fd3888c6&fi=DIC_MAX_ENTRIES#33

Not sure why this hard limit. I don't see it documented:
https://help.libreoffice.org/7.4/en-US/text/shared/optionen/01010400.html

Any reason for this hard 30,000 limit?
Should this report be changed into a documentation issue?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108728
[Bug 108728] [META] Dictionaries bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to