Pirate English

[Konstantin Haase]

I suggest adding Pirate English (as Facebook and Google have) with the
Accept-Language header value 'xx-pirate'. Also, putting the
localization files somewhere on GH, so users can fork them and send
pull-requests would be awesome.

Konstantin

[Alexey Palazhchenko]

And how about to bring back LOLcatz? :)

–-–
Aleksey

[Henri Watson]

And while we're at it, what about making the API output in LOLcode?

--
- Henri Watson
http://henriwatson.com/
he...@henriwatson.com

[Henrik Hodne]

+1 on open-sourcing the locale files.

Henrik / dvyjones

[Scott Chacon]

I addressed this on the blog post about i18n. There are a number of
issues with releasing locale files - for one, I don't have any. We
keep all the translation data in the database, only english is in a
yml file. I didn't want to have fragmented locale files, for
translators to have to add new strings, for me to have to merge them
(merge conflicts on a locale file? ew). I also didn't want to have
commits each time I took contributions and most of all, I didn't want
to have to deploy for new translations. By having the translations in
the database, we can update it and see new translations in real time.
So, having locale files (yml or po) in a repo for forking will never
happen - it sounds cool, but it's just not a good idea.

Scott