What QCDS Translates and What It Does Not

QCDS deliberately separates translated presentation from authoritative transaction content. Interface labels and selected creator-authored communication can be localized for the recipient, while source documents, Request identity, signer values, and other evidence remain unchanged.

QCDS-Owned Interface Text

QCDS ships local runtime/UI language catalogs for its own controls, instructions, statuses, buttons, and standard signer field labels. The browser-side UI translator is intentionally scoped to QCDS-owned control surfaces and skips known customer-content areas.

For example, QCDS can localize its signer-page title and standard field wording without replacing a customer-authored Request title.

Creator-Authored Email Content

The frozen source for QCDS email templates—including subject, plain text, and enabled Custom HTML—is eligible for protected runtime translation when the recipient's language differs from the source language.

Request-specific Signer Invitation edits become part of that Request's frozen creator-authored source. Translation creates recipient-facing output; it does not publish those edits back to the reusable template.

Creator-Custom Signer Field Labels

Standard QCDS field labels come from the local language catalog. A creator-custom field label can receive a signer-facing translated display label. QCDS batches those custom labels for bounded protected translation, caches the proven result, and falls back to the immutable source label if translation is unavailable.

The translation is a display derivative—the field's frozen source label is not rewritten.

Customer and Transaction Content QCDS Does Not Rewrite

QCDS does not use its UI-localization layer to rewrite customer-authored names, Request titles, document titles, or typed user content. The secure signer app explicitly avoids replacing the customer-authored Request title.

QCDS also does not machine-translate the source PDF into a different legal document. Completed PDFs are generated from the frozen PDF pages plus final field values, attachment presentation pages when used, and the appended Audit Trail.

Signing Evidence Remains Authoritative

Signatures, initials, signer-entered values, timestamps, hashes, identity-verification evidence, delivery history, and the immutable Request snapshot are preserved as transaction evidence. Language selection may change how QCDS presents surrounding UI or communication, but it does not rewrite those recorded facts.

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.