Translation process

Login.gov is currently available in English, Spanish, and French. This guide covers the tools available to translate the application, and the processes around introducing and translating new strings.

Translating content guidance

Content on secure.login.gov and login.gov is offered in the following languages:

  • English (U.S.)
  • French (Canada)
  • Spanish (Mexico)

Translations are requested when content is added or updated on secure.login.gov and login.gov. You can find specific guidance on how to request translations in the Login.gov guidance document.

NOTE: partners.login.gov and developers.login.gov are not expected to be translated.

Internationalization APIs

All strings shown to a user should be localized. This can be achieved for both server-rendered views, as well as front-end JavaScript code.

In both cases, strings are defined within the files of config/locales. Each folder should cover a domain area of the application, roughly aligning to controllers found in app/controllers. Translation files should always exist for all supported locales, and should always include the same YAML structure. In both Rails and JavaScript, a string will be referenced by a dot (.)-separated key representing the YAML nested dictionary path.

Server-side

Login.gov uses Rails’ default internationalization (i18n) API.

Translate a string using the t (translate) method:

t('doc_auth.buttons.start_over')

Front-end

Login.gov uses a custom JavaScript implementation providing basic support for a Rails-like t translation function.

For strings to be available to translate in the front end, you must first add the key to the array of keys found in config/js_locale_strings.yml.

The translated result of the key can be retrieved using the window.LoginGov.I18n.t method:

const { t } = window.LoginGov.I18n;

console.log(t('doc_auth.buttons.start_over'));

Updating strings

As new screens are added or existing views are updated, the set of localized strings should be kept in sync with what’s used in the code. This includes the removal of strings which are no longer used, but more often than not, you will find yourself adding new strings.

When should strings be added?

Content will change through the process of design iteration and feedback. It is up to the team’s discretion when to add strings to config/locales, as opposed to using temporary text in an in-progress implementation.

Note:

  • To avoid mistakenly leaving text as untranslated, it can help to introduce the string sooner rather than later.
  • The naming of the string key should ideally be generalized enough to not be tightly coupled with the exact text, which can improve resilience to changes in copy.

How should strings be added?

It’s perfectly acceptable to manually create and arrange locale files and the strings within them.

You can also take advantage of some automated tooling to assist in this process: