Detailed guide. An unofficial adaptation of User Guide 2.7. Source updated April 14, 2025; reviewed November 6, 2026. No running-Drupal procedure test has been performed.
Official source ↗ · Previous: 2.6 Editorial Workflow · Chapter 2 overview
Goal
Distinguish interface, configuration and content translation. Read data types , modules and 2.3 .
Adapted language concepts
Software starts from English, but a site can use another default language or offer multiple languages. The source identifies Language as the prerequisite for languages other than English. Translation completeness must be assessed for each information category.
Three translation targets
| Target | Examples and source modules |
|---|---|
| Interface | Built-in strings; Interface Translation, plus Update Manager for automatic translation downloads as described in the source |
| Configuration | Labels, site name, Views headers, automatic emails; Configuration Translation |
| Content | Text and file fields configured for translation; Content Translation |
Existing interface translations may be downloaded; default configuration translations can accompany them. User-created configuration has base values and translations. Content translation is configured per subtype and field, allowing some values to remain shared.
Why English may remain
The source distinguishes editing untranslated configuration from editing its translations. For example, Edit and Translate for a menu address different values. English in an administrative configuration screen is not by itself proof that translation is broken.
Our verification example
Classify a save button, site name, article body and article image. Record source language, translator and shared versus translated fields. Plan checks for labels and destinations as well as body text when switching languages.
Connection to changes
Verify the listed modules for the intended release. Advisories for optional translation integrations or language restrictions are not automatically advisories about this core concept. See the language chapter for procedure summaries and related extension notes.
This page adds no languages or translation downloads. Conceptual understanding and live behavior tests remain separate tasks.
Sources, credits and changes
Source: Drupal User Guide 2.7 ↗ . Contributors and source links listed in its Attributions: Jennifer Hodgdon ↗ . Refer to the source for writing, editing and adaptation roles, and to the guide-wide credits ↗ .
Copyright remains with the individual contributors; the official copyright page ↗ states © 2015–2025. Changes include reorganized explanations and procedures, our preparation and verification examples, troubleshooting notes, source-interpretation qualifications and release references. Original screenshots and videos are not reproduced. This adapted text is shared under CC BY-SA 2.0 . It is not an official edition or endorsement. This notice does not license unrelated articles or the site design.
Chapter navigation
Previous: 2.6 Editorial Workflow · Chapter 2 overview
Chapter 1 details · Chapter 3 · All chapters · Search official information