gratipay / gratipay.com

Here lieth a pioneer in open source sustainability. RIP
https://gratipay.news/the-end-cbfba8f50981
MIT License
1.12k stars 308 forks source link

Internationalize user interface messages (i18n) #957

Closed dahlia closed 10 years ago

dahlia commented 11 years ago

Although I’m not sure if it’s really necessary for open source hackers, but I think it would be nice. The most of open source hackers are already enough familiar with English, but I think givers might not.

Aspen seems not to have any special considerations about internationalization, but we can simply go Babel.

Opinions?

chadwhitacre commented 11 years ago

This would be awesome! You're right that Aspen doesn't make any provisions for i18n. Have you used Babel before?

dahlia commented 11 years ago

@whit537 I’ve done i18n several times using Babel before. I want to work on this if you don’t mind.

chadwhitacre commented 11 years ago

@dahlia Yes, please. This is great! :D

chadwhitacre commented 11 years ago

Dropping from Infrastructure. See #1030.

clone1018 commented 10 years ago

To note, our templating engine is now Jinja2 which has a plugin for i18n

chadwhitacre commented 10 years ago

+1 from eliasfbarros in private email.

elbarros commented 10 years ago

I'm happy to help with translation. I spoke with a friend about the project he also would like to help. The translation is being done using Aspen or Babel? Is there any simple tutorial to install Gittip in Ubuntu13.10?

zbynekwinkler commented 10 years ago

There is a PR with a script to install gittip on ubuntu 12.04. You can take a look. It might help. If I remember right the postgres package from 12.04 can be installed on 13.10 if you uninstall logrotate. There was a repo with postgres 9.3 for ubuntu 13.10 @rummik is using https://launchpad.net/~chris-lea/+archive/postgresql-9.3 (I haven't tried it).

All other info should be in the README.md.

chadwhitacre commented 10 years ago

+1 from Gérard Foucher from France via support@gittip.com.

patcon commented 10 years ago

Thoughts on using a python port of rails' i18n gem? I've been messing around with LocaleApp, and it seems like it would help us make internationalization dead-simple to crowdsource: http://www.localeapp.com/

Technically, LocaleApp is meant to work for the ruby i18n lib, but since python-i18n is a direct port, we should be able to get it working. Could even have travis pull in the most recent translations before deploying a slug to heroku :)

(I don't like that localeapp isn't open source, but the UI seems really slick, so I think it might be worth using a closed source app in to get the best experience to our volunteer translators!)

patcon commented 10 years ago

Oh, I might take the process for a test-spin by internationalizing the strings for our invoke tasks. Will submit a PR.

patcon commented 10 years ago

cc: @YenaHong (I saw in your intro repo that you do translations, and thought this might be up your alley)

ghost commented 10 years ago

Well, I usually do translations on translatewiki.net, which was originally designed for MediaWiki i18n. Though translation using any platform is OK, but what we should do is deploying translation quickly (and if possible, automatically).

patcon commented 10 years ago

Gotcha. LocaleApp seems to have a really slick UI, so it might suffice

patcon commented 10 years ago

cc: @nemobis @siebrand @Nikerabbit from translatewiki project: https://translatewiki.net/wiki/Project:About https://github.com/wikimedia/translatewiki

siebrand commented 10 years ago

Interesting project. Taking a look at your i18n.

siebrand commented 10 years ago

Hmm, there is no i18n yet, is there? I'm not familiar with the above mentioned python port of a Ruby i18n framework. If that's rails-i18n with YAML files, that would be very nice.

patcon commented 10 years ago

Yep, you're right about lacking i18n. And yes, the railsy yaml format is how it works in ruby-land, so personally would prefer to stay cross-compatible for the sake of tooling

nemobis commented 10 years ago

Yes, that's a format we support. See https://translatewiki.net/wiki/Translating:New_project for requirements, I see it's a CC-0 website and while you i18n it you'll also need to add message documentation. https://translatewiki.net/wiki/Translating:Localisation_for_developers#Message_documentation

patcon commented 10 years ago

FYI someone else is using translatewiki for non-mediawiki sites (the flash editor UI): https://translatewiki.net/wiki/Translating:OpenStreetMap

Not quite as smooth as localeapp, but free software is nice :)

The next thing to figure out is whether there's a cli for pushing and pulling translations, as that's a really helpful feature of localeapp that will allow us to sync translations on travis deploy...

patcon commented 10 years ago

@michaelbaudino @futhr I don't suppose @Locale has any plans to go open source anytime soon? Closed source software def part of your business model? coughopencompanycough :)

futhr commented 10 years ago

@patcon Localeapp is a free service for open source projects.

patcon commented 10 years ago

@futhr thanks man :) I'm aware it's free for OSS projects, but I still lean toward using services that use free software, for all the reasons here: https://github.com/bevry/goopen

So that's a no? It's not an internal topic of discussion either? No problem if it isn't, just looking for clarity

futhr commented 10 years ago

@patcon I'm unable to answer that. Its a question for the project owner @tigrish

patcon commented 10 years ago

@futhr :+1: thanks. I'll just hold off on his comment before moving forward

nemobis commented 10 years ago

Yes, some dozens projects use translatewiki.net. https://translatewiki.net/wiki/Category:Supported_projects You don't need cli access, translations are committed directly to your repo, as explained in https://translatewiki.net/wiki/Translating:New_project (please give @siebrand and @nikerabbit push access when you want to move forward).

"Not quite as smooth": have you tried translating? Please register on the main page and give it a try, or use https://meta.wikimedia.org/wiki/Special:Translate which is open for everyone. At any rate, please file the things you (would) miss from Localeapp: https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions&component=Translate

patcon commented 10 years ago

@nemobis thanks very much! I'll give the docs a further read. They're great, but it's simply that, having dedicated about equal time to each, I feel I understand LocaleApp a little better. But I'll commit some more time to both :)

Perhaps it would be beneficial to start with LocaleApp, so we understand that workflow, and then migrate to TranslateWiki, so we'll know what might be missing, if anything (and then we can perhaps commit code ourselves to scratch that itch ;)

EDIT: In retrospect, I think all the pretty screen captures on LocaleApp were what made my lazy skimming so information-dense :)

chadwhitacre commented 10 years ago

There's also https://www.transifex.com/, which is an open product.

nemobis commented 10 years ago

Not by the definition of open service http://opendefinition.org/software-service/

chadwhitacre commented 10 years ago

@nemobis Thanks, I hadn't seen the opendefinition.org website before, nor their definition of an "open service." Ftr, I was referring to the definition of an open product that I laid out last year.

patcon commented 10 years ago

Mysterious translation app comparison spreadsheet of unknown origins and authorship ;) https://docs.google.com/spreadsheet/ccc?key=0AvdoxmL5NpHydFFKMXJVZ1B0ZnpsUWd3LTVQRngtcmc&usp=drive_web#gid=0

glezos commented 10 years ago

Hey guys, Dimitris, founder of Transifex here. We'd be happy to host gittip on Transifex. There are more than 15.000 open-source projects hosted, including Linus Torvald's own pet projects, so you'll be in good company.

In terms of openness, Transifex is much closer to GitHub than your average open-source project.

My advice, based on experience, is to invest in a solid localization platform. It makes the difference between 4 languages 85% translated and 20 languages 98% translated.

nemobis commented 10 years ago

My advice, based on experience, is to invest in a solid localization platform. It makes the difference between 4 languages 85% translated and 20 languages 98% translated.

Agreed. One such solid platform is translatewiki.net (or any MediaWiki + Translate install of course, it's all free software) and the last project added got 100 % translated in 12 languages in less than a month. Of course it's not as big as fedora. :) https://translatewiki.net/wiki/Special:MessageGroupStats/out-nfcring-control#sortable:3=desc

seanlinsley commented 10 years ago

http://blog.discourse.org/2014/05/translating-discourse-with-transifex/

kyzh commented 10 years ago

Transiflex does a very good job. I used it for both "The Foreman" and theforeman.org, I warmly recommend it .

ericmeltzer commented 10 years ago

+1 for transifex, have used it and loved it.

chadwhitacre commented 10 years ago

!m @oakes

astrojuanlu commented 10 years ago

The web needs an update! http://inside.gratipay.com/appendices/colophon https://github.com/gratipay/inside.gratipay.com/blob/master/www/appendices/colophon.spt#L79

chadwhitacre commented 10 years ago

@Juanlu001 Done in https://github.com/gratipay/inside.gratipay.com/commit/2332729c8f1dd29fa4c9db3e0597f167de16f31c and https://github.com/gratipay/inside.gratipay.com/commit/68fcbcadcba8c28b34c86ee7c6d35f0acda626dc! :-)