• By allowing users to translate what they see at the front-end rather than going digging for strings in the back-end you can very quickly create usable translations of your site that the users actually see.

    What’s less clear is what happens when the underlying source content changes, and how you can go about tracking those changes across languages. I’m yet to find the ideal workflow where new languages are translated using machine translation like DeepL, but flagged as “fuzzy” until clarified by a human translator (ideally with a todo list for same by language).

Viewing 1 replies (of 1 total)
  • Plugin Support Alex

    (@alexcozmoslabs)

    Thank you for your feedback.

    You need to know that we take into account the suggestions on how we can improve the translator review on translations made with TranslatePress. For the moment, we are just counting the interests of our users in a feature like this. As soon will be a major demand for it from our community, we will surely try to find a feasible implementation.

Viewing 1 replies (of 1 total)
  • The topic ‘Smart approach to translation’ is closed to new replies.