About date display
I know this site is displayed date like "January 1 2013"(%{month} %{day}, %{year}). In Korean, date is showed like "2013년 1월 1일"(%{year}년 %{month} %{day}일). In Chinese and Japanese, date is showed like "2013年 1月 1日"(%{year}年 %{month} %{day}日). but site is use only "%{month} %{day}, %{year}".
Apologies, this is (surprisingly or not) outside the scope of EOL translations. We rely on Sven Fuch's Rails I18n ( https://github.com/svenfuchs/rails-i18n ) for date translations. If the format is incorrect, it would actually need to be fixed there. :\
Sorry.
Is rails-i18n now being used? I recall that in the early days, there was a customised version in EOL...
아라, if you're interested, I could guide you to contributing to the rails i18n framework (if you don't know already or are not able to find out by yourself -- it would be a new thing for me too :P).
You're actually right that we don't include the gem in our Gemfile, but we use it to "bootstrap" the translations, periodically.
That said, I'd like to stop doing that, and integrate it. The problem is that it seems to enforce "proper" pluralization in Russian and Arabic, so we'll either need to not include those (less desirable) or add "few" pluralizations based on the "other" translations that exist at the moment.
I've put a ticket to that effect into our queue, but I don't know if we'll get to it in the near-term.
THAT said, we can always "steal" from rails-i18n at any time it's convenient, without adopting the gem fully, so if inroads are made there, we'll gladly grab the data at that point in time.
Any status update, Jeremy?
It's still on the TODO list, sorry. We've had some ... shall we say... "team restructuring" that has made it difficult to prioritize this task. Sorry!
Seems we can use EOL:Website-date.formats.long and EOL:Website-time.formats.long to localize it now, so why not close this?