-
Improvement
-
Resolution: Fixed
-
None
-
Emptyshow more show less
Hi Marc,
I hope you are doing well.
There was a gap in the Globalese API which has now been addressed.
In short, changed engines were always dubious: if they had been trained before, they could be used for translation, but if not, there was actually no engine yet. I think you also pointed this out at one time.
We have remediated that by introducing a "ready" Boolean for every engine. If it comes back as true, the engine is ready for translation.
Please see the updated API docs here:
https://app.swaggerhub.com/apis/globalese/Globalese/2.1
(We didn't change the API version.)
Would you be able to adapt the connector to this change, i.e. instead of listing engines whose status is "trained", list engines whose "ready" property is true?
Kind regards,
Greg
[TRANSLATE-1533] Switch API value, that is checked to know, if Globalese engine is available
Workflow | Original: MittagQI Workflow [ 27798 ] | New: MittagQI Workflow with Peer [ 35583 ] |
Status | Original: Test Ready [ 10005 ] | New: Done [ 10000 ] |
Fix Version/s | New: translate5 - 3.0.2 [ 10608 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Test Ready [ 10005 ] |
Status | Original: Selected for Development [ 10100 ] | New: In Progress [ 3 ] |
Rank | New: Ranked higher |
Status | Original: Open [ 10002 ] | New: Selected for Development [ 10100 ] |