Thanks for your reply. I had a look at the duplicated form "Create User and Project (1)" in the ATE editor. However, I don't see any translations there as I would expect reading your text about translation memory.
What I now tried was the following: In the string translations I exported the .po file from the initial form, fixed a few errors in there, renamed it to suit the duplicated form and imported it for the new duplicated form. That works for the front end but I know expect to see the translations set in the string translations also in the ATE. However there the fields are still blank. How can I get the translations set in the string translations in the ATE editor?
Currently, we don't support importing translation to the translation memory on our server. You don't see the translation content in ATE because the form content has not been translated in ATE before.
You can copy the translation from .po file manually when translating the form in ATE. Generally, strings translated on your site won't be available in ATE.
Thanks Long. Just to understand the ATE way of translating properly: If the clients don't manage to translate all the fields in one go (or in our case some forms are populated dynamically therefore also change), the already translated strings should be already visible correct? I tested this (screenshots attached) and can't see the translated labels in the front end.
the already translated strings should be already visible correct? Ican't see the translated labels in the front end.
No, WPML only displays the completed translation in the frontend. If you translate some strings/sentences in the Advanced Translation Editor, it will be saved to the translation memory and available there. You can continue translating other sentences in the future.
After you click on the Complete button in ATE, the translated sentence will be displayed in the frontend.
Hi Long, as I said we have a dynamic field in this form (a select field with a lot of options). These options constantly get updated by users filling out these forms and adding more options. If I understand you correctly that would lead to a not fully translated form not translated and therefore the translations wouldn't show in the front end is that correct?
Plus second question: Does the same apply for xliff fields? As in if not fully translated the translation wouldn't show?
If I understand you correctly that would lead to a not fully translated form not translated and therefore the translations wouldn't show in the front end is that correct?
Yes, in ATE, if you only translate a part of the form content, the translation won't be displayed in the frontend.
Does the same apply for xliff fields? As in if not fully translated the translation wouldn't show?
If you export the XLIFF file from WPML > Translations and translate the form content (a part) > Import it to your site, the translation will be displayed in the frontend and the rest will be displayed in the original language. It works like you translate the form in String Translation.
But please notice that, if you use XLIFF or PO file to translate the form content, that means you are translating content on your site and there isn't a way to import the translation to ATE.
Looking forward to your reply.
Thanks
The topic ‘[Closed] How can I get the translations set in the string translations in the ATE editor?’ is closed to new replies.
