Product Localization

Hand over translation files with their variables, context and decisions intact

Prepare PO and XLIFF exports with protected elements, context and a known return route, then check the returned language and its behaviour inside the product.

The Arabic Studio Editorial Team22 Nov 202620 min read
Two women discussing beside a large office window, with an open laptop and a closed laptop.
A discussion with a computer at hand. Stock illustration: Christina Morillo / Pexels.

Send PO or XLIFF translation files with a clear reference version, instructions for protected content, useful screen context and a way to resolve questions. Agree what should return, then check both the returned file and the text inside the product. Fluent Arabic alone cannot show that a variable survived, a review question was answered or the correct release received the work.

You do not need to write software to organise this handover. You need a shared understanding of which parts are language, which parts connect that language to the product, and who checks each. This guide explains translation files from that buyer’s perspective, including what to ask when the export looks unfamiliar.

Identify what the translation files will produce

Begin with the destination: an application, website, help system or another defined output. Name the release and the target Arabic locale agreed for that product. “Arabic” can describe a language requirement without specifying every technical setting. Ask the product owner to confirm the locale value the receiving system expects, rather than inventing one in the translation files.

State what work is being requested. New translation, revision of existing Arabic and checking previously approved content are different tasks. Mark entries provided only as reference. If the translation files combine these categories, the language team should be able to distinguish them without interpreting the age of each sentence as an instruction.

Also identify the person who imports the return. That person can confirm the export settings and organise a small return test when needed. A handover becomes more practical when the recipient of the translation files knows who can answer a format question, rather than being passed between a project manager and an unidentified technical team.

What PO and XLIFF translation files mean in plain language

A PO file is an editable collection connecting source messages with translations. The GNU gettext manual explains source and target entries, comments, context and plural forms. For a buyer, the important point is that PO translation files carry more than a list of sentences: their structure helps the product find the right translated message.

XLIFF is an exchange format used to move localisable content through translation workflows. Think of it as a structured package containing source and translated material, with information the participating tools may need. The OASIS XLIFF 2.1 specification describes notes and inline codes, including content representing formatting or placeholders. This is a specific published reference, not a claim that all XLIFF translation files use the same version.

Neither extension tells you the whole workflow. Ask which version and tool produced the export, which application should receive it, and whether supporting material is needed. Do not convert translation files merely because another extension looks more familiar. A readable spreadsheet can be useful for review while still being insufficient as the file that must go back into the product.

Confirm the export before sending the whole batch

Ask the technical owner to open a representative export in the intended translation tool and return a small sample through the agreed route if compatibility is uncertain. Choose entries with ordinary text, a protected variable and any relevant formatting. This tests the path translation files will follow without making the language team discover a basic import problem after completing the batch.

The check should answer concrete questions. Can the target language be entered and exported? Does the receiving system recognise the returned units? Are notes visible? Do protected elements remain usable? Opening translation files successfully in one editor does not establish that a different application will reconstruct the finished content correctly.

Record the working settings once confirmed. Keep a copy of the actual export, not just a screenshot of a successful dialog. If a tool changes later, reconsider compatibility rather than treating the earlier test as permanent proof. The aim is a known route for these translation files, not a general endorsement of a product or format.

Inventory the translation files without renaming the sources

Keep original filenames exactly as received, including spaces, punctuation and identifiers. Use a separate inventory to explain their roles. You might identify a file as “checkout messages” without changing its actual name. This makes translation files easier to match with the release record and prevents a helpful-looking rename from breaking a downstream expectation.

List the source language, target language, export date, release reference and requested treatment for each file. Note whether a companion package, reference copy or existing translation is included. Count meaningful units when that helps the team compare the return, but explain what the count includes. A raw line count in translation files does not necessarily equal the number of user-facing messages.

Keep superseded exports outside the active working set, with their status visible. When two files have the same name, their separate folders and inventory references must distinguish them. A translator should not have to guess which of several attachments is the active set of translation files because the final email happened to mention one of them first.

Hands typing on a laptop with green technical text on a dark screen, viewed from above.
Keep translation files connected to their source version and context. Working with a structured digital file. Stock illustration: Sora Shimazaki / Pexels.

Identify protected elements in the translation files

Some visible items are instructions to the product rather than words for the user. A placeholder may be replaced by a person’s name, an order reference or a number. Explain which tokens are protected and what changes the workflow permits. In translation files, changing the spelling of such a token can be different from changing the surrounding sentence.

Do not rely on a general “keep all symbols” instruction. Ordinary punctuation may need language editing, while a particular brace, identifier or escape sequence may need exact preservation. Ask the technical owner to identify the relevant conventions. If the tool protects placeholders automatically, confirm what it protects and what remains ordinary editable text in the translation files.

For a fictional message such as “Your order {order_id} is ready,” document that {order_id} receives an order reference and is not to be translated. The example illustrates a convention; it does not prescribe that syntax for your software. Translation files from another system may use a completely different way to represent the same idea.

Explain variable values in the translation files

Protection and understanding are separate needs. A translator can preserve a token perfectly while misunderstanding the value that appears in its place. Provide a safe representative value and explain its meaning. Translation files should distinguish a number of orders from an order number, because the surrounding Arabic may need different wording.

Use synthetic examples where real data is unnecessary. A sample reference such as ORD-204 can expose mixed Latin letters, punctuation and digits without disclosing a customer’s details. Explain that it is invented. Keep the exact example unchanged in discussions so reviewers of the translation files know whether they are looking at the same test case.

Ask about optional or empty values as well. A greeting built around a name can look acceptable when the name is present and become awkward when it is missing. The language team can suggest a wording approach, but the product owner must confirm which situations actually occur. Translation files need the behaviour of the field, not guesses based on its label.

Preserve what tags do in the translation files

An inline marker may represent formatting, a link or another element reconstructed by the workflow. Explain its purpose in ordinary language. Is the enclosed phrase a button label? Does a pair mark a linked destination? Translation files should give the linguist enough information to keep that relationship while forming a natural Arabic sentence.

Preserving function does not always mean copying English word order. A supported tool may allow certain codes to move with the phrase they belong to; other codes may have restrictions. XLIFF provides editing constraints for inline codes, but the export and receiving workflow determine the practical task. Do not tell a reviewer to delete awkward markers from translation files simply to make the sentence easier to read.

If a marker looks broken or its role is unclear, ask the technical owner. A paired element, a standalone placeholder and ordinary visible punctuation are not interchangeable. The returned translation files should pass the appropriate structural checks, with any approved exception explained. A screenshot of clean Arabic text alone cannot show that a link or formatting boundary survived.

Two people seated together in a grey high-backed booth looking at a laptop.
Reviewing material together before the next handover. Stock illustration: Thirdman / Pexels.

Attach useful context to the translation files

Short strings need a task, not just a dictionary equivalent. “Open” might be a command or a status. A nearby number may be a quantity, a reference or a duration. In the context accompanying translation files, identify the screen, the user action and the result the person should expect.

Screenshots help when they show the relevant state. Label the entry or provide a clear mapping to its identifier; a folder full of unnamed images creates another search task. Include the error state or empty result if that is where the message appears. Translation files are often extracted without the surrounding words that make their purpose obvious in the product.

Our guide to Arabic app-string context develops the language briefing in more detail. Here, connect that context to the units in the actual handover. The translation files and their explanations must remain traceable together, even when the translator is working in a tool that displays translation files in a different order from the interface.

Keep identity separate from editable language

A technical identifier helps a system or reviewer locate content. It may look like English, but that does not automatically make it a phrase to translate. Identify the permitted editing area and keep the source identifiers intact unless a separate authorised change is requested. Translation files should not acquire new identifiers as an incidental result of language polishing.

For PO content, do not assume every repeated source phrase is redundant. Context can distinguish different uses. For other exports, ask how the receiving tool identifies each unit. A reviewer who removes apparently duplicate lines from translation files may accidentally remove a distinct message that the product still needs.

Likewise, distinguish a real product name from an internal label. The language team may need an approved Arabic product name, while an internal reference remains unchanged. Give each its own instruction. Maintaining identity in translation files is not an instruction to leave all English untouched; it is a way to identify precisely which text serves which role.

Plan plural cases before treating the file as complete

English singular and plural wording does not describe every Arabic message pattern. Confirm how the product represents quantity-dependent messages and what forms the translator is expected to supply. Translation files can expose separate cases, but the language team still needs the noun, surrounding sentence and meaning of the number to write them appropriately.

Unicode’s plural-rule guidance explains that category names describe number-dependent behaviour and are not simply labels to interpret by their everyday English meanings. Ask the technical owner which plural mechanism the product uses. Do not paste a formula from another project into translation files on the assumption that every application selects its messages in the same way.

Prepare representative test values that exercise the implemented cases. Include zero and relevant larger values where the message supports them; include fractions if the product can genuinely produce them. The owner should explain the expected coverage. A checklist for translation files that asks only whether every visible field contains text may miss a case the interface later displays incorrectly.

Give questions a place outside the displayed message

Do not put “please confirm” into a target field that could appear to users. Keep unresolved questions in the agreed notes or issue record, linked to the file and unit. Translation files may carry notes, but confirm that the intended participants can see them and that they are not being mistaken for publishable wording.

A useful question states the uncertainty and the consequence. “Does ‘return’ mean refund the purchase or go back to the previous screen?” is actionable. Attach the relevant context and a proposed interpretation if helpful. For translation files, that question can be resolved once and then checked against related messages instead of being guessed independently in each place.

Name an answer owner and record the decision where the language team will find it. A reply in a private conversation should be transferred into the shared project record when authorised. Otherwise, the next reviewer may reopen the same issue or apply an older answer to the translation files without knowing that the product behaviour has changed.

A woman in a pale green jumper writing in a notebook beside a laptop.
Check translation files in the tool and in the product. Keeping questions and notes close to the working file. Stock illustration: Liza Summer / Pexels.

Understand review states without treating them as approval

A target field in translation files can contain words and still need revision. GNU’s documentation on fuzzy PO entries explains that an entry may be flagged for further translator review, including after a source update. Translation files should therefore be checked for both content and relevant workflow states, rather than being declared complete because no cell appears blank.

Ask what each status means in your tools and who may change it. Do not assume that similarly named states in different systems are equivalent. A language review, a technical acceptance and a release decision may happen separately. Keep those responsibilities visible in the record accompanying the translation files.

Avoid clearing warnings or changing states solely to make a dashboard look finished. Investigate the entry, resolve the question and apply the appropriate status under the agreed process. If an item remains open, identify it explicitly. The recipient of translation files needs an honest account of remaining work, not a misleading completion percentage.

Manage changes to translation files while work is underway

Agree how new wording reaches the language team. Send an identified update and explain whether it replaces the previous export or adds to it. Translation files arriving through several channels can leave people editing different baselines, especially when the filenames remain identical and only an attached message describes the difference.

Mark new, changed and removed material using the agreed workflow. Keep approved translations available where they remain applicable, but do not assume they fit modified source text. A changed condition can alter the Arabic even when most words are unchanged. Translation files should preserve the relationship between the source revision and the review it requires.

If an urgent change affects a message already under review, name it explicitly and check related entries. A button label may appear in help text or a confirmation message too. The team should decide the scope of the update. Sending one corrected sentence outside the translation files does not automatically update every place where it is used.

Keep reviewer edits inside the agreed return path

A stakeholder may prefer to review Arabic in a readable document or on a screen. That can work, provided each requested change maps back to the correct file and unit. State who applies approved comments to the translation files. Otherwise, a polished review document can coexist with an unchanged production export.

Ask reviewers to distinguish an error, a preferred term and a new product decision. A request to change “cancel” to “close” may affect the action rather than merely its style. The owner needs to confirm that distinction before the language is updated. Translation files should preserve the intended behaviour, not silently resolve a disagreement about what the interface does.

Keep the approved wording and the reason together for important decisions. Our translation feedback guide explains a practical issue record. In this workflow, the crucial final step is verifying that the resolved decision appears in the returned translation files and later in the product, rather than only in the reviewer’s notes.

An open hand holding a small metal USB flash drive, with a laptop blurred behind it.
One example of a physical storage device. Stock illustration: Anete Lusina / Pexels.

Check the returned translation files before import

Start by matching the return to the inventory: expected filenames, languages, release reference and agreed deliverables. Open the actual files with the appropriate tools. A successful download or a document preview does not demonstrate that translation files parse correctly or belong to the export you commissioned.

The technical check should examine protected tokens, required code relationships and any relevant format validation. The language check should examine the approved source, Arabic text, terms and resolved questions. These checks have different purposes. Translation files can be structurally valid while containing an inaccurate message, or linguistically sound while failing an import because something structural changed.

Review additions, omissions and unresolved states against the agreed scope. Do not automatically delete every target that equals the source: a brand, identifier or approved retained term may legitimately stay unchanged. Conversely, identical source and target can also reveal missed work. Investigate the entry’s purpose in the translation files before deciding which explanation applies.

Test the language with realistic product values

Import through the agreed test route and inspect representative screens. Use safe values that exercise names, references, numbers and the implemented plural cases. Translation files are an intermediate deliverable; the interface combines them with data, layout and behaviour that may not be visible in a language editor.

For Arabic, inspect mixed-script references, punctuation and directional behaviour without reversing stored characters by hand. A truncated message or misplaced value may require a design or implementation decision. Record the actual state and expected result so the team can reproduce it. Do not “repair” translation files in a way that conceals the underlying product problem.

Check that actions still mean what the user will do. A confirmation prompt, its buttons and the result need to agree. If a label was approved in isolation, this is where a contextual mismatch may emerge. The return test should send relevant findings back to the owner of the translation files, with a clear decision about any correction and retest.

A fictional handover with a missing quantity case

Imagine a fictional booking tool whose English export contains a message about selected rooms. The Arabic translation files arrive with readable text, intact variables and no import error. During a test using two rooms, the reviewer notices that the displayed message uses wording intended for a different quantity. The translation files opened correctly, but the tested output still needs investigation.

The team checks the expected case selection and discovers that the export did not expose one case the implementation requires. The technical owner corrects the export process; the language team supplies the missing wording with context. Nobody invents an extra field manually in the translation files merely because it seems like the simplest way to finish.

They then repeat the relevant quantity tests and record which file replaced the previous return. This scenario is entirely invented. It illustrates the difference between translated fields, structural acceptance and behaviour in the product. The exact defect in real translation files could be different, so the observed symptom should guide investigation rather than an assumed diagnosis.

Return a package that explains what is ready

Keep the deliverable modest and explicit: the agreed translation files, a concise record of resolved and open questions, and any requested review evidence. Preserve filenames and separate explanatory material from production content. Identify the active set and the baseline it matches so the recipient can continue without reconstructing the project from email history.

Confirm who has approved the language, who has checked the import and what remains before release. If the interface test has not happened, say so. Our guide to translation file access and versions covers the surrounding sharing process; neither a shared folder nor a successful upload proves that the content has passed the agreed checks.

To discuss Arabic website and application localisation, provide a representative export, the product context and the intended return route. Include any known restrictions or unresolved format questions. That gives the team a concrete basis to assess the translation files and define the work before a complete batch is sent.

Questions frequently asked about translation files

Can we send screenshots instead of PO or XLIFF translation files?

Screenshots are valuable context, but they usually do not preserve the structure the product needs for import. Send the actual export when it is the agreed production format, with screenshots mapped to relevant entries. If no export is available, discuss another workflow explicitly. Do not assume that translating the visible screen creates usable translation files or covers messages shown only after errors, empty states or different user actions.

Should translators edit the English identifiers as well as the Arabic?

Only when a separate authorised task explicitly requires it. Identify the editable language fields and the content that must remain intact. An identifier can look like ordinary English while serving as a technical reference. Translation files should preserve that reference through the language workflow. If an identifier is misleading, report the problem to the product owner instead of renaming it as part of a stylistic correction.

Can a placeholder move within the Arabic sentence?

It depends on the placeholder and the workflow’s permitted operations. Arabic word order may require a different position, but some codes have constraints. Ask the technical owner to explain the token and use the supported editor correctly. Translation files should retain the token’s identity and function. Do not translate its name, duplicate it or delete it simply to make the sentence look natural in isolation.

Does a populated target field mean the entry is finished?

No. It may contain an old translation, provisional wording or a status that requires review. Check the source revision, workflow state, language and outstanding questions. For translation files, completion should describe the agreed checks actually performed. A progress indicator can help manage work, but it cannot by itself confirm that every term is correct, every protected element survived or the interface behaves as intended.

Do all XLIFF translation files work in the same tools?

Do not assume that they do. Confirm the version, export settings, relevant features and receiving application, then test a representative return if compatibility is uncertain. A file extension names a format family, not proof of a complete working route. Keep the actual sample and settings with the project record. There is no need to convert translation files merely to use the newest-looking version name.

Who should answer a question about an ambiguous button label?

The person who knows the product behaviour should confirm the action, while the language reviewer chooses appropriate Arabic for that confirmed meaning. Link the question to the file, unit and relevant screen. If the answer changes the product decision, record that separately from a language correction. Translation files should receive the approved result through the agreed route, with related messages checked where necessary.

What should we do if the returned translation files fail to import?

Keep the received translation files and capture the import message, application and baseline. Ask the technical owner and language supplier to investigate the actual failure before editing content at random. A format issue, incompatible setting or unexpected structural change may need a different remedy. After correction, repeat the relevant checks and identify the replacement clearly. A readable Arabic preview does not resolve a failed import by itself.

Sources & further reading

About The Arabic Studio Editorial Team

Put it into practice

Ready for your next project?

Explore our Website & App Localization service or tell us what you need.

Explore the service ↗