Skip to content
Automate string extraction from haml into locale files
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Extract strings likely to be translated from haml templates for I18n translation. Replace the text, create yaml files, do all things you thought macros would solve, but didn't end up really saving THAT much time. Automate that pain away.


gem install haml-i18n-extractor

However I don't upload gems to rubygems in my spare time, so if you want the latest code edge style, you can also simply clone this repo and install the gem from the root of the repo:

gem uninstall -x haml-i18n-extractor; rm *gem; gem build *gemspec; gem install --local *gem


  • You can use the lib directly:
  @ex1 =
rescue Haml::I18n::Extractor::InvalidSyntax
  puts "There was an error with #{haml_path}"
rescue Haml::I18n::Extractor::NothingToTranslate
  puts "Nothing to translate for #{haml_path}"
  • You can also simply run the binary provided with the gem on a rails app:

cd your-rails-app-to-translate && haml-i18n-extractor .

This will run on all the haml files it finds, by suffix, in the cwd you are in and convert them, following the example provided later, below.

Though it works great, I'm dubbing it beta at the moment and ensuring it does not overwrite anything but lets you decide what you want, and don't want.

The workflow at the moment is to run the binary then do a git diff and see all the changes. I would be interested for any feedback you may have on how you would like to use this lib and/or other comments.

What you should be seeing for a "foo.haml" file is a dumped version "foo.i18n-extractor.haml" file which has the representation of the file it tried to translate. It also dumps the corresponding i18n locale .yml file for the haml just translated in the current working directory, suffixed with the path of the haml file it was working on.


This should be a before and after picture of using this lib, whether directly in rubyland or using the executable:

  • Before running (old haml):
  shai@comp ~/p/project ‹master*› » cat app/views/admin/notifications/index.html.haml
  %h1 Consumer Notifications

  .nav= will_paginate(@consumer_notifications)
  %table.themed{cellspacing: 0}
        %th.first Type
        %th Identifier
        %th Data
        %th Success
        %th Reported To
    - @consumer_notifications.each do |cn|
        %td.type= cn.notification.type
        %td.identifier= cn.notification.identifier
        %td.success= cn.success
        %td.reported_to= cn.reported_to
  .nav= will_paginate(@consumer_notifications)
  • After running (new haml, new yaml):

Note how some of the strings are replaced, and the ones that shouldn't, aren't. Yup. Beautiful, right?


  shai@comp ~/p/project ‹master*› » cat app/views/admin/notifications/index.html.i18n-extractor.haml 
  %h1= t('.consumer_notifications')

  .nav= will_paginate(@consumer_notifications)
  %table.themed{cellspacing: 0}
        %th.first= t('.type')
        %th= t('.identifier')
        %th= t('.data')
        %th= t('.success')
        %th= t('.reported_to')
        %th.last= t('.nbsp;')
    - @consumer_notifications.each do |cn|
        %td.type= cn.notification.type
        %td.identifier= cn.notification.identifier
        %td.success= cn.success
        %td.reported_to= cn.reported_to
  .nav= will_paginate(@consumer_notifications)


  shai@comp ~/p/project ‹master*› » cat notifications.index.html.haml.yml  
  --- !ruby/hash:ActiveSupport::HashWithIndifferentAccess
  en: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
    notifications: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
      consumer_notifications: Consumer Notifications
      type: Type
      identifier: Identifier
      data: Data
      success: Success
      reported_to: Reported To
      nbsp;: ! ' '


Can use github issues to address any concern you have, or simply email me, with the contact info here:


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request
Something went wrong with that request. Please try again.