Internationalise strings throughout the website (i18n)

[Skud]

Taken from this discussion thread:

Here's a list of priorities of strings to be i18n'd by turning "foo" into t("foo") and putting the relevant string in config/locales/en.yml

• top navbar items ("Crops", "Community", etc)
• bottom navbar items ("Contact", "Terms of Service", etc)
• page titles throughout the site, eg. "Edit planting"
• action buttons, eg. "Save", "Plant this", etc.
• field names on forms throughout the site, eg. "Planted at:"
• items shown in the "thumbnail" and "index card" views for plantings, crops, members, etc
• Note that as we go, we should definitely think about creating helpers or view partials for anything that gets reused frequently, to avoid repetition and make sure there's only one string to translate (see the signup_signin partial as an example).

So the task here is to slog through all of this. I don't expect anyone will do it all at one hit, but feel free to do a handful and issue a PR for any small amount you like.

I've marked this as "curated: beginner" as it seems like a beginner-friendly thing to do. A step by step howto would probably also help with that.

[roryaronson]

We're just looking into translating our i18n strings for OpenFarm. You might find the discussion/links helpful: openfarmcc/OpenFarm#429

Have you researched any ways/services to translate your strings? Perhaps we can work together considering we have very similar ones?

[Skud]

I suspect our strings are sufficiently different that it might not
actually help that much, just looking through some of the text on your
site. We have a few short strings in common ("search", "about",
"privacy") but not much else. I did a rough review of Growstuff's
app/views and found around 1500 strings in our app so there's obviously
a lot there.

Wrt our plans: we'll be working with our community for translations,
taking our lead from a few other open source projects we're familiar
with. We've been looking around for a good web UI for l10n but haven't
found much that impresses us as yet. For now it's just locales/*.yml.

A.

On 21/01/2015 6:57 am, Rory Aronson wrote:

We're just looking into translating our i18n strings for OpenFarm. You
might find the discussion/links helpful: openfarmcc/OpenFarm#429
openfarmcc/OpenFarm#429

Have you researched any ways/services to translate your strings?
Perhaps we can work together considering we have very similar ones?

—
Reply to this email directly or view it on GitHub
#658 (comment).

Alex "Skud" Bayley
[email protected]
http://growstuff.org/

[roryaronson]

Right on, that makes sense about most of the strings being different. Thanks for the quick update!

[cesy]

That linked pull request is an example, if anyone wants to have a go at this.

[jestallin]

I will take a stab at this.

[cesy]

Footer will no longer apply as that's now using our CMS. We'll need to investigate how translation for CMS works.

[jestallin]

@cesy https://github.com/jestallin/growstuff/commit/788742ce0e5dbc3244faecc3921b7f28fa9f4cb7 for top nav

[jestallin]

@cesy 85f7ca4 for drop down and some page titles

[cesy]

@jestallin looks good, so PR?

[jestallin]

POC for automating the process using rake and haml-i18n-extractor - 9858180 @cesy

[maco]

In a lot of these cases, we're dealing with a model's name. We should use .model_name methods. Most likely, that's Model.model_name.singular and Model.model_name.plural (or in situations where we don't know whether singular or plural, Model.model_name.human, but #919 is a separate issue for that)