The old APIs still work, but we're moving most apps to the TaskProcessing API now, so the old APIs will not be used by most providers anymore.

Do you think we need to keep both APIs in parallel then or just just migrating to the new one fine?

I would just migrate to the new one directly.

• Migrate the FakeTranslationProvider to the new task api as it is used by our cypress tests
• Migrate text initial state for translations to new task processing API
• Migrate Translate.vue component to use task procesing API when doing the API call to translate

Notes from chat with Marcel:

• So, the Translate task type defines input and output language slots: https://github.com/nextcloud/server/blob/master/lib/public/TaskProcessing/TaskTypes/TextToTextTranslate.php#L69-L85
• these are defined as enums, the value for which is defined by the provider
• getAvailableTaskTypes contains the possible values in the key inputShapeEnumValues: https://github.com/nextcloud/server/blob/master/lib/public/TaskProcessing/IManager.php#L48-L52
• integration openai implements a translate provider for example: https://github.com/nextcloud/integration_openai/blob/main/lib/TaskProcessing/TranslateProvider.php
• translate2 app will implement this
• translate app not
• deepl/libretranslate need scheduling

Hey there,

The testing app now has a task processing translation provider: OCA\Testing\TaskProcessing\FakeTranslateProvider

More details on how to run translation tasks and get the available languages in the translate section of nextcloud/assistant#114