QCDS Supported Languages: Current 20-Language Reference

QCDS 2.0.7 currently ships runtime language catalogs for 20 languages. QCDS discovers these installed catalogs at runtime and uses them for its own interface/notification language plus recipient-facing language resolution.

Current Bundled Languages

  • cs-CZ — Čeština
  • da-DK — Dansk
  • de-DE — Deutsch
  • el-GR — Ελληνικά
  • en-GB — English (United Kingdom)
  • es-ES — Español
  • fi-FI — Suomi
  • fr-FR — Français (France)
  • hu-HU — Magyar
  • it-IT — Italiano
  • nb-NO — Norsk bokmål
  • nl-NL — Nederlands
  • pl-PL — Polski
  • pt-BR — Português (Brasil)
  • pt-PT — Português (Portugal)
  • ro-RO — Română
  • sk-SK — Slovenčina
  • sv-SE — Svenska
  • tr-TR — Türkçe
  • uk-UA — Українська

How QCDS Chooses a Participant Language

For current signer pages and recipient emails, QCDS resolves language dynamically in this order:

  1. the current preferred language on the linked Contact;
  2. the current workspace Default frontend language;
  3. the current QCDS/Joomla global frontend language; then
  4. en-GB as the final fallback.

The language/locale captured when a participant was sent remains historical evidence, but it does not prevent a corrected Contact preference or later workspace default from affecting later recipient-facing loads/messages.

One Authored Email-Template Set, Not 20 Copies

Each sender/workspace uses one authoritative authored Email Template source set. When a Request is sent, QCDS freezes that source. For a recipient who prefers another supported language, QCDS translates the frozen creator content for that recipient instead of asking the sender to maintain a separate editable template set for every language.

Translation is atomic and fail-soft. If one field cannot be translated successfully, or a translation engine/version changes during the same template bundle, QCDS falls back to the exact source-language bundle rather than sending a mixed-language message.

Built-In QCDS Text Uses Installed Catalogs

QCDS-owned interface and built-in notification labels come from the installed language catalogs. Creator-authored Subjects and message bodies are separate content and use the Request-time translation path described above.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.