Separate code related to internationalization

[psychoslave]

Hello @jjuliano,

First all apologies I unfortunately can't speak Filipino. I'm conducting a project similar to bato, named Ĝue. I see that you are much more advanced on features you enable in bato. I see that you managed by some way to even translate keywords, all that putted in a gem! Congratulation!

Now, that's already wondeful that I can read and learn from the source code, but it would be even better if we could collaborate to create a common project where internationalization facilities are gathered, and specific localizations would relies on this facilities.

What is your opinion?

Cheers

[psychoslave]

@jjuliano could you explain your approach for closing this ticktet?

Note that there are other projects that make similar port of Ruby to other languages, such as https://github.com/Pluvie/italian-ruby

[jjuliano]

@psychoslave I think a common translatable system can be implemented on the Ruby code itself, as it's much saner. For now, this kind of projects accomplishes those goals (to teach locals programming), but if there's a huge demand for translation in programming logic (creative thinking in their local language) in Ruby or other language, I think this feature should be implemented across the mainstream languages.

[jjuliano]

@psychoslave on the other hand, a plugin based system can be implemented in Ruby, and that does not steer clearly away from the current logic. I imagine translation should be sourced somewhere to a common folder. Existing mature i18n systems can be incorporated (i.e. PO files), or YAML it all the way (akin to Rails).

[psychoslave]

Ok, great to have feedback about this. How could I help as it stands?