BetterTranslate 🌍

🚀 A powerful Ruby gem for seamless YAML file translations using AI providers like ChatGPT and Google Gemini

BetterTranslate simplifies the translation of YAML files in your Ruby/Rails applications by leveraging advanced AI models. With support for both ChatGPT (OpenAI) and Google Gemini, it offers:

✨ Key Features

• 🔄 Smart translation modes (Override/Incremental)
• 🎯 Precise key exclusion control
• 📊 Real-time progress tracking
• 🧪 Comprehensive test coverage
• ⚡️ LRU caching for performance
• 🔍 Translation similarity analysis
• 📚 Extensive YARD documentation

• 🌐 AI-Powered Translation: Leverage ChatGPT, Google Gemini, and custom providers for high-quality translations
• 🔄 Smart Translation Modes:
  • Override: Full file rewrite
  • Incremental: Update only new/modified keys
• 🎯 Precise Control:
  • Global key exclusions
  • Language-specific exclusions
  • Dot notation support
• 🛠 Developer-Friendly:
  • Rails generators included
  • Custom provider support
  • Comprehensive test suite
  • LRU caching for performance
  • Progress tracking
  • Detailed YARD documentation
• 🔍 Translation Analysis:
  • Similarity detection
  • Detailed reports
  • Optimization suggestions
• 🔧 Flexible Helpers:
  • Single text translation
  • Bulk text translation
  • Multiple target languages support

Add the gem to your Gemfile:

gem 'better_translate', '~> 0.5.0'

Then run:

bundle install

Or install the gem manually:

gem install better_translate

In a Rails application, generate the initializer by running:

rails generate better_translate:install

This command creates the file config/initializers/better_translate.rb with a default configuration. An example configuration is:

BetterTranslate.configure do |config|
  # Choose the provider to use: :chatgpt or :gemini
  config.provider = :chatgpt
  
  # API key for ChatGPT (OpenAI)
  config.openai_key = ENV.fetch("OPENAI_API_KEY") { "YOUR_OPENAI_API_KEY" }
  
  # API key for Google Gemini
  config.google_gemini_key = ENV.fetch("GOOGLE_GEMINI_KEY") { "YOUR_GOOGLE_GEMINI_KEY" }
  
  # Source language (e.g., "en" if the source file is in English)
  config.source_language = "en"
  
  # Output folder where the translated files will be saved
  config.output_folder = Rails.root.join("config", "locales", "translated").to_s
  
  # List of target languages (short_name and name)
  config.target_languages = [
    # Example:
    { short_name: "it", name: "italian" }
  ]
  
  # Global exclusions (keys in dot notation) to exclude from translation
  config.global_exclusions = [
    "key.child_key"
  ]
  
  # Language-specific exclusions: keys to exclude only for specific target languages
  config.exclusions_per_language = {
    "es" => [],
    "it" => ["sample.valid"],
    "fr" => [],
    "de" => [],
    "pt" => [],
    "ru" => []
  }
  
  # Path to the input file (e.g., en.yml)
  config.input_file = Rails.root.join("config", "locales", "en.yml").to_s
  
  # Translation mode: :override or :incremental
  config.translation_mode = :override
end

To start the translation process, simply call the magic method:

BetterTranslate.magic

This will execute the process that:

1. Reads the input YAML file.
2. Applies the global exclusion filtering.
3. Applies additional language-specific exclusion filtering for each target language.
4. Translates the strings from the source language into the configured target languages.
5. Writes the translated files to the output folder, either in override or incremental mode based on the configuration.

The gem includes generators to simplify tasks:

• Generate Initializer:

  rails generate better_translate:install

• Trigger Translation Process:

  rails generate better_translate:translate

  The better_translate:translate generator will trigger the translation process (via BetterTranslate.magic) and display progress in the terminal.

• Analyze Translations:

  rails generate better_translate:analyze

• Create Custom Provider:

  rails generate better_translate:provider YourProviderName

  The better_translate:analyze generator will:

  • Scan all YAML files in your locales directory
  • Find similar translations using Levenshtein distance
  • Generate two reports:
    • translation_similarities.json: Detailed JSON report
    • translation_similarities_summary.txt: Human-readable summary

  This helps you:

  • Identify potentially redundant translations
  • Maintain consistency across your translations
  • Optimize your translation files
  • Reduce translation costs

BetterTranslate allows you to create and use custom translation providers, enabling integration with any translation API or service. This feature is particularly useful if you want to use a translation service not natively supported by BetterTranslate, such as DeepL, Microsoft Translator, Amazon Translate, or any other API-based translation service.

1. Generate a custom provider template:

   rails generate better_translate:provider DeepL

   This creates a new provider class in app/providers/deep_l_provider.rb and a README with implementation instructions.

2. Implement the translation logic:

   Edit the generated provider file to implement the translate_text method with your API-specific code:

   # app/providers/deep_l_provider.rb
   module Providers
     class DeepLProvider < BetterTranslate::Providers::BaseProvider
       def initialize(api_key)
         @api_key = api_key
       end
   
       def translate_text(text, target_lang_code, target_lang_name)
         # Implement your API call to DeepL here
         # Return the translated text as a string
       end
     end
   end

3. Register your provider:

   Create an initializer to register your custom provider:

   # config/initializers/better_translate_providers.rb
   # Require the provider file to ensure it's loaded
   require Rails.root.join('app', 'providers', 'deep_l_provider')
   
   BetterTranslate::Service.register_provider(
     :deepl,
     ->(api_key) { Providers::DeepLProvider.new(api_key) }
   )

   Note: The require statement is important to ensure the provider class is loaded before it's used.

4. Update your configuration:

   Add your API key to the BetterTranslate configuration:

   # config/initializers/better_translate.rb
   BetterTranslate.configure do |config|
     config.provider = :deepl
     config.deepl_key = ENV['DEEPL_API_KEY']
     # ... other configuration
   end

5. Use your custom provider:

   Your custom provider will now be used when you call BetterTranslate.magic or any other translation method.

6. Troubleshooting:

   If you encounter a NameError related to the Providers module, make sure the provider file is properly required in your initializer as shown in step 3. The require statement ensures that the provider class is loaded before it's used.

BetterTranslate provides helper methods to simplify translation tasks.

The translate_text_to_languages helper allows you to translate a single text into multiple target languages in one call.

Example Usage:

text = "Hello world!"
target_languages = [
  { short_name: "it", name: "Italian" },
  { short_name: "fr", name: "French" }
]

translated = BetterTranslate::TranslationHelper.translate_text_to_languages(
  text,
  target_languages,
  "en",       # source language code
  :chatgpt    # provider: can be :chatgpt or :gemini
)

puts translated
# Expected output:
# { "it" => "Ciao mondo!", "fr" => "Bonjour le monde!" }

The translate_texts_to_languages helper extends the functionality to translate an array of texts into multiple target languages. It returns a hash where each key is a target language code and the value is an array of translated texts.

Example Usage:

texts = ["Hello world!", "How are you?"]
target_languages = [
  { short_name: "it", name: "Italian" },
  { short_name: "fr", name: "French" }
]

translated_texts = BetterTranslate::TranslationHelper.translate_texts_to_languages(
  texts,
  target_languages,
  "en",       # source language code
  :chatgpt    # provider: can be :chatgpt or :gemini
)

puts translated_texts
# Expected output:
# {
#   "it" => ["Ciao mondo!", "Come stai?"],
#   "fr" => ["Bonjour le monde!", "Comment ça va?"]
# }

BetterTranslate comes with a comprehensive test suite using RSpec. To run the tests:

bundle exec rspec

The test suite covers:

• Core translation functionality
• Cache implementation (LRU)
• Provider selection and initialization
• Error handling
• Configuration management

1. Fork the repository
2. Create your feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

• Email: alessio.bussolari@pandev.it
• Issues: GitHub Issues
• Discussions: GitHub Discussions

This project is licensed under the MIT License - see the LICENSE.txt file for details.

BetterTranslate aims to simplify the translation of YAML files in Ruby projects by providing a flexible, configurable, and extensible system. Whether you need a complete file rewrite or an incremental update, BetterTranslate streamlines the translation process using advanced providers like ChatGPT and Google Gemini. Contributions, feedback, and feature requests are highly encouraged to help improve the gem further.

For more details, please visit the GitHub repository.

BetterTranslate is distributed under the MIT license. See the LICENSE file for more details.