Gustavo started a discussion about how to contribute translations for openproject. In the resulting pull request relaxdiego proposed to crowdsoure translations.

‘Great idea!’ I though, so let’s collect some translations tools/websites

I propose we collect some more translation tools/services/plugins first (please tell me if you know some) and opinions about them.
After comparing what we’ve found, we can decide which tool to use.

Best,
Tessi

it seems still incorrect, all of the translation name become ‘English’.
I select them one by one, it seems Simplified Chinese is missing.

The translations key general_lang_name should contain the name of the language, which is ‘English’ for the english translations.
Unfortunately people translated the word english to their language instead of writing the name of the current language into that key.
This can be easily fixed on crowdin.

I am not sure what happened with Simplified Chinese but I’ll investigate.

— tessi

Simplified Chinese should now appear. Taiwanese Mandarine (both have the ‘zh’ language code) took it’s place. Now both should appear (but Taiwanese Mandarin is still named “English” in the menu).

I took the chance to fetch the current translations from crowdin and uploaded them.

I know I misunderstood the key general_lang_name when I was working on crowdin, so I have already fixed it for Simplified Chinese translation.
However, if I put the yml file directly into folder locales, I can get the right translation with direct translation of ‘English’. But it is not the case after installing the plugin, all of them became ‘English’(I have captured the screen in attachment), and none of them is Simplified Chinese.(actually 2 of them are the uncompleted Traditional Chinese.)

update plugin to the latest, it is correct now.
but still getting error message in log when i click ‘administration’->‘settings’. I have tried run the precompile, not working.

ActionView::Template::Error (jstoolbar/lang/jstoolbar-zh-cn.js isn't precompiled):
    33: <p><%= setting_text_field :app_title, :size => 30 %></p>
    34: 
    35: <p><%= setting_text_area :welcome_text, :cols => 60, :rows => 5, :class => 'wiki-edit' %></p>
    36: <%= wikitoolbar_for 'settings_welcome_text' %>
    37: 
    38: <p><%= setting_text_field :attachment_max_size, :size => 6 %> <%= l(:"number.human.storage_units.units.kb") %></p>
    39: 
  lib/redmine/wiki_formatting/textile/helper.rb:51:in `block in heads_for_wiki_formatter'
  lib/redmine/wiki_formatting/textile/helper.rb:50:in `heads_for_wiki_formatter'
  lib/redmine/wiki_formatting/textile/helper.rb:35:in `wikitoolbar_for'
  app/views/settings/_general.html.erb:36:in `block in _app_views_settings__general_html_erb___599123391255880555_32912920'
  app/views/settings/_general.html.erb:30:in `_app_views_settings__general_html_erb___599123391255880555_32912920'
  app/views/common/_tabs.html.erb:61:in `block in _app_views_common__tabs_html_erb___1894114438409737620_55244240'
  app/views/common/_tabs.html.erb:60:in `each'
  app/views/common/_tabs.html.erb:60:in `_app_views_common__tabs_html_erb___1894114438409737620_55244240'
  app/helpers/application_helper.rb:319:in `render_tabs'
  app/views/settings/edit.html.erb:34:in `_app_views_settings_edit_html_erb___4520726662695454535_55381460'
  app/controllers/settings_controller.rb:37:in `index'

Thanks for the error report!

It seems that crowdin and jstoolbar disagree on the names of translation files.
I added a file-rename step to the plugin, which names the translation files so that jstoolbar works with it.

After an update of the plugin

bundle update --source=openproject-translations

All user which use chinese will be reverted to use english. You have to reenable chinese as an available language (in the settings).

Please tell me if it works for you (the administration page works for me in production).

So far the translation is working fine. Thanks for the work.
Is there any plan to translate the plug-in?

got a error today when creating new work package in timeline view, if I decided to close the dialog without saving current input.

[missing "zh.js.timelines.really_close_dialog" translation]

this should be a translation of

really_close_dialog: "Do you really want to close the dialog and loose the entered data?"

maybe it is missing in the Simplified Chinese file. BTW, where is the translation file after the plug-in installation?

The translation exists in zh.yml (you’ll find the translations at the place where the openproject-translation gem was installed and then in the subdirectory config/locales.

It might be that you need to do another

  bundle exec rake assets:precompile

(and then a server restart)

so that javascript translation get recompiled.

If this fixes your problem, then I’ll add the step to the plugin README.

Concerning plugin-translations, I’ll ask some colleagues and come back to you later.

Hello all,

My team and I have finished the French translation of the interface. I’m sorry I didn’t use the Crowdin thing, but we could work much faster by directly editing the file.

The translation is complete as we’ve gone through every line, which means that this is basically ready to be used as an official translation if you like. Of course, there’s always a small possibility of errors that we’ve missed (or got mangled in a technical-speech kind of way), so please feel free to give feedback.

We’re very happy to contribute this back to the project, and hope others find it useful.

Philipp Tessenow wrote:

The translation exists in zh.yml (you’ll find the translations at the place where the openproject-translation gem was installed and then in the subdirectory config/locales.

It might be that you need to do another

[…]
(and then a server restart)

so that javascript translation get recompiled.

If this fixes your problem, then I’ll add the step to the plugin README.

Concerning plugin-translations, I’ll ask some colleagues and come back to you later.

the precompile works as expected.

Thanks, I’ll add the precompile step to the plugin-readme.

Concerning plugin translations, we are currently not set on a solution.
Plugins may be contributed by everyone (so the OPF team has no control over their translations). We could rely on the plugins to server their own translations, or have a separate crowdin project (and translation gem?) for every plugin. Which option do you prefer? Do you have any other ideas?

Jay Kay, thanks for your contribution! :)

I’ll look into merging your translations with the crowdin ones, if I find enough spare time to do that.

Philipp Tessenow wrote:

Thanks, I’ll add the precompile step to the plugin-readme.

Concerning plugin translations, we are currently not set on a solution.
Plugins may be contributed by everyone (so the OPF team has no control over their translations). We could rely on the plugins to server their own translations, or have a separate crowdin project (and translation gem?) for every plugin. Which option do you prefer? Do you have any other ideas?

At least you can manage the translation for those plugins from OPF team, and integrate the crowdin projects together. For the rest of plugins, of course you have no control and I agree to let them decide their translation method. The OPF team can give your guidline and preference. What do you think?

It seems the latest stable openproject code has been changed a lot, the crowdin project doesn’t reflect the changes. If we use the current translation file, we might get errors. For example, in the latest stable 3.0.3, the original en.yml file contains a group named ‘select2’, while it is not existing in the crowdin file. As we can see a lot of difference, could you update the crowdin project accordingly?

Thanks for notifying us.

Unfortunately I am not aware of a method to have crowdin translations for two branches of the same project (`dev` and `stable`). currently we use the `dev` branch. But you are right, we should better take the `stable` branch, as that is what we recommend for installation.

Currently, I cannot promise when we are able to fix it. However, I created a WorkPackage () to track the progress of this bug. I will try to schedule it, so that we can fix it soon.

cheers,
tessi

Hi everyone,

I’ve just sign up on crowdin, and made myself part of the project. I’ve started validating the Spanish translation already. I’d like to know if there’s a way of downloading the .yml file, in order to add it to my local OpenProject install.
Thanks in advance,

Ignacio

Hello Ignacio,

as you can read here in the thread ;) just install the OpenProject Translations plugin and you can use all OpenProject translations.
To install the plugin add the following line to the Gemfile.plugins than run bundle install

gem "openproject-translations", :git => 'https://github.com/opf/openproject-translations.git', :branch => 'stable'

Best
Ratzi

Thanks so much, Ratzi :)
I’m really sorry I didn’t read the thread thoroughly :( I’ll try to pay more attention next time.

Cheers,

Nacho

Hello everyone,

the translations plugin was out of sync with the OpenProject core for some time now. Sorry if this caused you any inconvenience! I have fixed the underlying problem in the last couple of days.

Now we have up-to-date translations again. A plus is that the error which came when installing the translations plugin should be fixed too.

Another thing is, that we support multiple versions of OpenProjet now. So we can have translations for the current stable version, older versions, as well as a bleeding edge development version.

If you experience any problems with the updated translations plugin, please reach out to us and we have a look at it.

cheers,
Philipp