Source material to prepare
Provide screenshots, version details, file formats and the portions that must remain unchanged, including examples and placeholders.
Written translation
Make technical instructions understandable without altering code, identifiers or the approved names of interface features.
Provide screenshots, version details, file formats and the portions that must remain unchanged, including examples and placeholders.
Decide which wording should match the live interface and who will verify the translated help against the product.

Before requesting translation of software documentation, match the source to the recipient’s instructions. A photocopy, updated record and working draft can all have the same title. Include the current release guide and approved screenshots where applicable and say which file needs translation. If you include reference material to explain what a page means, mark it as reference so that the quoted scope and the actual order stay aligned.
With software documentation, several pages can be part of one record even when they are scanned separately. Give the files a sequence and explain what belongs together before upload. It is especially useful to identify translatable instructions versus commands and unreleased labels. If a page cites an insert you don’t have, tell us whether the recipient requested that insert or whether you are only submitting the pages already available.
Look through the scans of your software documentation on a full screen before you send them. Page edges, old impressions, issued dates and handwriting can fade or disappear in a thumbnail. When a detail is hard to read, upload a closer image as a supplement. If target users will see different controls depending on account permissions, include an explanation before review so that the files are handled as a deliberate set.
If software documentation contains a name or term that already appears in other records, provide the spelling and point to the matching reference. Tell us which forms of a company name or address must stay recognizable. A short note beside the upload is easier to review than a renamed file, and it keeps those choices separate from what was actually printed on the source.
Confirm who will receive the translation of software documentation and ask whether they expect a digital file, a paper copy, an accuracy statement, or their own form. Some requests arrive with a list of exhibit or file names; share it early if format matters. Set a date for your own check as well as the submission date. Mailing time and a recipient’s review window are separate decisions.
When the translation of software documentation is ready, set the source and finished files next to each other. Check names, identifiers and the sequence of attachments first. If anything differs from what you expected, cite the page and the item in question. This is particularly helpful if target users will see different controls depending on account permissions. Keep the completed translation and its matching source together for later reference.
Send the version the receiving organization expects to review. Include the current release guide and approved screenshots if it belongs to the requested record and mark any additional material that is there to provide context.
A clear scan or photograph of software documentation can help us review your request. Include every side with relevant text, show the paper edges, and add a close-up if an entry is difficult to read.
First check whether a clearer or complete copy is available. If you cannot find one, tell us which part is affected. This is especially useful when the reader relies on translatable instructions versus commands and unreleased labels.
Ask the organization that will receive your software documentation for its instructions. If it calls for an accuracy statement or a particular form, pass along the exact wording before your order.
Yes. Supply the existing spelling as a note and identify the name in the software documentation. A passport or other familiar reference may help, provided it is appropriate to share.
Confirm what the recipient needs before sending your software documentation. Use the designated upload flow and explain how any permitted redactions affect the sections being translated.
List the filenames and order the recipient expects. If target users will see different controls depending on account permissions, note that before ordering so we can review the materials and handoff together.
List each source and target language you need for your software documentation. Also say who will use each version; terminology, signs of certification and delivery instructions may differ.
Reference the file, page and entry when you ask for a review of your software documentation. If the source itself has been reissued, identify the corrected version so we can distinguish it from a translation adjustment.
Submit the files in scope, preferred delivery date, language pair and recipient instructions. Note whether the current release guide and approved screenshots is part of the quoted translation or only included for context.