Wrong translations with translatepress

  • Resolved ndrw

    (@ndrw)


    3 years, 8 months ago

    Hello,
    thank you for the great plugin!

    I just have a problem with translations. My site has a few languages that are translated automatically using TranslatePress and google translate.

    I can verify English and Polish versions, and the Polish version ONLY on the “Cookie Policy (EU)” page is translated incorrectly. E.g. the word “cookie”, which on the Polish version should be kept “cookie” is translated into the literal meaning of the word (“ciasteczko”). Some paragraphs in Polish do not make any sense.

    I looked deeper into the problem:
    1. translate press keeps the original strings in a table “trp_original_strings”
    2. each string in this table is only in its original version – i.e. on my website in English, as this is the default language
    3. However, strings from the “Cookie Policy (EU)” page (and only from this page) occur multiple times in the trp_original_strings table – each version in a different language. Translate Press thinks that each of these strings is an original string. It does not have any idea that Complianz has already translated these strings. Furthermore – Translate Press thinks that each of these strings is in English.
    4. The result is that in tables trp_dictionary_en_us_ + language code (e.g. trp_dictionary_en_us_pl_pl, etc) there are many translations from the “original” strings contained in the trp_original_strings table, to the translated version.

    It is no wander then why the Polish translation (and probably all other translations) does not make any sense:
    1. Complainz makes the polish version of the page and let’s Translate Press save it in the original strings table
    2. Translate Press upon switiching the language in the front-end tries to translate the Complianz-made Polish text, thinking it is an English text, to Polish again.

    For now I try to exclude the “Cookie Policy (EU)” page from being translated by Translate Press, but this does not seem to work either. I will try cleaning the database – we will see.

    However – I think there should be a switch in Complianz wether I would like to use Complianz translations or relay on my translation pplugin.

    Do you see any solution to this?

    Thank you

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter ndrw

    (@ndrw)

    Just to update – excluding cookie policy from translation by trranslatepress did not work.
    To have a sensible cookie policy in other languages I manually copied-over the double-translated version of translatepress to the complianz version.

    Just to retierate the problem:
    1. Normally Translate Press takes the original and translates it to other languages, like so:
    original (English, in trp_original_strings) -> translated from original (in trp_dictionary_en_us_xx)

    2. With Complianz the problem is double-translation:

    original (english, trp_original_strings) -> Complianz translation (other language, trp_original_strings) -> translated from Complianz translation (treated as English, but this is not English, trp_dictionary_en_us_xx)

    Thank you

    Plugin Contributor jarnovos

    (@jarnovos)

    Hello @ndrw,

    Strange issue indeed, but I must admit that I have don’t have much knowledge about how TranslatePress handles translations. I do know that Complianz makes the translations available in the same way as we do for every other translation plugin, so I can’t really explain the difference in what TranslatePress does, compared to plugins like PolyLang or WPML.

    Translations are fetched conform WordPress guidelines, from https://translate.www.ads-software.com/projects/wp-plugins/complianz-gdpr. As can be seen on this page, we have indeed not translated the word “Cookie” as stated in your post. Especially in the case of Legal Documents, it is not advisable to use machine translations. I know that plugins such as WPML and PolyLang adhere to the WordPress guidelines as well. In the case where you have issues with TranslatePress, I think contacting TranslatePress for support would be the most helpful in this case.

    As we speak, a translator is working to get the Polish translations back up to 100%. That would fully negate the need for machine translations for Polish.

    Hope this helps/clarifies.
    Kind regards,
    Jarno

    Thread Starter ndrw

    (@ndrw)

    Thank you for your answer.
    It seems to me that TranslatePress uses a different approach to translations than WPML or other plugins. So Complianz should not know that my website is multilingual.
    Then I would be able to verify the machine translation, which would be better still than what results from a double-translation of translation.
    OK – I will leave it as it is right now.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Wrong translations with translatepress’ is closed to new replies.