Feature request – Making any language the source language

  • Resolved 528491

    (@528491-1)


    3 years, 10 months ago

    Hello,
    I am using the commercial package of the plugin. There is I believe a feature need for an option to choose any of the already translated languages and set them as the source for translating to other languages.
    As it is now, the default language is the only language from which you can translate to other languages. There is no way of choosing a source language to translate from, that would be based on an already existing trp translation.

    The following scenario will not work:

    1. The website is in Croatian, my native language.
      (Very obscure language that Google Translate handles pretty badly)
    2. I set up TranslatePress default language as Croatian.
    3. I translate via TranslatePress from Croatian to English, manually, string by string.
      (Manually, because of the obscurity of the language, and I know English perfectly.).
    4. I then want to use this English translation as a base content to translate further to all other languages (Italian, German, Polish, Czech), automatically, via Google Translation API machine.
      I want it so, because I trust Google API to handle the English source way better than Croatian source.
      I do not want to automatically translate from Croatian to Italian, and other languages, because automatic translation by Google API from Croatian is bad.

    It is impossible to make my existing English trp translation into the source for Google API within Translatepress.

    I am talking about the following panel (please see screenshot):

    View post on imgur.com

    Can you please confirm that this feature will never be in the pipeline for this plugin in the future?

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

  • Hello,

    Thank you for your feature request.

    It is an interesting one indeed.

    Yes, at this moment this is not possible due to the way TranslatePress works.
    At this moment TranslatePress works at the string level and each translated string is directed to his original… due to this way of translation what you proposed is not so achievable as it would require increasing exponentially the database with new tables+ it would require some changes to the core structure of the plugin.

    What we want to say is that we do not exclude the idea from the start, and we will never implement it, but in the near future there are other priorities that we will prioritize.

    Of course, if several users ask for similar features we will gather them all and certainly at some point, we will add a solution to this request.

    Thank you for understanding.

    Cheers,

    Thread Starter 528491

    (@528491-1)

    Thank you kindly for fast reply and informations.
    I’ve seen quite a few support threads asked for this (‘Change default language’ topics), and plugin developer usually redirects them to use the ‘Enable Subdirectory for Default Language’ method to circumvent this, which I shall do as well at this time of course.

    My idea would be to make this available at least for English language, if not for any other language (to keep the database small), since all the Machine translation APIs use English as a the ‘most clean’ starting point.

    Best,

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Feature request – Making any language the source language’ is closed to new replies.