-
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
Soft hyphens in text break grammar API #23
Comments
Turns out the problem is soft hyphens in the text sent from Word. So the categorisation above is probably invalid, and just a happy coincidence of the test data used. To trigger the error, use the following text - it should contain two soft hyphens:
|
Seems the error is in libdivvun - @unhammer could you have a look? |
The issue this time was the character |
INFORMATION SEPARATOR ONE? |
Everyone's favourite codepoint! The input was |
What is libdivvun doing wrong? I get
from the command line with newest giella-sme-speller (that hl-nonprinting is just a script to sed \xad into a dash and EOL into ⁋). |
@snomos has conflated two issues. the |
– should we be removing it from input, or are we somehow introducing \x1f's, or am I not reproducing the issue correctly here? (Some "expected this, but got that" examples would be nice ;)) |
Sorry I am trying to go on vacation, haha. Error was |
Might help with divvun/divvun-gramcheck-web#23 https://tools.ietf.org/html/rfc7159 says "escape U+0000 through U+001F", we were escaping up to but not including 1F, simple fix :)
There was a bug in libdivvun – that character should've been escaped according to the json spec. Fixed now, hopefully might help with this issue. |
This seems to be fixed, at least not causing any trouble in neither Word nor GDocs. Even
(containing two soft hyphens) seems to be fixed. Closing. |
I am not able to get GramDivvun to work in MS Word (the local app) when using the UiT account. It can be installed, it loads, and looks the way it should in the initial screen. But when clicking "Check", it almost immediately dies with the following errors in the console:
Screenshot of the same:
I have tested various setups, and most work, but not this one. The ones I have tested are:
The Safari+UiT problem manifests differently, and thus seems to be a different issue, and can be easily worked around by using another browser. So this bug report targets the Office 2016 locally installed app issue only.
The text was updated successfully, but these errors were encountered: