Comments on: Haml + Gettext = automagic translation

By: Language independant translator using haml parser | Josh Software – Where Programming is an Art!

Mon, 29 Aug 2011 18:05:11 +0000

[...] google’d and I found some good reference here. Using this reference I made necessary changes for parsing my .haml pages and enable for [...]

By: Colin Dean

Colin Dean — Sun, 27 Mar 2011 19:22:16 +0000

Thanks for creating this. It’s a great tool.

However, I’m having trouble figuring out where in my Sinatra app to put the FastGettext.add_text_domain and .text_domain call/set.

I’m using bundler to manage gems and have sinatra-hat and fast_gettext in my Gemfile. I also have gettext for :development so I can use its tools.

Inside my app file:

include FastGettext::Translation
require ‘gettext/haml’

Then, to configure FastGettext, I’ve got in in a configure block inside the class definition,

configure do
FastGettext.add_text_domain(‘uio’, :path => ‘locale’)
FastGettext.text_domain = ‘uio’
end

but I get this when I load the page:

FastGettext::Storage::NoTextDomainConfigured at /
Current textdomain (nil) was not added, use FastGettext.add_text_domain !

I’ve tried adding what’s in that configure to just under where I’m requiring gettext/haml, but to no avail.

Thoughts?

By: Igor

Igor — Wed, 21 Jul 2010 18:09:44 +0000

Adam, in my code on github you can check the solution. I took the second approach and instead forced HAML to keep translate(“phrase”) calls within the template. So there is a single template for the whole app locales, but the keys which can be translated are stored within the template not as a plain text but as a ‘translate’ method calls.
This gives some performance degradation of course, but its fine for my project so far.

By: Adam

Adam — Wed, 23 Jun 2010 12:36:59 +0000

Igor: Thanks for a note. Sorry I haven’t replied your previous post. Did you managed to do it for several locales? I believe the trick was to mod HAML a bit so the stored compiled templates are separate per each locale, so adding locale code prefix to compiled template method name should make it.

By: Igor

Igor — Wed, 23 Jun 2010 12:32:50 +0000

If of any use, here: http://github.com/cail/haml_i18n is practically the same code but as a rails plugin and using i18n, not gettext.

By: Igor

Igor — Tue, 22 Dec 2009 14:24:32 +0000

Hi. Tried to adapt your solution (used i18n however).
However found the next flaw with your hack: HAML compiles the template and includes translated texts into the compiled form as a plain text.
This has a consequence that template only adapts to a single locale. Meaning different users (or a single user changing its locale dynamically) will see the very first compiled localization, not different.

There are basically two solutions to this problem. First – it is possible to somehow tell Rails template system to compile separate template for each locale. However that requires monkeyhacking and not quite straightforward.

Another way (which I think I’ll choose) is not to return plain text within your push_plain/parse_tag, but return a push_script(“= _(‘#{text}’)”) instead and force HAML to dynamically translate stuff all the time.

Or, is there any other solutions?

By: Hasan Tan

Hasan Tan — Mon, 29 Jun 2009 20:44:19 +0000

been looking for this information. Thank you very much…