-
-
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
Echo translation engine doesn't work for Paratext projects #396
Comments
The most straightforward way to accomplish this is to abstract the alignment and inclusion/exclusion of data functionality from The switch to a default of |
My plan was that once we move the Machine engine to the Serval repo, we could create a library for shared engine functionality. So, yes, we should wait until we move the Machine engine to the Serval repo. |
@johnml1135 Doesn't look like the machine engine has been moved over yet; can we move this back to another release? |
Waiting on #451 |
@ddaspit, do you think it would be appropriate to move some of the logic from |
This is likely low priority.
The echo translation engine only works with text files. As Scripture Forge now uploads Paratext zip files, we are no longer able to use Echo for testing purposes.
In addition, the language checks
'https://qa.serval-api.org/api/v1/translation/engine-types/echo/languages/en
always returnisNative: false
for echo. Should these always return true, as echo supports any language?The text was updated successfully, but these errors were encountered: