Translating more effectively

  • Resolved alyabee

    (@alyabee)


    3 years ago

    I think TranslatePress has 2 big issues which I cannot find a workaround.

    1) Flexibility
    Mostly we translate big paragraphs for products description. This includes numbers that may need to be changed in a future date. When a single letter changes in original phrase, all translations disappear. We need to copy old translations for all languages to the new one. This is a huge problem. I wish there was an easy way to assign a custom id to the translation, so the original translation could be changed easily.

    2) Garbage collection
    Tens of old products are deleted periodically from the system, which leaves behind a big garbage of translated chunks of paragraphs. In couple of years, the database will be really unmaintainable. If there was a simple table which we can search and delete translations, preferably by assigned custom id in the 1st matter, this would be really easy and clean. We don’t want to mess with tables using phpmyadmin, I believe no worker would be able to do it without mistake in the long term.

    3) Bonus: Let us translate inputs and textareas in the admin panel too. This way we could translate products much faster.

    If there are any workarounds for these topics, would you kindly direct us to the right way please?

    Big thanks for this great plugin.

Viewing 5 replies - 1 through 5 (of 5 total)
  • justicef

    (@justicef)

    I have the same problem with disappearing of all translations when changing anything in original text on the site…
    Translations should be blocked and prevented from disappearing. There are no such issues with WPML or Polyang plugins.

    Plugin Support Anghel Emanuel

    (@anghelemanuel99)

    Hello there,

    Thank you for letting us know about this!

    1) ?If you change a string and add a symbol to it such as “.” this will invalidate the translation and that string will be treated as a new string with status 0 (0 means without translation).
    ?
    ?So, for example, you have this string: “I love WordPress” and you put a “.” at the final of the string, this will become “I love WordPress.”.
    ?
    ?TranslatePress will treat the second string as a new one and you`ll need to put a new translation to it.
    ?
    ?If youll delete the "." from the string, the translation will come back because its stored in your local database.
    ?
    ?At the moment this is how our plugin works but we work for this so in the future you won`t be needed to put again the translation.

    2)We need to make the difference between gettext strings, and the original ones and that`s why we create a table in each language.

    3)We work for this so in the future you will be able to add translation in the admin panel too.

    If there`s anything else, please let me know!

    Kind Regards,

    Plugin Support Alex

    (@alexcozmoslabs)

    Since it’s has been more than 5 days since you received instructions about the opened topic, and you did not return with an update, we will mark this ticket as successfully resolved.
    If you have other questions regarding TranslatePress, we recommend you create another ticket.

    Thread Starter alyabee

    (@alyabee)

    Well technically you did not resolve these issues. On the other hand, I found a workaround which never came to my attention. Shortcodes!
    https://translatepress.com/docs/restrict-by-language/translation-shortcode/

    I wish you recommended me this 2 weeks ago. It would save me a lot of time. This fixes all 3 of my problems partially.
    1. I can edit my fat original paragraphs whenever I want without losing translations.
    2. No garbage left behind. Translation gets deleted with product.
    3. I can manage translation directly in admin panel description area.

    This solution must go to the homepage of this plugin to save some time of others.

    Thanks for this great plugin!

    @alyabee I agree and it’s rather funny that you had to find out on your own, but yes, that’s how you can translate post and pages in a Polylang fashion.
    Translating single paragraphs for long posts/pages is insane, terrible organization, and not portable as @anghelemanuel99 kinda admitted.

    In my opinion the best thing is to use shortcodes for posts and long/hot pages, and UI translation for anything else, e.g. tags and categories.

    The big cons are:
    * internal links are not translatable in the free version.
    * excerpts can only be translated via the UI.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Translating more effectively’ is closed to new replies.