Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • 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.

    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

Viewing 2 replies - 1 through 2 (of 2 total)