XLIFF 2.1: Inline Codes and Placeholder QA

XLIFF 2.1: Inline Codes and Placeholder QA

Choose one answer. All questions are included, with explanations after checking. No time limit. Training target: 21/26. Diagnose XLIFF 2.1 inline-code permissions, copying, original-data references, spanning codes, reordering, text placeholders and round-trip failures. For localization engineers and technical reviewers working with a pipeline explicitly configured for 2.1. Excludes XLIFF 2.2-specific behavior, complete schema authoring, vendor-specific extensions and translation certification. XML fragments assume the XLIFF 2.1 document namespace unless stated otherwise. Sources: https://docs.oasis-open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.html https://support.crowdin.com/enterprise/project-settings/qa-checks/ https://www.w3.org/TR/REC-xml/
1 of 26
An extractor represents an atomic {account} substitution as <pc id="v">{account}</pc>, allowing translators to edit text inside it. Which representation best fits this standalone substitution?