Language Translation with DITA

DITA's modular and structured format makes it ideal for translation and localization.

How DITA Supports Translation

DITA supports translation in the following ways:

  • Clear content boundaries: Topics and maps provide distinct units for translation.
  • Shared reusable components: Elements like warnings, steps, or standard messages only need to be translated once.
  • Conditional text: Content filtered by audience, platform, or product can be managed efficiently for translation.
  • Language attribute support: DITA supports the xml:lang="fr" attribute for specifying content language.
  • translate="no" attribute: DITA allows exclusion of specific content from translation, for example:
    • Brand names
    • Code snippets
    • Non-translatable strings or sample outputs
    Sample XML snippet: 
    
<p translate="no">Use the command: `init -d config.yaml`</p>

Customizing Output Formats

DITA enables deep control over content presentation via publishing pipelines or style tools.

  • PDF styles: Modify XSL-FO templates or use visual editors for branding and accessibility.
  • HTML output: Customize CSS, JavaScript, and templates for branded and responsive web layouts.
  • DITA-OT plugins: Extend or override default behaviors for custom outputs.
  • Content delivery portals: Apply filters, UI themes, and search tuning.

Common use cases for customization:

  • Branded headers and footers
  • Embedding accessibility features
  • Responsive layouts for mobile
  • Separate guides per product variant

The publishing strategy should align with audience needs and platform capabilities.