• Resolved Dennis Rasmussen

    (@dennisras)


    Hi Burst,

    Is there a reason that our suggested translations get rejected and then added as your own translations? I’ve noticed this happens in a lot of the languages. We’re talking about thousands of translations written by contributors.

    https://translate.www.ads-software.com/projects/wp-plugins/burst-statistics/contributors/

    Translation contributors spend hours upon hours writing these translations in order to support the plugin. Good collaboration ensures the sustainability of the contribution and improves translation quality, but am I missing something here or why are all of our work being discarded like this?

    I went back to check the status of the Danish translations, because I’ve noticed that the dashboard still isn’t fully translated, but then I notice the above and it makes me wonder if we should even volunteer to help out with translations for this project.

    Thanks for reading.

    • This topic was modified 1 year, 8 months ago by Dennis Rasmussen. Reason: Link
Viewing 1 replies (of 1 total)
  • Plugin Contributor Leon Wimmenhoeve

    (@leonwimmenhoeve)

    Hi @dennisras,

    First of all, thank you very much for your contribution to the Danish translations. We greatly value contributions of volunteer translators very much, as it helps to provide our plugins to a greater audience.

    It is not at all our intention to deny credit for anyone that contributes to the plugin, hence the props in our changelogs for code contributions.

    You are right to notice that we reject suggestions and upload them again. We do this because this allows us to process any corrections in the future. Unfortunately we have seen translations being added and approved by PTEs that (for various reasons) needed corrections later on. These strings can then only be corrected by PTEs or GTEs.

    Especially for languages with less active translation teams it can take up to months to get in touch (via polyglots and Slack) with someone that then takes the time to review and approve these corrections. This is very time consuming and frustrating for users that rely on (sometimes front-end facing) strings.

    I have discussed this with the Dutch translation team as well, but there doesn’t seem to be a prettier workaround at the moment.

    I’d like to encourage you to keep contributing to the Danish translations, as we wouldn’t be able to offer our plugins in this many languages without volunteer translators! Please feel free to reach out to me personally (on Slack or via our support channel) if you wish to discuss this further. We are always open for suggestions!

    Kind regards,
    Leon

Viewing 1 replies (of 1 total)
  • The topic ‘Rejected translations?’ is closed to new replies.