https://bugs.documentfoundation.org/show_bug.cgi?id=136306
Lars Jødal <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #10 from Lars Jødal <[email protected]> --- I do not read Dutch, but as I understand the discussion, the problem derives from compounding of words that in themselves are correct words, but which become gibberish when compounded. Right? This is not the fault of Hunspell or LibreOffice, but it is still something we would like to handle. Here follows some tips from the Danish dictionary. Danish has a similar problem: Very many correct possibilities of compounding, but also very many possibilities of nonsense within the normal compound rules. To minimize the problem, the Danish dictionary has for many years (since 2012) switched off compounded words from suggestions by this Hunspell option (in the .aff file): MAXCPDSUGS 0 This instructs Hunspell to give at most zero (i.e., none) compound words in the list of suggestions. As an example, "kaffe" (coffee) and "klaver" (piano) are both in the dictonary, and "kaffe" is marked for compounding with no added letters. If the user writes "kaffeklaver" (coffee piano), then it is accepted as a possible word, but "kaffeklaver" will not be suggested by the dictionary. The quite common compound word "kaffebønne" (coffee bean) is in the dictionary, so "kaffebønne" can be suggested, not a as a compound word, but as word in itself. More recently, as a current developer of the Danish dictionary, I have myself added this option to the .aff file: CHECKCOMPOUNDREP This option asks Hunspell to check a possible compound word against the REP list of common mistakes (as defined in the .aff file). If a possible compounding differs only by a common mistake from a word that is already in the dictionary (.dic file), then the word is rejected, even though it follows the compound rules. Adding this rule will reduce the number of nonsense-compoundings that are recognized. It will also once in a while weed out a valid compound word, but these valid words can be added to the dictionary. I.e., if you are a dictionary developer, it is worth checking the dictionary on a group of texts after adding the CHECKCOMPOUNDREP option, to catch common words that was earlier recognized as compounds, but which should better be added as dictionary words. As for the new LibreOffice option, I consider it a valuable possibility to give the normal user the possibility to disallow compounding. Dictionary developers like myself do our best to make good dictionary, including compounding, but it will always be the case that some users will have different needs than another, so adding this choice to the individual user is a sure bonus. Thanks to László Németh for this option. -- You are receiving this mail because: You are the assignee for the bug.
