-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Speller does not recognize words with touching full stop #3
Comments
The comma does not seem to be an Issue. Can you confirm that, @rueter ? |
Tokeniser seems to be fine. Bug report needs to be more specific. Which platform and in which software are you seeing the issue?
|
Yes, I confirm that there is no problem with commas or even question marks. Here you can see the version of the speller. |
I am using a M2 Ventura 13.0.1 There are problems with the full stop ‹.› and ‹...› touching a previous word. |
I can report the same as Jack, for sme on my LO, word + "." gives error message, whereas word + "…" does not. This behaviour has been there for some time. The Mac-internal speller (e.g. in Pages) does not display the same error, here everything works. I have Ventura as well, and new LO. My speller versions: |
Actually, the only problem I have is with the word + "." in myv giving an error message. There is no problem with U+2026 Horizontal elipsis; the myv texts literally have three full stops U+002E. Hence, this is the only problem, and it may be aligned with Trond's sme problem. |
Yeah, the second I hear LibreOffice I know it's just sending the wrong garbage to DivvunSpell. Will look into it soon. |
The Erzya speller does not recognize words with touching full stop.
This may have something to do with Cyrillic-letter range.
Here full stops, both ‹.› and ‹...› following a word will cause it to not be recognized.
If a space is inserted, the word form is recognized.
The text was updated successfully, but these errors were encountered: