The WebTranslateIt Blog

The Challenge

Screenshots are invaluable for translators—they show exactly where and how text appears in your application. But annotating screenshots by manually drawing rectangles around each piece of text and searching for the corresponding segment? That’s tedious, especially for screens packed with UI elements.

The Solution: Auto-Detect Segments

Our new auto-detection feature uses OCR (Optical Character Recognition) to automatically find text in your screenshots and create draft annotations. Here’s how it works:

Full Screenshot Detection

Click the Auto-detect Segments button in the sidebar to scan the entire screenshot at once. The system identifies text elements and creates draft annotations for each one—with the detected text pre-filled in the search box.

Region-Based Detection

For more control, draw a selection on the image first. The button changes to Detect text in selection, scanning only the area you’ve selected. This is perfect for focusing on a specific part of a busy interface.

Smart Text Grouping

The detection intelligently groups related text together based on visual proximity. Side-by-side UI elements like “Settings · Profile” are recognized as separate items, each getting their own annotation.

The Workflow

1. Upload your screenshot
2. Click Auto-detect Segments or draw a selection first for targeted detection
3. Review the draft annotations (shown with dashed purple borders)
4. Click each draft to open a search dropdown pre-filled with the detected text
5. Select the matching segment to convert the draft into a linked annotation
6. Dismiss any drafts you don’t need with a single click

What used to take minutes of careful drawing and searching now takes seconds.

Best Practices

• Focus on translatable text: Skip user-generated content like usernames, dates, or dynamic data that isn’t in your translation files
• Use region selection: For complex screens, select specific areas to get more accurate results
• Review before linking: Auto-detection does the heavy lifting, but a quick review ensures accuracy

Try It Today

Visual Context with auto-detection is available now for all projects. Head to your project’s File Manager → Visual Context tab, upload a screenshot, and experience the faster way to provide visual context for your translators.

Learn more in our Visual Context documentation.

We’re excited to announce that Mistral AI is now available as a machine translation provider in WebTranslateIt!

What is Mistral AI?

Mistral AI is a French artificial intelligence company that has quickly become one of the leading providers of large language models in Europe. Their models are known for being fast, efficient, and particularly strong at understanding context and nuance in translations.

Why Mistral AI for Translation?

Like our existing Gemini AI integration, Mistral AI goes beyond simple word-for-word translation. It understands:

• Translation Instructions: Project-level guidelines that help maintain consistent terminology and tone across all translations
• Translation Terms (Glossary): Your custom terminology is automatically applied to ensure brand consistency
• Context: Mistral considers the full context of your content, producing more natural-sounding translations

How to Enable Mistral AI

1. Go to your User Settings → Translation Suggestions
2. Select Mistral AI from the available machine translation providers
3. Start translating!

You can also use Mistral AI for Batch Operations to machine translate multiple segments at once:

1. Open your project’s Batch Operations page
2. Select “Machine translate” as the operation
3. Choose Mistral AI as your provider
4. Select the target languages and run the operation

Pricing

Mistral AI translations are billed based on character count, similar to our other AI translation services. You can monitor your usage in Organization Settings → API Usage.

Get Started Today

Mistral AI is available now for all WebTranslateIt users. Give it a try and let us know what you think!

---

Have questions about Mistral AI or any of our machine translation options? Contact our support team at support@webtranslateit.com — we’re happy to help!

We’re excited to announce new features that give you better visibility and control over your machine translation usage on WebTranslateIt.

What’s New

Included Machine Translation Quota

All WebTranslateIt plans now include a generous machine translation character quota:

• Starter & Premium: 500,000 characters/month
• Enterprise: 2,000,000 characters/month
  

This quota covers all machine translation services including Google Translate, Microsoft Translator, and our new Gemini AI integration.

Usage Dashboard with Visual Progress

We’ve redesigned the API Usage page (found under Organization → Billing → API Usage) to give you clear visibility into your machine translation consumption:

• Progress bar showing your current billing period usage against your quota
• Color-coded status: Green when usage is healthy, yellow when approaching the limit, red when over quota
• Monthly breakdown with the ability to click into any month for daily usage details
• Service-level visibility showing exactly how many characters were translated by each provider

Transparent Overuse Billing

If you exceed your included quota, additional usage is billed at a simple, predictable rate of €30 per million characters. This is automatically calculated at the end of each billing cycle.

No surprises—you can always see your current usage and any projected overuse charges on the billing page.

Why These Changes?

Machine translation has become an essential tool for localization teams. These changes ensure:

1. Predictability: Know exactly what’s included in your plan
2. Transparency: See your usage at a glance with visual progress indicators
3. Flexibility: Go over your quota when needed without service interruption
4. Fairness: Pay only for what you use beyond your included quota

Getting Started

Visit your Organization’s Billing page and click on “API Usage” to see your current machine translation consumption. The new dashboard shows your billing period usage, quota, and historical trends.

Questions about your quota or usage? Reply to any WebTranslateIt email or contact us at support@webtranslateit.com.

We’re excited to announce a major update to WebTranslateIt’s translation workflow: AI-Powered Translation Suggestions. This release brings together machine translation and translation memory into a unified, intelligent experience.

New: Gemini AI Translation

We’ve added Google’s Gemini AI as a translation option in WebTranslateIt. Gemini brings a fresh approach to machine translation, leveraging large language models to produce more natural, context-aware translations.

Unlike traditional neural machine translation, Gemini can better understand nuance, idiomatic expressions, and maintain consistency across longer texts. It’s particularly effective for creative content, marketing copy, and user interface strings where tone matters.

Plural form support: Gemini AI can machine translate plural forms—something traditional MT engines like Google Translate and Microsoft Translator can’t do. When translating a segment with plural forms, Gemini generates all the plural categories required by the target language automatically.

Unified Translation Suggestions

The new Translation Suggestions panel in the translation toolbar combines all your translation resources in one place:

• Google Translate - Fast, reliable machine translation
• Microsoft Translator - Alternative MT engine for comparison
  
• Gemini AI - Google’s latest AI model for natural, context-aware translations
• Translation Memory - Your existing translations for consistency

Simply toggle on the services you want to use, and WebTranslateIt will fetch suggestions from all enabled sources as you translate.

Per-User Preferences

Each team member can now configure their own preferred translation services. Enable Google Translate, Microsoft Translator, Gemini AI—or all of them at once. Your preferences are saved and applied automatically, and you’ll see suggestions from all your enabled services side by side.

Enhanced Batch Operations

You can now choose which machine translation to run directly in batch operations. Select your segments, choose your preferred MT engine (Google, Microsoft, or Gemini), and translate hundreds of segments at once.

Smarter Plural Form Handling

When batch translating plural forms with Gemini AI, WebTranslateIt now properly generates all plural categories required by the target language. For example, when translating to Polish (which has one, few, many, and other forms), the system creates the appropriate structure automatically.

Improved Toolbar Experience

We’ve refreshed the toolbar dropdown menus with a cleaner, more intuitive design:

Translation Memory Fuzziness Control

Fine-tune your translation memory matches with the new fuzziness slider. Choose between:

• Fuzzy matches - See more suggestions, even partial matches
• Exact matches only - Strict matching for maximum consistency

Getting Started

The new features are available now in your translation interface. Open any project, click on a segment to translate, and look for the Translation Suggestions button in the toolbar.

---

We’re committed to making translation faster and easier. These AI-powered features are just the beginning—stay tuned for more updates!

Questions or feedback? Contact our support team.

Ever wondered what changed between your local translation files and what’s on WebTranslateIt? Now you can find out instantly.

Introducing wti diff

Version 3.2.0 of the wti gem introduces a new command: wti diff. It lets you compare your local translation files with the versions hosted on WebTranslateIt, right from your terminal.

Why is this useful?

Before pushing or pulling files, you might want to know:
- What local changes haven’t been pushed yet?
- Did someone update the remote file since your last pull?
- Are there any conflicts to be aware of?

Now you can answer these questions before committing to a sync.

How to use it

Compare all your source language files:

wti diff

Or compare a specific file:

wti diff config/locales/en.yml

The output shows a standard diff between the remote version (on WebTranslateIt) and your local file.

Installation

Update to the latest version:

gem install web_translate_it

Or if you’re using Bundler, update your Gemfile and run bundle update web_translate_it.

---

Thanks to @vpolozov for this contribution!

Speed is everything when you’re translating hundreds of segments. We’re thrilled to introduce a new keyboard navigation system that lets you select translation suggestions without ever touching your mouse.

What’s New?

You can now navigate through translation memory suggestions and machine translation results using arrow keys and apply them with a simple Enter press. This enhancement makes the translation workflow significantly faster for power users who prefer keyboard-driven interfaces.

How It Works

Opening a Segment

When you open a segment for translation (press Enter or click the edit icon), WebTranslateIt automatically loads suggestions from:

• Your Project Translation Memory: Translations from your current and connected projects
• Global Translation Memory: Over 24 million translations from the community
• Machine Translation: Results from Google Translate, Microsoft Translator, DeepL, etc. (if configured)

Navigating Suggestions

Once suggestions load, you can navigate them using your keyboard:

1. From the textarea: Press ↓ (Down arrow) when your cursor is at the end of the text
2. First suggestion: Automatically highlighted and focused
3. Move between suggestions: Use ↓ (Down) and ↑ (Up) arrows
4. Apply suggestion: Press Enter to paste it into the translation field
5. Return to textarea: The focus automatically returns to your translation

Visual Feedback

As you navigate with arrow keys, the currently selected suggestion is visually highlighted, making it easy to see which one you’re about to apply.

Complete Translation Keyboard Shortcuts

Here’s a refresher on all available keyboard shortcuts in the translation interface:

Navigation

• ↓ or J — Select next segment
• ↑ or K — Select previous segment
• Enter — Open selected segment for editing
• / — Focus on search field
• H — Display keyboard shortcuts help

In an Open Segment

• Esc — Close segment without saving
• Tab — Save and move to next segment
• Shift + Tab — Save and move to previous segment
• Cmd/Ctrl + Enter — Save current translation
• ↓ — Navigate to suggestions (when cursor at end of text)
• ↑ / ↓ — Navigate between suggestions
• Enter — Apply selected suggestion

Segment Actions

• P — Mark segment as proofread
• F — Flag segment as “to verify”
• V — Copy source text to target
• C — Open comments
• D — Open segment details
• I — View instructions
• L — View all translations for segment
• → — Go to segment history
• ← — Return to segment list

Real-World Example

Let’s say you’re translating a software interface from English to French:

1. Navigate to the next untranslated segment with ↓
2. Open the segment with Enter
3. The translation memory loads and shows several French suggestions
4. Review suggestions using ↓ to scroll through them
5. Select the best match with Enter to paste it
6. Edit if needed (maybe just a small terminology adjustment)
7. Save and continue with Tab to move to the next segment

All of this without touching your mouse!

Why This Matters

Speed

Keyboard navigation is significantly faster than mouse clicking. For professional translators working on large projects, this can mean:

• 30-50% faster suggestion selection
• Reduced context switching between keyboard and mouse
• Better flow state during translation sessions

Ergonomics

Keeping your hands on the keyboard reduces repetitive strain from constantly moving between keyboard and mouse. This is especially important for translators who work long hours.

Precision

Sometimes with a mouse, you might accidentally click the wrong suggestion, especially when they’re visually similar. Keyboard navigation gives you precise control with clear visual feedback.

Translation Memory Reminder

Not familiar with WebTranslateIt’s Translation Memory? Here’s a quick overview:

Project Translation Memory learns from translations in your current project and connected projects. The more you translate, the better it gets.

Global Translation Memory contains over 24 million translations from projects that choose to contribute. You can opt in or out in your project settings.

Translation Memory automatically provides:

• Complete Matches (100%): Exact matches from previous translations
• Partial Matches: Similar segments with varying match percentages
• Context awareness: Prioritizes suggestions from your own projects

You can adjust suggestion quality using the matching level selector at the bottom of the screen (4, 7, 10, or Complete Match).

Learn more in our Translation Memory Documentation.

Machine Translation Support

This keyboard navigation also works with machine translation suggestions! If you’ve configured machine translation engines (Google Translate, Microsoft Translator, DeepL, etc.), their results appear in the suggestions list alongside translation memory matches.

Navigate and apply them the same way—with arrow keys and Enter.

Pro Tips

1. Combine with other shortcuts: Use V to copy source text, then ↓ to check suggestions, then Tab to save and continue
2. Adjust match quality: Use higher quality settings (10 or Complete Match) to see only the best suggestions
3. Learn the flow: Practice the rhythm of Enter → ↓ → Enter → Tab for maximum speed
4. Use search: Press / to quickly jump to specific segments using keyword search

Getting Started

This feature is available immediately for all users on all plans. No configuration needed—just open the translation interface and start using arrow keys to navigate suggestions!

Press H in the translation interface to view all available keyboard shortcuts.

We’d Love Your Feedback

We’re constantly working to improve the translation experience. If you have ideas for additional keyboard shortcuts or workflow improvements, please let us know at support@webtranslateit.com.

Happy translating! ⌨️🚀

---

Additional Resources:

• Translation Interface Documentation
• How to Translate Guide
• Keyboard Shortcuts Reference (accessible by pressing H)
• Translation Memory Documentation

We’re excited to announce a powerful enhancement to our API label filtering system that makes it easier than ever to work with segments across multiple categories.

What’s New?

You can now use OR logic when filtering segments by labels in the WebTranslateIt API. This means you can retrieve segments that match any of the specified labels, not just those that match all of them.

How It Works

The Syntax

Use the |[label1,label2,label3] syntax to filter segments with OR logic:

GET /api/projects/:project_api_key/strings.json?filters[label]=|[bug-fix,new-feature]

This returns all segments labeled with either “bug-fix” OR “new-feature”.

Real-World Example

Let’s say you’re managing a large localization project and you want to export all segments that need urgent attention. You’ve been using labels to categorize your work:

• high-priority for critical segments
• bug-fix for corrections
• release-blocker for segments that must be translated before launch

Previously, you would need to make three separate API calls to fetch each category. Now, you can get them all in one request:

curl "https://webtranslateit.com/api/projects/YOUR_API_KEY/strings.json?filters[label]=|[high-priority,bug-fix,release-blocker]"

Complete Label Filtering Options

WebTranslateIt now supports three different label filtering modes:

1. Single Label Match (default)

filters[label]=urgent

Returns segments with the “urgent” label.

2. OR Logic (any of the labels)

filters[label]=|[label1,label2,label3]

Returns segments with any of the specified labels.

3. AND Logic (all of the labels)

filters[label]=[label1,label2,label3]

Returns segments with all of the specified labels.

4. Negative Matching (exclude a label)

filters[label]=!unwanted

Returns segments that do not have the “unwanted” label.

5. No Labels

filters[label]=none

Returns segments with no labels at all.

URL Encoding

Remember to URL-encode your labels when making API requests. Spaces should be encoded as + or %20, and special characters must be properly escaped:

filters[label]=|[new+feature,bug+fix,ui+improvement]

Use Cases

This feature is particularly useful for:

• Batch exports: Download all segments from multiple related categories at once
• Priority filtering: Combine different priority levels (critical, high, medium) in one query
• Feature-based filtering: Get all segments related to multiple features (checkout, payments, shipping)
• Status tracking: Filter by multiple workflow states (needs-review, needs-context, needs-screenshot)
• Release management: Gather segments for multiple upcoming releases

Integration with Existing Workflows

This enhancement works seamlessly with all other API filters. You can combine OR logic with:

• Status filters (filters[status]=to_translate)
• File filters (filters[file]=123)
• Category filters (filters[category]=mobile)
• Date range filters (filters[created_at]=2025-10-01)
• Type filters (filters[type]=string)

Example combining multiple filters:

curl "https://webtranslateit.com/api/projects/YOUR_API_KEY/strings.json?filters[label]=|[urgent,high-priority]&filters[status]=to_translate&filters[locale]=fr"

This returns all French segments that are untranslated and marked as either “urgent” OR “high-priority”.

Documentation

For complete API documentation, including all available filters and parameters, visit:

API String Documentation

You can also learn more about label filtering in our FAQ:

Searching for segments with multiple labels

Getting Started

This feature is available immediately in the API for all WebTranslateIt plans. No changes are required to your existing integrations—OR logic is a new syntax option that works alongside your current label filtering.

Try it out and let us know how it improves your workflow! If you have questions or feedback, reach out to us at support@webtranslateit.com.

---

Technical Details:

• Label matching is case-sensitive
• You can include as many labels as needed in the array
• The feature is available in both the read-only and read-write API endpoints

We released the version 3.0.0 of our synchronization tool wti. This is mostly a code refactoring release and it removes one dependency. Here’s the changelog:

• Remove dependency on multipart_post gem
• Don’t rescue SSL Errors.
• Move ArrayUtil#to_columns to StringUtil
• Replace custom ArrayUtil#chunks with native ruby method each_slice
• Autocorrect frozen strings comments offences

See the complete wti changelog.

The update to the gem is also available as a docker package, which is running the latest Alpine linux with ruby 3.2.2.

We’ve released an update to WebTranslateIt where all organization on the plans including Machine Translation (all plans excluding the Starter plan) get access to free machine translations using Google Translate or Bing Translator.

In your project settings you can now select if you want suggestions to run with Google Translate or Microsoft Translator. You won’t have to input your own API key anymore, we’re using our own API key and take care of the bill.

We hope you will like this improvement. Thank you for using WebTranslateIt!

In order to maintain WebTranslateIt’s service we will take the service down for a hardware maintenance.

We’re upgrading our servers to more powerful and energy saving hardware.

In order to do this upgrade we will need to be unavailable on Saturday, May 20th 2023, 07:00 CEST (Paris Time) as we migrate the data to our new servers. We expect the downtime to not exceed 2 hours. The website will be unavailable from Saturday, May 20th 2023, 07:00 CEST to Saturday, May 20th 2023, 09:00 CEST.

As always, we’ll keep you updated on this blog post and we’ll also post live updates on @webtranslateit on Twitter.

We apologize for this planned downtime.

Hi! I hope you’re having a productive week so far. We’ve been shipping several important updates to WebTranslateIt in the past month. We focussed our attention to code refactoring, improvements to existing features and performance improvements.

We have also released a new category on our blog: The Changelog, where you can see the nitty gritty details about the updates that we make. You can subscribe through the changelog’s atom feed. You can also read the changelog on the dashboard when you’re signed in. It’s a quick and easy way to keep you informed about our latest changes.

Here’s what has changed, by order of importance.

Faster Translation Suggestions

We’ve released an update to the Translation Suggestions system to make them load much faster. They are so fast actually, that we’ve simplified and removed all the loading system that used to work via background jobs. Enjoy a much better user experience when using translation suggestions.

More information: Faster Translation Suggestions

Faster File Updates

We released another round of improvements to our file generation system to make them much faster.

More information: Faster File Updates

Updated our YAML handler

Our YAML files are now generated with a new handler using libyaml. The file output will be different. Here is an example of the differences between our current YAMLer and the new YAMLer.

More information: Updated our YAML handler

Update to the word and character count system using Unicode’s text segmentation standard

This is a very deep change on how words and characters are counted in WebTranslateIt. The new system is more accurate, especially when counting words or characters in CJK language.

You can read more information:
- in our documentation about word counting
- or in the changelog entry.

Translation suggestions system improved

We improved the translation suggestions system for projects using Gettext PO files. Due to the nature of PO files, the source text is often blank and is populated by the key name, and this wasn’t picked up by the suggestions system. We updated our translation memory so that it also uses the text from the key names.

More information: Translation suggestions system improved

API Authentication Update

We’ve refactored how the API Authentication system works internally. The project and organization API keys are now prefixed with proj_readwrite and proj_readonly, for example. There is no need to update your integration.

More information: API Authentication Update

Project image charts updated

We replaced the charts system using the long deprecated Google Image Charts with one provided by quickcharts.io.

More information: Translation Charts Update

Removed low-priority import mode

It used to be possible to push a language file and set the import as a low priority. This was a nice thing to do in the early ages of WebTranslateIt when importing many files used to clog our import queue, but it doesn’t matter anymore so we removed that option and deprecated the command options on the wti client.

More information: Removed low-priority import mode

We have released a new version of the web_translate_it gem, the open-source synchronization Command Line Interface tool for Web Translate It.

This new version brings a few improvements:

• Add ability to see translation statistics per file.
  • wti status gives the whole translation project statistics,
  • wti status path/to/file gives the file translation statistics.
• We have updated the documentation to indicate that we have a docker package for easy installation: https://github.com/webtranslateit/wti-docker/pkgs/container/wti-docker

---

Install or Upgrade

To install web_translate_it, please refer to the gem documentation.

As usual, upgrade web_translate_it to its latest version by typing in a terminal: gem install web_translate_it.

Follow us on Twitter, LinkedIn & Facebook for instant updates.

We’ve been busy working on the app. Here’s an update of what we’ve been up to.

A large infrastructure update

We have spent a few months working on upgrading our app framework Ruby on Rails to the latest version 7. We also upgraded ruby to the latest version 3.1.

While doing so, we also worked on increasing our test code coverage. We also ran tools such as rubocop to standardize our code.

We also upgraded our translation serialization system which previously relied on a custom serializer using YAML to use native Postgres JSONB fields. It looks like nothing, but migrating close to 90 million translations took us over a week!

Overall these upgrades were a lot of work, but were worth it, as they helped us increase our software quality, standardize the way we write code and increased the website performance while lowering our resources usage.

We have replaced our Translation Memory engine

We have been using Sphinx Search for almost 10 years (we’re not getting any younger are we? 😳) and it has served us well. However our database server PostgreSQL now integrates a great full-text search engine, and it is easier to maintain it than having both PostgreSQL and Sphinx running side by side. So we simplified our stack and now use PostgreSQL to run our translation memory.

We have also set up a series of tests and benchmarks to maintain and improve the translation memory speed and relevance, and we will keep improving on it.

All our infrastructure and providers are now in the European Union & GDPR compliant 🇪🇺

We hired a GDPR specialist and revised our Data Processing Agreement and improved our GDPR support.

We were also advised to make some changes on the providers we use (namely Amazon S3 hosted in the US and Mailchimp) to use similar services hosted in the European Union. Our Amazon S3 assets are now hosted in Germany and our newsletter by MailJet. You can see a list of all our providers on our Privacy page.

We value our users’ privacy so we’re now proudly made and hosted in the EU, and we’re also Carbon Neutral since 2017.

New homepage

We have a new homepage! You can see it when you are signed out of WebTranslateIt. The new homepage uses a new responsive design and includes a lot of new illustrations.

Auto-Translate

We’ve released a new feature for the organisations on the Enterprise plan: Auto-Translate.

Auto-Translate is a feature that lets you use the translations hosted on the different projects on your organization and automatically apply them to your projects right when a new translation candidate appears.

For instance if you add segments to a project and some of these new segments’ text have already been translated elsewhere (on your project or on another project hosted on your organization) it will use the other translations and apply them to your new segments.

It also works if a translator translates a segment on a project and if another similar segment exists elsewhere on your organization: as the first segment gets translated, the similar segments will get translated automatically.

New versions of the wti CLI tool

We’ve released several versions of our synchronisation tool wti. The latest changes include compatibility with ruby 3.1 and we’ve just added a new subcommand wti status path/to/file to see the translation statistics about a file.

If you don’t know about wti, you should try it it’s a great command-line tool to easily sync your language files with WebTranslateIt.

We also now have a docker package for wti.

Update to the Translation Interface

We’ve updated the Translation Interface with a brand new search bar which integrates case-sensitive and regex search. We hope you like these changes.

Follow us on Facebook, Twitter and LinkedIn for instant updates.

Today we released a new API endpoint to delete a Collaboration.

A collaborator is a person working on your organization and projects. Deleting a collaboration does the following:

• it removes the user from the organization,
• it removes any project memberships,
• it cancels any unaccepted invitations on your organization’s projects,
• it removes any team memberships,
• it cancels any unaccepted invitations on your organization’s teams.

So that person won’t be able to access anything on the organization.

I hope you will find this new feature helpful to manage your users. Thank you for using WebTranslateIt!

We’re removing JSONP support on all our API endpoints. JSONP (JSON with Padding) is a historical JavaScript technique for requesting data by loading a <script> element, and is ancient technology now.

It could be used to load data from our API using Javascript from another domain, by bypassing same-origin policy, which disallows running JavaScript code to read media DOM elements or XMLHttpRequest data fetched from outside the page’s originating site.

JSONP has been superseded with CORS in modern applications.

We’ve monitored our API usage over the past few days and nobody is using JSONP, so this deprecation shouldn’t impact anyone.

Do you translate? Do you know what the character counter is? Here is another trick for our power-translators out there.

When translating software, it is important to keep the size of the text your type as concise as possible, as it can cause size problems (text overflowing elements or going out of the viewport, etc). The character counter you can see at the bottom right of the translation text area gives you a soft warning when the text you typed in is more than twice as large as the size of the source text.

When translating size-constraint segments, the character counter gives you a hard warning that you went over the limit, and actually prevents you from saving your translation.

This is the sixth episode of our new series of posts with short, useful tips showing you how to use some of the most advanced features in WebTranslateIt that maybe you didn’t know existed.

Do you find these tips and tricks useful? Let us know on Twitter @webtranslateit if you like this series of posts.

Related Posts

• How to use case-sensitive search and regex search with the new search bar
• Use a specific date in the filters
• How to quickly add a term to the TermBase
• How to filter segments by more than one label
• 2 ways to paste translation suggestions in WebTranslateIt

Did you know you could filter segments by more than one label? Well you can. This trick is for power users.

In the Translation Interface, click on the first label you’d like to filter by. Then, go to the address bar and search for the label parameter. Replace the label name by square brackets [ ] and then type in the label names you want to search by separated by commas. You should have something like labels=[label1,label2].

This is the fourth episode of our new series of posts with short, useful tips showing you how to use some of the most advanced features in WebTranslateIt that maybe you didn’t know existed.

Do you find these tips and tricks useful? Let us know on Twitter @webtranslateit if you like this series of posts.

Related Posts

• How to use case-sensitive search and regex search with the new search bar
• Use a specific date in the filters
• How to quickly add a term to the TermBase
• 2 ways to paste translation suggestions in WebTranslateIt

We have released a new version of the web_translate_it gem, the open-source synchronization Command Line Interface tool for Web Translate It.

This new version brings a few improvements:

• Better support for before_pull, after_pull, before_push, after_push hooks. They now display the command output, and write an error message if the exit status of the command was not successful.
• Add ability to ignore files from pulls with a setting in the .wti file. It lets you ignore a specific file, or use a glob to ignore a series of files. Example: ignore_files: ['**/fr.yml', 'config/locales/js/*.yml', 'config/locales/app/fr.yml']
• Remove silence_errors = true option that could be put in the configuration file, which was silencing SSL connexion errors. SSL is important, and if it isn’t properly configured, it needs to be fixed on your machine by updating your cert chain.
• We have also updated our documentation to show how you should use wti to handle multiple projects.

---

Install or Upgrade

To install web_translate_it, please refer to the gem documentation.

As usual, upgrade web_translate_it to its latest version by typing in a terminal: gem install web_translate_it.

Follow us on Twitter, LinkedIn & Facebook for instant updates.

We’ve had a look at the file formats we support and noted that 4 of them are now obsolete. In order to streamline our code we will retire these file formats on June 1st, 2022.

The obsolete file formats are:

• Babbel Flash, used for Flash app localization,
• Blackberry rrc, for Blackberry apps localization,
• Typo3 LLXML, for older version of Typo3. The community has moved to XLIFF,
• WebL10N, used for FirefoxOS localization.

Want more information? Follow us on Facebook, Twitter and LinkedIn.

Do you use suggestions? Here is another trick for our power-translators out there.

When you click on a suggestion, the text in the text area is replaced by the suggestion. Did you know that if you hold the Ctrl key (Command key on a Mac) while clicking on the suggestion, the suggested text is inserted where your cursor is?

We also have a lot of keyboard shortcuts for power-translators out there. Just press the H key anywhere on WebTranslateIt to see them.

This is the fourth episode of our new series of posts with short, useful tips showing you how to use some of the most advanced features in WebTranslateIt that maybe you didn’t know existed.

Do you find these tips and tricks useful? Let us know on Twitter @webtranslateit if you like this series of posts.

Related Posts

• How to use case-sensitive search and regex search with the new search bar
• Use a specific date in the filters
• How to quickly add a term to the TermBase