• Resolved photokitchen

    (@photokitchen)


    Hello,

    I translated all myself and with copy paste the translated language (English to Dutch) I paste into the field for Dutch, then I saved. All looks good, however, some days later, in the translated Dutch page, partly is back again in English. If I go again to “translate this” the memory of the translation is there, I just must click on it to get it in the field again. Then saved again. So, this doesn’t make sense to re-translate all again or updating the page with the memory translation.

    Regards,

    Steven

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support Alex

    (@alexcozmoslabs)

    Any change of the original string will invalidate the front-end translation as they are directional. 

    This is how our plugin works because we save each translation in the database. Every string has a corresponding translation. If you change the original string, basically, you create a new string that will need to be translated.

    To facilitate translation retrieval we implemented the Translation Memory* feature.
    For example, if you have a string in your default language that is translated and you go in and modify that string, the translations for it won’t appear anymore at the front-end level but will continue to exist in wp_trp_* tables from your database. After, if you go to the translation interface and select that string, the Translation Memory feature will show you translation suggestions for that string (based on other strings that you have translated, even ones that don’t appear anymore in the front-end; so most likely, you will see the older translation as the first suggestion).

    *The translation memory is approximate, based on what strings are in the database. It’s possible sometimes that doesn’t work 100%.

    However, we offer support now for editing in a way that if the changes on the original string do not exceed more than 5% of the entire string, the translations remain assigned to that string. This feature requires enabling the Automatic Translation Memory feature in TP Settings –> Advanced tab –> Miscellaneous options and is not applicable for translation blocks (in case those are edited, the translation is not kept).

    Thread Starter photokitchen

    (@photokitchen)

    Sorry but keep it simple! Why are making it more complicated as it is? The orginally text is English and translated into Dutch and German by myself as automatic translations aren’t working. Then I save the translated part and it should remain there till I change it MYSELF. Why are you making it more complicated as it is? I am a photographer and taking pictures, not the whole time to be working with this kind of stuff, this must be easier.

    Plugin Support Alex

    (@alexcozmoslabs)

    Our plugin is a based string one, meaning if you change the original string, you create a new one that requires a translation.

    Thread Starter photokitchen

    (@photokitchen)

    Yes but that isn’t the point. Of course I understand if I chnage th orginal part I have to update the translation. And as you wrote, 5% change will keep the translated part remaining as before, but it didn’t.

    Plugin Support Alex

    (@alexcozmoslabs)

    Have you activated first the Automatic Translation Memory option? It will nto work without it.
    Maybe you can tell if about what string we are talking about and what changes did you make?

    Thread Starter photokitchen

    (@photokitchen)

    Of course not, as it says automatic translation. If it necessary, why is there anyway an option On/Off? One string was not changed in the orginal, only in the translation. A day later the translation was gone.

    Thread Starter photokitchen

    (@photokitchen)

    Even with the API Key it doesn’t work: API Key Error.

    Plugin Support Alex

    (@alexcozmoslabs)

    The API key need to be generated on Google platform. Our plugin automatic translation is based on Google API Key, which means you need a working API key generated on Google platform in order to translate automatically your content with TranslatePress.
    We have documentation steps on how to set up the Google Translate API key and how to add quotas to never exceed a certain threshold: 
    https://translatepress.com/docs/settings/generate-google-api-key/.

    Could you please replicate the supposed issue (invalidation of the translation) on a testing page and let me know the exact steps you followed in this process? If it’s a bug, our dev team is ready to intervene.

    We apologize if you had an unpleasant experience. We have no interest in leaving the user in doubt. We try to help him as much as possible.
    If it’s not too much to ask, would you consider temporarily adjusting your review? We believe this might better represent the ongoing nature of our support process.
    After we resolve the issue (if it is an issue/bug), we’d appreciate if you could update your review based on the overall experience, as it provides a more comprehensive understanding for others who might be considering our plugin.

    Thread Starter photokitchen

    (@photokitchen)

    Indeed I followed your description mentioned on your website yesterday. I set up a Google cloud account and created an API Key, after copy-paste it was green and after saving an error showed up. I just tried this so-called free translation test account, however it`s only for a certain period. Then I tried a new project, but I need again to answer X-questions and I don’t want all this and certainly, not given my CC credentials to Google. It is very easy for me, I don’t want to have a Google cloud account as I will never use it. Besides my job is something else and don’t want to deal all day with all this Google shit. I translated all manually, which is always better than using Google translation, after X-times of saving and checking again it works. So, automatic translation I off again and will remain off.

    Plugin Support Alex

    (@alexcozmoslabs)

    What I recommended the first time in this thread was using the option of Automatic Translation Memory, which has nothing to do with the automatic translation feature from Google. The Automatic Translation Memory basically enables our system to retain the previous translation of a string if this is changed. So I guess you misunderstood me first.
    As specified in the documentation, the translation memory works if the original string (the string from the default language) does not undergo transformations greater than 5% of it. In other words, the similarity between the old string and the new one (the modified one) must be at least 95% for the automatic memory to save/deliver the translation for the new string automatically.

    Please understand that our plugin is a string-based one. We are not creating new pages for translated versions. You can translate string by string and the translation is then saved into your site database. TranslatePress is focused on a visual front-end translation approach, which is fast and gives you context.

    Considering the clarifications, we would appreciate it if you would take them into account when modifying the review left.

    • This reply was modified 1 month, 3 weeks ago by Alex.
    Plugin Author Anghel Emanuel

    (@anghelemanuel99)

    Hello there,

    Since 5 days have already passed without getting any reply from you, I will mark this thread as “Resolved”.

    Have a great day!

    Kind Regards,

Viewing 11 replies - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.