new “Bulk translation” ?

  • Resolved fff654

    (@fff654)


    2 weeks, 6 days ago

    Hi,

    Nice GUI update in 1.7 from today.

    What is the new “Bulk translation” ? one of the 2 topics we have discussed ?

    Where is it ?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Vishali Tayal

    (@vishali009)

    2 weeks, 6 days ago

    Hi,

    Thank you! Glad you liked the GUI update in version 1.7 😊

    Yes, the new “Bulk Translation” feature is the same one we discussed earlier. It allows you to translate multiple pages automatically instead of translating them one by one.

    You can learn how to use it step-by-step in our documentation here:
    https://docs.coolplugins.net/doc/ai-translation-translatepress-bulk-translation/

    We’d also really appreciate it if you could try the feature and share your feedback with us. Your input will help us improve it further.

    Let me know if you have any questions or need help setting it up.

    Best regards.

    Thread Starter fff654

    (@fff654)

    2 weeks, 6 days ago

    hooo, i did not look there, but in your plugin or frontend admin toolbar. OK, clear. And doc has been added in the meantime, nice
    My feedback:

    Short version: IT ROCKS! This should have been a 2.0, as it brings so much in usability.
    (honestly the main plugin dev should have implemented himself that, instead of moving to their $$$ SaaS model copy of DeepL … but that is another debate; you took the opportunity “bring your own key” model and did it well, congrats!)

    Detailed version:
    The ability to select mutiple posts x multiple languages and start all in one batch = SUPER
    Make this available for all CPT = SUPER ALSO

    FYI, I tested on 5 big posts (normally mostly translated already) x 6 target languages = it took about 45 minutes (no problem, its automatic, with no click)

    my 2 suggestions:

    • in the batch window, I would suggest to add a column “strings translated”, example: 267 (string translated), between STATUS and ACTIONS, to have a basic idea of what it did. Currently there is no view if there was a lot translated or nothing new to translate.
      Idealy, it could be “strings translated / total strings”, example 267 / 300 (if 33 where already translated and skipped). That would give a far better view on what is happening behind, especially if your modified your post and run it again or if you retranslate the post again … and permit to stop the process if something is strange.
    • for each provider (Gemini in my case, but question is valid for all), you should really recommend the model that works the best and is the cheapest. Because you know your prompt and context you are providing, you have made tests, and clearly big AI model for string translation is probably overkill … so the smallest model as possible -but tested-, you know already for sure.

    Note: I had to register with Gemini as I was using previoulsy the Google Translate no key 100% Free method. So:

    • With a Gemini key generate as per your link, I got the error “try later”.
    • It did work with another Gemini key I am using for something else.

    Some questions:

    • does it translate only the non-already-translated strings, or the complete post content again ?
    • does it skip strings with the class added in the HTML to not translate that element ? (TranslatePress permits to define a class that we can add anywhere in the page or template; and this is VERY useful to avoid stupid translation of adresses or names or original quotes or adverts or special content)
    • for more advanced WP users: does it translate the custom fields attached to the post also ? (that are displayed in the frontend by the WP template)
    • any plan on slug translation also ? 😉
    Plugin Support Vishali Tayal

    (@vishali009)

    2 weeks, 6 days ago

    Hi @fff654,

    Thanks a lot for the detailed feedback and the kind words—really happy to hear that the feature is working well for you and that the bulk translation is helping with larger batches. Your testing and suggestions are very helpful for us 😊

    About your suggestions:

    1. Batch window – “strings translated” column
    That’s a great idea. Showing something like “Strings Translated” or “Strings Translated / Total Strings” would definitely make it easier to understand what the process is doing. We’ll discuss this with the team and will try to include something like this in a future update

    2. Recommended models for providers
    Good point. For translation tasks, using very large models is usually unnecessary, so recommending tested models that give good quality at a lower cost makes sense. We’ll review this and see how we can improve the recommendations in the docs or settings.

    Answers to your questions:

    • Does it translate only the non-translated strings or the whole post again?
    Right now it translates only the strings that are not already translated, so existing translations are skipped.

    • Does it skip elements marked with the “do not translate” class?
    The plugin follows the same logic as TranslatePress, so it only translates strings that TranslatePress supports for translation.

    • What about custom fields attached to the post?
    If those custom fields are handled by TranslatePress and appear in its translation system, they will be translated as well.

    • Any plan for slug translation?
    Currently the feature works within the normal TranslatePress translation flow. But slug translation is an interesting idea — if you could share a bit more about how you would like it to work, we can definitely look into it.

    And if you’re enjoying the plugin, it would really help us if you could leave a review ⭐ Your feedback helps other users discover the plugin and motivates us to keep improving it.

    Thanks again for taking the time to test everything and share such useful feedback! 🙌

    Thread Starter fff654

    (@fff654)

    2 weeks, 5 days ago

    is it normal that translating 1 post with the post “content” being 1 image + 2x <p> takes 5+ minutes for 1 language ?

    (and the rest of the page, with indeed heavy GUI, already translated before)

    is it making a lot of DB checks or DOM rendering & filtering ?


    (with previous method and front-end free google translation trick, translating 1 page 1 language on the popup where it says “grab a coffee”, a big table and a progress bar, it was less than 10s for 400+ strings … now its Gemeni AI = slow by nature, but only 2 strings)

    Plugin Support Vishali Tayal

    (@vishali009)

    2 weeks, 5 days ago

    Hi @fff654,

    Thanks for testing and sharing this.

    For a post with only 2 strings, 5+ minutes does sound slower than expected. Normally it should finish much faster, even when using Gemini.

    A few things could affect the time:

    • The AI provider response time (sometimes Gemini APIs can be slower depending on load).
    • Background processing / queue execution on the server.
    • TranslatePress string detection and checks before sending the strings for translation.

    But in your case (only 2 strings), it definitely shouldn’t take that long, so we’d like to investigate it further.

    Could you please help us with a couple of details?

    • Which Gemini model are you using?
    • Are you trying to translate the translated pages/posts again?
    • Does the same delay happen again if you run another translation test?

    This will help us reproduce the situation and see if there is anything we can optimize on our side.

    Thanks again for the detailed feedback—it’s really helpful for improving the feature.

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

You must be logged in to reply to this topic.