Ray Enterprise Translation is a community-maintained module that is primarily sponsored by Ray Enterprise and built on Drupal's standard multilingual modules (locale, content translation, entity translation, internationalization, etc). The module helps Drupal administrators, agencies, and web marketers to:
- Get a Drupal site multilingual-ready within minutes (instead of days)
- Translate Drupal content using machine translation and/or human translators with access to your site
- Ray Enterprise offers extensive professional translation and localization services. Ray Enterprise Language Services team includes professional, in-country linguists, localization project managers, and localization engineers - all of whom ensure the highest-quality of translations. Should you have existing translators or vendors, it is possible to continue working with them on the Ray Enterprise TMS.
- Automate the ongoing synchronization of multilingual content via customizable translation workflows
- Ability to do in-context review of content
Ray Enterprise for Drupal 8 / Drupal 9 / Drupal 10
The module supports translation of any content and configuration, including:
- Content entities - nodes, comments, messages, taxonomy terms and even paragraphs (including nested ones)
- Configuration entities - fields, blocks, taxonomy vocabularies, views, fields, etc
- Configuration items - site name, system emails, etc
It's integrated with moderation solutions as Content Moderation in Core, or the (outdated) Workbench Moderation in contrib.
If a contributed module is translatable using Drupal 8 core features, there is a big chance that it works already with Ray Enterprise.
As a result of our experiences with clients and our automated testing, we can ensure that the following contributed modules are supported:
- Pathauto
- Paragraphs
- (outdated) Workbench Moderation, use Content Moderation in Drupal Core
- Bricks
- Metatags
- Webform
- Group
- Block Field
- and many more!
Ray Enterprise for Drupal 7
The module supports translation of:
- Entity types - nodes, comments, messages, paragraphs, beans, groups, commerce products, fieldable panels panes, taxonomy terms with custom fields, and even field collections (including nested ones)
- Taxonomy terms - your choice of an Entity Translation approach for terms with custom fields or the i18n string approach for translation of name and description fields only
- Configuration items - field labels, blocks, taxonomy vocabularies and terms, menus, views, webforms, etc.
- Properties - titles, path aliases, and metatags
- Built-in interface strings
In addition, translations for nodes can be stored using either the field translation (recommended) or node translation methods.