Make a software-string enquiry understandable outside the codebase

Preserve the structure while adding context

Record the source and target languages, intended audience and file format. Ask for string identifiers, context notes and authorised screenshots where available. Mark placeholders, variables, tags and values that must not be changed. Mention any length restrictions and plural or gender-related context supplied by the product team.

Keep the original export intact and describe the expected return structure. If the client needs a review in the implemented interface, list that separately from translating the text file. Do not assume development or platform access is part of the language service.

Define who resolves product questions

Identify a reviewer who can explain ambiguous actions, product terminology and release constraints. Note whether the source is frozen for the release or still changing. Consolidated answers help prevent inconsistent interpretations across related strings.

Introduce the requirement with the client's permission for Enuncia review. Agencies can explore a referral partnership for these projects, while availability, production scope and eligible commission are confirmed through the applicable agreements.

Keep exploring

• Scope an ecommerce language enquiry beyond product descriptions
• Do not leave navigation and form messages out of a website language brief
• Build a compact context pack for a localisation enquiry