Thread:Support/Getting iNaturalist.org registered on translatewiki/reply (6)

Nemo:

1. The only sublocales we currently support are: en-US, es-ES, es-MX if that looks good can we close this issue (1)? (will we be able to add additional locals - i.e. yml files - once iNat is registered or is that a bottleneck?)

2. We'll continue to flesh out qqq.yml https://github.com/inaturalist/inaturalist/blob/master/config/locales/qqq.yml to annotate confusing or ambuguous terms, but is it really necessary for us to annotate every string? I've looked at some other examples of this file on translatewiki projects (e.g. https://github.com/EOL/eol/blob/master/config/translations/qqq.yml) and it doesn't look like annotating every string is the usual practice. If our qqq.yml looks like a good start can we close this issue (2)?

3. I now have a better understanding of rails-i18n pluralization which is what we're using since its built into rails. You mentioned that this plulralization was not convincing: https://github.com/inaturalist/inaturalist/blob/master/config/locales/en.yml#L39 Is that because you'd prefer it to be like: x_observations: one: "%{count} observation" other: "%{count} observations" (e.g. https://github.com/openstreetmap/openstreetmap-website/blob/master/config/locales/en.yml#L1268) Because looking at other translatewiki projects, it looks like our existing syntax is used: https://github.com/EOL/eol/blob/master/config/translations/en.yml#L131 If our pluralization system looks good, can we close this issue (3)?

Any other issues we need to address?

Thanks!