Comments on: simplyglobal : A simple globalization plugin for Rails http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/ Because programming should be fun Wed, 04 Jan 2012 05:17:14 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Dan http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/comment-page-1/#comment-766 Dan Mon, 03 Nov 2008 22:14:14 +0000 http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/#comment-766 The <a href="http://www.artweb-design.de/2008/7/18/the-ruby-on-rails-i18n-core-api" rel="nofollow">i18n support in Rails 2.2</a> looks great! Can't wait to try it. But for the moment, I will still use SimplyGlobal. The i18n support in Rails 2.2 looks great! Can’t wait to try it. But for the moment, I will still use SimplyGlobal.

]]> By: Frank http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/comment-page-1/#comment-759 Frank Sat, 01 Nov 2008 14:20:11 +0000 http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/#comment-759 I just wanted to say that we used SimplyGlobal in 4 projets already and it did the job very well everytime. What I like the most about Dan's plugin is the fact that the translations are NOT stored in YML files or in the database. Everything is plain Ruby. Moreover it's a very light plugin that just does what you expect. Now maybe i18n support in rails 2.2 will make simplyglobal unnecessary... this I don't know. But for now, this plugin is the best of its kind in my opinion. I just wanted to say that we used SimplyGlobal in 4 projets already and it did the job very well everytime. What I like the most about Dan’s plugin is the fact that the translations are NOT stored in YML files or in the database. Everything is plain Ruby. Moreover it’s a very light plugin that just does what you expect. Now maybe i18n support in rails 2.2 will make simplyglobal unnecessary… this I don’t know. But for now, this plugin is the best of its kind in my opinion.

]]> By: links for 2008-11-01 « Bloggitation http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/comment-page-1/#comment-757 links for 2008-11-01 « Bloggitation Sat, 01 Nov 2008 07:08:32 +0000 http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/#comment-757 [...] simplyglobal : A simple globalization plugin for Rails (tags: ruby rails programming) [...] [...] simplyglobal : A simple globalization plugin for Rails (tags: ruby rails programming) [...]

]]> By: jeremy http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/comment-page-1/#comment-756 jeremy Sat, 01 Nov 2008 04:59:01 +0000 http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/#comment-756 Will this not become redundant with the imminent release of rails 2.2 with i18n support? Will this not become redundant with the imminent release of rails 2.2 with i18n support?

]]> By: Dan http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/comment-page-1/#comment-754 Dan Fri, 31 Oct 2008 15:48:30 +0000 http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/#comment-754 I had this problem too. When I coded the "hello %s".t("Johnny"), it suited my needs... until the day I had the problem you are describing. Maybe one day, I will add that feature. I keep it has a possible enhancement : http://code.google.com/p/simplyglobal/issues/detail?id=4 I had this problem too. When I coded the “hello %s”.t(“Johnny”), it suited my needs… until the day I had the problem you are describing. Maybe one day, I will add that feature. I keep it has a possible enhancement : http://code.google.com/p/simplyglobal/issues/detail?id=4

]]> By: Luke http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/comment-page-1/#comment-753 Luke Fri, 31 Oct 2008 15:33:50 +0000 http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/#comment-753 this is a subject of some interest to me. simplicity is good, and this is probably fine for completely static translations. what about dynamically-generated text? i don't know if any frameworks really handle well a situation where, e.g., the text "i found #{x} files in #{y} directories" needs to be translated into a language where the word order would come out "in #{y} directories, #{x} files were found" and furthermore you need to inflect files/directories depending on the cardinality of x and y (which in some languages is far more complicated than singular vs plural). keep hoping someone will code that one up... this is a subject of some interest to me. simplicity is good, and this is probably fine for completely static translations. what about dynamically-generated text? i don’t know if any frameworks really handle well a situation where, e.g., the text “i found #{x} files in #{y} directories” needs to be translated into a language where the word order would come out “in #{y} directories, #{x} files were found” and furthermore you need to inflect files/directories depending on the cardinality of x and y (which in some languages is far more complicated than singular vs plural). keep hoping someone will code that one up…

]]> By: Dan http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/comment-page-1/#comment-751 Dan Thu, 30 Oct 2008 20:24:17 +0000 http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/#comment-751 I guess you could just reload a new hash of translations and it would replace the old translation hash. I'd say that if you change it once, it would change for the whole application in production (since the classes are cashed and it uses @@ class variables). In development, you'd have to reload the new translations at each request. I'm not 100% sure of what I say but if you test it, I'd like to know the result. Thanks! I guess you could just reload a new hash of translations and it would replace the old translation hash. I’d say that if you change it once, it would change for the whole application in production (since the classes are cashed and it uses @@ class variables). In development, you’d have to reload the new translations at each request.

I’m not 100% sure of what I say but if you test it, I’d like to know the result.

Thanks!

]]> By: Zubin http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/comment-page-1/#comment-750 Zubin Thu, 30 Oct 2008 20:14:32 +0000 http://www.rubyfleebie.com/simplyglobal-a-simple-globalization-plugin-for-rails/#comment-750 Nice one Dan, I like the way it's simple and therefore flexible. One question: If, say, one wanted to draw on a database of phrases instead of a manual hash, is there a method to reload the translations when they are edited? Nice one Dan, I like the way it’s simple and therefore flexible. One question: If, say, one wanted to draw on a database of phrases instead of a manual hash, is there a method to reload the translations when they are edited?

]]>