[IMPLEMENTED] Support more languages for auto-translation

aiwfiu · December 17, 2020, 11:52pm

I have…

[ ] Read the following guideline: https://docs.squidex.io/01-getting-started/installation/troubleshooting-and-support. I understand that my support request might get deleted if I do not follow the guideline.

I’m submitting a…

[ ] Regression (a behavior that stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Documentation issue or request

Current behavior

The following languages are not automatically translated: Arabic (any type of Arabic), Hebrew (any type of Hebrew), Korean (any type of Korean), Thai (any type of Thai).

Expected behavior

When clicking on the auto-translate button, the languages mentioned above should have a translated value from the master field

Minimal reproduction of the problem

Add the languages mentioned above to the project (from the settings panel)
In Scheme, add an “input” type of field to the scheme
In Content, add a post and enter “Test” in the field, and click on “All Languages”
Click on Auto-translate
The fields of the languages mentioned above won’t receive an auto-translte value

Environment

[ ] Self hosted with docker
[ ] Self hosted with IIS
[ ] Self hosted with other version
[x ] Cloud version

Version: Cloud version
Browser:

[ ] Chrome (desktop)
[ ] Chrome (Android)
[ ] Chrome (iOS)
[ ] Firefox
[x] Safari (desktop)
[ ] Safari (iOS)
[ ] IE
[ ] Edge

Others:

Sebastian · December 18, 2020, 8:54am

Not all languages are supported by the translation provider. It is not a bug…

aiwfiu · December 18, 2020, 7:36pm

Thanks! Is the translation provider is Google? Is there any option to change the provider or support more languages?

Sebastian · December 18, 2020, 7:52pm

At the moment it is deepl: https://www.deepl.com

aiwfiu · December 18, 2020, 7:54pm

Thanks. DeepL is good, although a bit limited compared to Google Translate’s API.

Sebastian · December 18, 2020, 7:55pm

Yes, but when I started with it the pricing was better. I can also add a second provider …

aiwfiu · December 18, 2020, 8:05pm

That would be awesome, if possible. If there’s an additional cost, maybe it can be added to the usage costs somehow?

Sebastian · December 21, 2020, 12:00pm

I have implemented a new system that supports multiple providers: https://github.com/Squidex/text/tree/master/Squidex.Text/Translations

aiwfiu · December 21, 2020, 5:15pm

Thank you, @Sebastian! Is that for self-hosted only or for the cloud one too? We’re using the cloud-based version.

Sebastian · December 21, 2020, 5:46pm

Also for cloud, but it was not deployed…now it is.

aiwfiu · December 21, 2020, 5:59pm

Thank you! And is it something we can set from the user-interface or from the back-end? (sorry for all the questions - I’m not the technical person)

Sebastian · December 21, 2020, 6:06pm

I have to configure something and then it should just work.

aiwfiu · December 21, 2020, 6:07pm

Awesome! Thank you so much for your prompt support!

Sebastian · December 21, 2020, 6:13pm

You can try it again…

aiwfiu · December 21, 2020, 6:14pm

so so cool! It works!

Thank you, this is really great!

aiwfiu · December 21, 2020, 10:01pm

Question about “Rich Text” field translation.

I understand the reason not to place an auto-translate button for that field because of the issues it can cause to the HTML structure. With that said, I tested it by:

Copying the source code of the rich text field with many different type of strings
Pasting in a “Text Field” which supports localization, and all languages were translated perfectly, except for Arabic and Hebrew (RTL), which makes sense, but not something that should prevent us from adjusting the text in those languages manually

Is there any chance that the “Rich Text” field will support the auto-translate feature? We find this feature one of the best Squidex advantages over other CMS products out there (beyond other amazing features).

Thanks!

!
!

Sebastian · December 22, 2020, 10:06am

Yes, I am planning to work on this. I would like to support markdown and html as well, but it is challenging and I expect the first versions to be buggy.

aiwfiu · December 22, 2020, 3:16pm

I assume 90% of the time it will be fine, so if that’s “buggy” - I think it will work out

Thank you!

Sebastian · December 22, 2020, 4:25pm

I already give up on this. It is super complicated.

My naïve approach was to start with markdown and to translate texts,e.g. “# Book” becomes “# Buch” in german. But when you have inline texts with formatting, it is a nightmare, for example when you have a bold text somewhere like “Hello ** friend **” friend, because you cannot isolate the different parts isolated from each other, because they build a sentence.

The only option that would somehow work is a conversion from html or markdown to text and to translate it then. But all the formatting is lost.

aiwfiu · December 22, 2020, 5:04pm

From what I saw, the “Text Filed” field works without any issues (after pasting the HTML source code into it), except for RTL languages. I wonder what is the difference?

In this example it’s: Hello World Hello Again