QCDS Supported Languages: Current 20-Language Reference

List and explain the 20 bundled languages currently shipped for QCDS UI/recipient-facing content and how site/account/contact defaults interact with them.

This guide applies to All plans and follows the accepted QC Digital Signature 2.0.7 implementation. Where older walkthrough language differs from the current interface or source behavior, use the current QCDS state as the authority.

Before You Begin

Verify Joomla itself can send mail before troubleshooting QCDS message templates.
Keep supported template tokens intact; QCDS protects/restores tokens during rendering and translation.
Remember that QCDS maintains one authoritative creator-authored source rather than asking you to maintain a separate editable copy for every language.

Step-by-Step Workflow

Open the QCDS screen or record that owns the topic so you are reading the current state rather than an old screenshot or memory.
Compare the visible state with the current 2.0.7 rules described in this guide.
Identify whether the value belongs to global installation settings, one sender workspace, a reusable Template, or one immutable/sent Request.
Make changes only at the layer that owns the behavior.
Verify the result with a safe test and preserve historical Requests/evidence.

The 20 Bundled QCDS Languages

English — en-GB
French — fr-FR
Spanish — es-ES
German — de-DE
Dutch — nl-NL
Italian — it-IT
Portuguese - Portugal — pt-PT
Portuguese - Brazil — pt-BR
Polish — pl-PL
Czech — cs-CZ
Slovak — sk-SK
Danish — da-DK
Swedish — sv-SE
Norwegian Bokmål — nb-NO
Finnish — fi-FI
Romanian — ro-RO
Hungarian — hu-HU
Turkish — tr-TR
Greek — el-GR
Ukrainian — uk-UA

QCDS discovers these bundled runtime language catalogs and normalizes language selections to supported tags. If an unsupported Joomla language would otherwise be selected, QCDS falls back through its configured defaults and ultimately to en-GB.

List and explain the 20 bundled languages currently shipped for QCDS

Participant language is resolved at use time in this order: Contact Preferred Language, sender/workspace Default frontend language, administrator Default frontend language, then English (en-GB). QCDS can translate creator-authored participant communication when needed, while protecting tokens, URLs, and HTML. If safe translation is unavailable, it falls back to the complete frozen source message rather than sending a partially translated mixture.

For QCDS Supported Languages: Current 20-Language Reference, verify this behavior using the actual object involved rather than a generic assumption. A global administrator setting, a sender-workspace preference, a reusable Template, and a sent Request have different ownership and history rules. QCDS is intentionally designed so changes for future work do not silently rewrite the evidence of an already-sent transaction.

The current QCDS workflow preserves the intended result

To verify before relying on this behavior in production

How This Fits into the QCDS Workflow

QCDS resolves participant language at use time and can translate frozen creator-authored communication when needed. Historical deliveries keep their original evidence while later reminders or signer-page loads can use a Contact’s newly selected Preferred Language.

Treat translated communication as delivery-time presentation of a frozen creator source. That protects historical meaning and makes fallbacks deterministic if a translation provider cannot safely translate one message.

Verify the Result

The owning QCDS screen reflects the intended saved state after reload.
A direct follow-up test confirms the change affects future/current workflow behavior without rewriting historical sent Request evidence.

Common Mistakes to Avoid

Changing several unrelated settings before recording the original QCDS state.
Using old walkthrough behavior when it conflicts with the current 2.0.7 interface/source.

Troubleshooting

If the result differs from this guide, capture the current QCDS version, Status message, owning object ID/reference, and exact reproducible action before opening a support request.

Operational Best Practice

Test meaningful changes with controlled data before relying on them in production. Keep QCDS, Joomla mail, Scheduled Tasks, and entitlement health observable; preserve successful Requests and completed evidence; and make the smallest change that solves the actual problem. For handoff or support, record the QCDS version, relevant Request/Template reference, the exact action taken, and the visible result without including secrets.

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.