-
Notifications
You must be signed in to change notification settings - Fork 28
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
The French to Arpitan translator is not working properly on the website #108
Comments
apertium/apertium-apy#17 would work around the issue, though fixing the actual problem would be better. Your null-flush vs. non-null-flush testcase showed differences already in morphology, so that's the place to start. |
The problem with null-flush vs. non-null-flush testcase is that we have the same odd results with null-flush for e.g. fra-oci, but the fra-oci pair is working well. In fact, it seems logical to have the same results in the morph mode for fra-oci and fra-frp because if there is something odd in the French morphological analyser, the problem very probably should be found in any translator from French. But they are all working, except fra-frp. So I can't understand your conclusion. To be more precise, in fra-oci I am executing this:
And I am getting this:
This seemingly is not a problem for fra-oci. Why would it cause the problem in fra-frp? |
apertium/apertium-apy#17 is now worked around and deployed on beta, and seems to be working exactly as desired. |
Yes, it is!! Hopefully, it can be deployed soon in the "real" web. |
The recently released French to Arpitan translator is not working properly on the website (www.apertium.org). If one puts a text and tries to translate it, most of the time he/she receives a blank page or a previous translation into Arpitan. Instead, if the same text is translated into, for instance, Spanish or Occitan, one quickly gets the correct translation into the given language. The translation from Arpitan into French seems to work properly.
The result of this issue is that, for some unknown reason, the translator is not reliable and very hard to use.
The text was updated successfully, but these errors were encountered: