-
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
GDocs/MS Word extensions mix error with identical substring in earlier word #18
Comments
GramDivvun marks the misspelling "vátti" and gives several suggestions, and the right context: "Lea, vátti dat" Here's the original text:
|
giellalt/lang-sme#45 shows that this is not restricted to GDocs. |
Trying to figure out I can't see any problems in the back-end:
Start indices of "gávnnat" are 242 and 341; our first error index is at 397. What methods do the gdocs/word extensions use to find the error to underline @bbqsrc ? |
My initial hunch is that this bug is in the MS Office/GDocs plugins, and not in the backend. Thus @bbqsrc et all should look into it. |
Here's another example, from SMA:
The actual error is correctly captured using the command line tool: echo 'Naan båeries saemieh Raarvihkesne guhth leah gïelem noerebaeleste \
lïereme, leah ennje væjkele soptsestidh, mohte eah leah man gallesh, eevre \
goh dejtie maahta aktene gïetesne ryöknedh.' \
| divvun-checker -a tools/grammarcheckers/sma.zcheck as seen in the output: {
"errs": [
[
"eah",
113,
116,
"typo",
"\"eah\"-baakoe vååjnoe båajhtode tjaalasovveme.",
[
"ih"
],
"\"eah\"-baakoe båajhtode tjaalasovveme"
]
],
"text": "Naan båeries saemieh Raarvihkesne guhth leah gïelem noerebaeleste lïereme, leah ennje væjkele soptsestidh, mohte eah leah man gallesh, eevre goh dejtie maahta aktene gïetesne ryöknedh."
} If the same string is checked in GDocs or Word, the substring @zoomix could you forward this to whomever is most appropriate? This bug is very annoying to users, and should ble fixed ASAP. |
This is now fixed in the latest server update, closing. |
The text was updated successfully, but these errors were encountered: