This Client SDK provides tools for translating Rails applications into any language using the TranslationExchange.com service.

To integrate Tml SDK into your own application, add the gem to your app:

Add the following gem to your Gemfile:

gem 'tml-rails'

Install the gems:

$ bundle install

Create a tml initializer file with the following configuration:

config/initializers/tml.rb

Tml.configure do |config|
  config.application = {
    key:   YOUR_APPLICATION_KEY,
  }
  config.cache = {
    enabled: true,
    adapter: 'rails'
  }
end

Tml must be used with caching enabled.

If you are already using Rails caching, you probably already specify it in your production file, like the following:

config/environments/production.rb

config.cache_store = :mem_cache_store, { :namespace => 'my_cache' }

Memcache for multiple servers:

config.cache_store = :mem_cache_store, '123.456.78.9:1001', '123.456.78.9:1002'

Memcache with Dalli:

config.cache_store = :mem_cache_store, Dalli::Client.new('localhost:11211', {
  :namespace => 'my_cache'
})

For Redis:

config.cache_store = :redis_store, {
  host:       'localhost',
  port:       6379,
  db:         0,
  namespace:  'my_cache'
}

Tip: to clear up Redis cache

$ redis-cli FLUSHALL

Then all you need to do is specify that you want to use the Rails cache adapter:

config/initializers/tml.rb

config.cache = {
  enabled:  true,
  adapter:  'rails'
}

Alternatively, you can provide a separate memcache server to store your translations:

config.cache = {
  enabled:    true,
  adapter:    'memcache',
  host:       'localhost:11211',
  namespace:  'translations'
}

You can also use Redis to persist your translations cache:

config.cache = {
  enabled:    true,
  adapter:    'redis',
  host:       'localhost',
  port:       6379,
  password:   'password',
  namespace:  'translations'
}

The above examples use shared caching model - all your Rails processes on all your servers share the same translation cache. This approach will save you memory space, as well as allow you to invalidate/redeploy your translations cache without having to redeploy your application.

To update the cache, execute the following line of code:

Tml.cache.upgrade_version

Or you can run the rake command from any of your app instances:

$ bundle exec rake tml:cache:upgrade

This will effectively invalidate your current cache and rebuilt it with the latest translations from Translation Exchange CDN.

An alternative approach is to pre-generate all your cache files when you deploy your application. The translation cache will be loaded and stored in every process on every server, but it will be faster at serving translations and this approach does not require cache warmup.

To specify in-memory, file-based cache, provide the following configuration:

config.cache = {
  enabled:  true,
  adapter:  'file',
  path:     'config/tml',
  version:  'current'
}

The file based cache can be generated from your current release using the following command:

$ bundle exec rake tml:cache:generate

In the HEAD section of your layout, add:

<%= tml_scripts_tag %>

Now you can simply add the default language selector anywhere on your page using:

<%= tml_language_selector_tag(:popup) %>

The default language selector is used to enable/disable translation modes. It may be useful on staging or translation server, but it may not be ideal on production. There are a number of alternative language selectors you can use, including your own.

To use a dropdown language selector that uses locale in the url parameter, use:

<%= tml_language_selector_tag(:dropdown, {
    :style => "margin-top:15px",
    :language => :english
}) %>

To use a list language selector that uses locale in the url parameter, use:

<%= tml_language_selector_tag(:list, {
    :style => "margin-top:15px",
    :language => :english
}) %>

If you want to see just a list of flags, use:

<%= tml_language_selector_tag(:flags, {
    :flags_only => true
}) %>

Now you can use Tml's helper methods and TML (Translation Markup Language) to translate your strings:

<%= tr("Hello World") %>
<%= tr("You have {count || message}", count: 5) %>
<%= tr("{actor} sent {target} [bold: {count || gift}]", actor: actor_user, target: target_user, count: 5) %>
<%= tr("{actor} uploaded [bold: {count || photo}] to {actor | his, her} photo album.", actor: current_user, count: 5) %>
  ...

There are some additional methods that can be very useful. For instance, if you want to translate something inside a model, you can simply use:

"Hello World".translate

Learn more about TML at: http://translationexchange.com/docs

If your application is already using the standard i18n framework, you can mix in the Tml framework on top of it. To do so, you need to set the i18n backend to Tml. Add the following line to your tml initializer:

config/initializers/tml.rb

I18n.backend = I18n::Backend::Tml.new

Now the "t" function will automatically fallback onto "tr" function. If you have the following in your base language file:

config/locales/en.yml

en:
  hello: "Hello world"
  my:
    nested:
      key: "This is a nested key"

Then you can call:

<%= t(:hello) %>
<%= t("my.nested.key") %>

And the i18n will use Translation Exchange as the backend for your translations. On top of it, you can continue using Tml's extensions:

<%= tr("Hello World") %>
<%= tr("This is a nested key") %>

The above calls are equivalent.

Tml comes with its own logger. If you would like to see what the SDK is doing behind the scene, enable the logger and provide the file path for the log file:

Tml.configure do |config|

  config.logger  = {
      :enabled  => true,
      :path     => "#{Rails.root}/log/tml.log",
      :level    => 'debug'
  }

end

Tml comes with default settings for the rules engine. For example, it assumes that you have the following methods in your ApplicationController:

def current_user
end

def current_locale
end

Tml only needs the current_user method if your site needs to use gender based rules for the viewing user.

Similarly, if you prefer to use your own mechanism for storing and retrieving user's preferred and selected locales, you can provide the current_locale method.

If you need to adjust those method names, you can set them in the config:

Tml.configure do |config|

  config.current_user_method = :my_user

  config.current_locale_method = :my_locale

end

The best way to start using the SDK is to run a sample application that comes bundled with this SDK.

$ git clone https://github.com/tml/tml_rails_clientsdk.git
$ cd tml_rails_clientsdk/spec/dummy
$ bundle

Before you running the application, visit TranslationExchange.com, register as a new user and create a new application.

Update your key and secret in the following file: config/initializers/tml.rb

config.application = {
    :key => YOUR_KEY,
    :secret => YOUR_SECRET
}

Now you can start the application by running:

$ bundle exec rails s

This will start the dummy application on port 3000. Open your browser and point to:

http://localhost:3000

• Register on TranslationExchange.com: http://translationexchange.com

• Read Translation Exchange documentation: http://docs.translationexchange.com

• Follow TranslationExchange on Twitter: https://twitter.com/translationx

• Connect with TranslationExchange on Facebook: https://www.facebook.com/translationexchange

• Watch our demo videos on YouTube: https://www.youtube.com/channel/UC7gLEbvNO1IKPv5dxwzR3Iw

• If you have any questions or suggestions, contact us: feedback@translationexchange.com

Copyright (c) 2017 Translation Exchange Inc

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.