Allowing for manual translations

[Pfenya]

First off: thank you for the great plugin that works amazingly well with little fiddling!

now for a (perhaps) unusual request for something that can be automated so well - but could the plugin theoretically also be used for creating a pipeline for manual translations? On the project i am working on the question came up of having native speakers do the translations - and I have been unable to find a good translation and/or import & export plugin to fit this manual workflow.
Right now we use this plugin and DeepL - which works really well - i wonder if i can add a manual option though, especially for the languages that DeepL doesn't support right now?

I assume i would need to add a custom provider (can two be defined btw?) but could it handle the async nature of this?

Thanks
Jenni

[layaxx]

Hi @Pfenya

can two be defined btw?

No, currently only one single translation provider can be defined/used.

having native speakers do the translations

I am not really sure how the workflow would be here. Is there anything preventing the translators from doing the translation right in strapi, without this plugin? (i.e. like this https://docs-v4.strapi.io/user-docs/content-manager/translating-content)

[Pfenya]

Thank you for the quick reply @layaxx!

I am not really sure how the workflow would be here. Is there anything preventing the translators from doing the translation right in strapi, without this plugin?

the reasoning is that this would most likely be handled by users who usually have nothing to do with the website, so they would need a lengthy intro to how the content is being handled and what it means to be able to work within the system (plus access to the content). Therefore the question was raised if we can simply output the texts to be translated and give it to them as a csv file or similar and get the translated texts back and get them into the system.

I think after having tried the DeepL integration that will cover most of our cases now with the native speakers going over that and giving feedback (makes this faster also). But will still need to figure out what to do about languages not supported by DeepL.

[layaxx]

Therefore the question was raised if we can simply output the texts to be translated and give it to them as a csv file or similar and get the translated texts back and get them into the system.

Ok, I understand the intended workflow, but I think some export plugin would be better suited for this task.

But will still need to figure out what to do about languages not supported by DeepL.

You can check if there is another provider that supports the language: https://www.npmjs.com/search?q=strapi-provider-translate

However, you would need to use this provider for all translations, since multiple providers are not supported.

[sargreal]

I had definitely thought about this at some point, but it probably requires some large changes to how providers work currently (if supported directly).

I had seen that the localazy plugin does basically that, but it currently creates a vendor lockin.

I actually think however that the csv export option could be viable, since we are already doing the work of finding all of the content fields that should be translated. importing should then also be rather simple to implement. Only that you can’t change the schema in the meantime.