Getting iNaturalist.org registered on translatewiki

This looks like a nice project that is a good fit for translatewiki.net. We (Nikerabbit, Siebrand) will need commit access to push translations. We can start setting up the project here to see if any further issues appear.

Nike (talk)‎14:53, 15 December 2014

Thanks Nike: Is it possible to rather commit to a fork and issue pull requests? That would be preferable for us. Thanks for setting up the project - let us know if you run into any problems.

Loarie (talk)‎01:12, 16 December 2014

No, we don't support pull requests. Review must happen on wiki, otherwise it makes little sense to use a wiki.

Nemo (talk)‎07:09, 16 December 2014

Nemo, would you be able to push translations to a branch other than master?

Loarie (talk)‎18:18, 16 December 2014

Nemo, regarding the pull request/separate branch request, we understand that the translatewiki review process is wiki-based and that's fine. Our motive is not for us to review the translations (we can't, since we don't speak the languages) but to review the effect of the translations on the code e.g. things like Nike mentioned below in 3 & 4

Loarie (talk)‎19:22, 16 December 2014
 
 
 

Some more questions notes:

  1. What is the difference between "es" and "es-ES" locales?
  2. There are what we call lego sentences in the strings: output is constructed by concatenating stuff in the code. This is bad for languages with different word order.
  3. It looks like most of your strings allow arbitrary HTML. While we have never had malicious HTML inserted by our translators, it's still a risk you could avoid by escaping output. By far more likely is that translators will create invalid HTML by mistake.
  4. Worth checking if the date_picker module has upstream translations you could use instead of re-translating them here. There are also strings which are directly input to JavaScript. If a translator makes mistake there, JavaScript on your site might not run.
  5. Do you have a (preferably SVG) logo?

Example of lego: 

  for_a_widget_showing_recent_observations_from: For a widget showing recent observations from %{place_name}, check out the
  for_more_information: for more information.

Example of possible lego or a word which is impossible to translate without message documentation: 

From
Nike (talk)‎15:52, 16 December 2014

1. es is general Spanish and es-ES is Spanish particular to Spain.

2. We'll work on reducing lego sentences

3. We're concerned about that too and want to make sure we test this stuff on a branch before integrating (see request above re: commit access) We'll just have to watch and maybe try using raw() if it'll be a problem

4. We'll check out what the module has. Can you point us in the right direction with a link?

5. Here's two versions of the logo in SVG format: https://www.dropbox.com/s/qhhwfgkbxye0lvm/logo.svg?dl=0 https://www.dropbox.com/s/4zf0t45jkaqo5ko/bird-square-text.svg?dl=0

Loarie (talk)‎19:20, 16 December 2014

Hi, sorry for the wait, but it's hard for me to motivate our staff to work on this project when we can't ensure the translations will be used: I recommend that you give push access to siebrand and nikerabbit. Before his message Nike had already prepared most of the config on dev.translatewiki.net, so it really takes little more to get started.

  1. The differences between the two files are not clear, they are mostly duplicative. Here "es-ES" happens under "es" (and pt-PT on "pt", fr-FR on "fr" etc.), so I guess we'll pull and update "es" <-> "es". It's not clear to me how your "es-ES" file was generated, but if we don't export to it you can continue working on it in the same way. Is this ok?
  2. Ok.
  3. See above. In general, no matter what system you use, translators should translate, not worry about programming languages. So it's extremely recommended that you don't rely on translators being (or being assisted by) programmers for their translations.
  4. It's advisable to know what upstream software you're working with. It seems it might be [1] but I have no time to inspect your source code.
  5. Ok, uploaded at File:INaturalist_logo.svg.
Nemo (talk)‎11:09, 22 December 2014

Hi Nemo, Thanks to you and Nikerabbit for the discussion on freenode yesterday. Nikerabbit & Siebrand now have commit access and sounds like every thing is sorted on our end and now Nikerabbit just needs a few free hours on his end go get this project rolling. We'll eagerly await hearing from you guys when things are set up, but if in the meantime you need anything from us, please give me a shout here. -Thanks!

Loarie (talk)‎21:43, 31 December 2014
 
 
 
 
Retrieved from "https://translatewiki.net/wiki/Thread:Support/Getting_iNaturalist.org_registered_on_translatewiki/reply_(10)#Getting_iNaturalist.org_registered_on_translatewiki_44691"