-
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
It seems grc versions are not updated on the server #71
Comments
This bug is really about how and when to update the grammar checker |
While waiting, we should document how to inspect the dates for the grammarcheckers. |
After update on the server (today), I now check as describet above: I add the following sentence Hann skal læra at virða tær skyldur og tey rættindi, sum fólkaræði byggir á, har ímillum teir sáttmálar, ið Sameindu Tjóðir hava samtykt í sambandi við barnarættindi og mannarættindi annars. and send it to checkng. Now (contrary to yesterday) the setence comes out as true negative. The update thus is done, and the new version works. The bug should not be closed, though: What happened today was that 3 languages were manually updated (fo.zcheck, nb, smn). The other languages were not updated, and the automatic update procedure is also not in place. Also, the documentation for how to check for dates (either via easter eggs or via inspecting the dates on pahkat.uit.no) is not in place. The good news is that 3 languages are updated, so that the last 9 months of work is available for the language communities. Thanks! |
So, let us partition the problem: if I understand correctly, we need two things:
There should be no reason for waiting months for the second point, it seems like a five-minute-fix, at most. The issue thus seems to have stranded at the first point. I do not whether speller update is linked to the |
I guess giellalt/lang-smj#109 (comment) is the same issue. The version running on the server is from before September 2019 ( giellalt/lang-smj@9e9a73a removed "msyn thingy" from errors.xml), that's over 5 years ago! @bbqsrc what's the procedure for getting these packages updated? |
That is very strange, and points to other issues. The That is, there is something strange going on. |
About the procedure: the present procedure goes as follows:
@bbqsrc is working on an update to the whole Páhkat ecosystem that will include automatic releases of grammar checkers, the same way we do speller releases now (a version tag in a specific format). This update will also cover the api server, and thus make the api server update automatically upon stable/tagged releases. |
There is also a possibility that the |
See my comments in giellalt/lang-smj#109 - I am not able to replicate the issue with |
errors.xml was #98 so not relevant for this.
any reason not to just use the one built by Tino's packaging? |
No, not really, I just find it more convenient to build locally (=how do I get the one built by Tino?). |
well, any ubuntu machine doing @TinoDidriksen is there a nightly-data script for osx? Feel like I've heard of one once. |
There is https://apertium.projectjj.com/osx/install-nightly-data.sh invoked as e.g. Rather simple script that downloads the .deb file from https://apertium.projectjj.com/osx/nightly/data.php and unpacks it, with some path adjusting for .mode files. |
For fao grc, the following sentence:
gets a correction
samtykt
tosamtykja
, and the error message "Det ser ut til at verbet ditt ikkje skulle ende på ð.", corresponding to the tag &msyn-sup-inf. The problem is that this (false) alarm cannot be reproduced on the command line. The offending rule was removed from thegrammarchecker.cg3
file on february 6th.The conclusion is thus that MS Word accesses an online grammar version dating from before February 6th. I do not know whether this holds for fao only, or whether it goes for all the online grammars, but it should be looked into. The fao grc is in use by a whole language community (the largest of the ones we serve) and the issue should thus get some priority. If the error carries over to the other grc versions the issue is even worse. Due to bug #70, I have only tested on MS Word.
The text was updated successfully, but these errors were encountered: