You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Break patters at the beginning and the end of the word shouldn't be considered in the recursive calls. IMO, they should work on the whole word and not on part of it. For example, given the following break patterns
BREAK 2
BREAK ^+
BREAK -
and the word abc-+xyz, the algorithm will first check the whole word, then it will split it to abc and +xyz, and then +xyz will be trimmed to xyz because of the break pattern BREAK ^+. This is considered a break pattern only for the beginning of the word, and should remain as such. This behavior also exists in Hunspell, and I think this is by accident and it should be fixed. I need to retest and reanalyze Hunspell code for break patterns, but I'm pretty sure it works this way and it is by accident.
Break patters at the beginning and the end of the word shouldn't be considered in the recursive calls. IMO, they should work on the whole word and not on part of it. For example, given the following break patterns
and the word
abc-+xyz
, the algorithm will first check the whole word, then it will split it toabc
and+xyz
, and then+xyz
will be trimmed toxyz
because of the break patternBREAK ^+
. This is considered a break pattern only for the beginning of the word, and should remain as such. This behavior also exists in Hunspell, and I think this is by accident and it should be fixed. I need to retest and reanalyze Hunspell code for break patterns, but I'm pretty sure it works this way and it is by accident.Originally posted by @dimztimz in #85 (comment)
The text was updated successfully, but these errors were encountered: