Edit strings

Use Strings to inspect source text and correct a target translation. Saving creates a new accepted translation version. Your app receives that wording after a catalog containing it is published.

1. Find the string

1. Select your project and environment, then open Strings.
2. Choose one target language or All enabled languages.
3. Search by source text or string key, or narrow the view by status or source file.
4. Open the string to inspect its source text, placeholders, context, source locations, and translation history.

The list follows the latest ready build in the selected environment. If it is empty, first upload your application text. Change source wording in the repository and upload a new build; the editor changes target translations.

2. Correct the target text

Read the original text and any matching glossary terms. Enter the target wording, optionally add a note, and choose Save version. Use suggestion copies a memory suggestion into your draft; Discard edit restores the saved draft base. You can use translation-memory suggestions as a starting point, but check that they match the current context.

Preserve every placeholder and named rich-text slot. For example, the sample source Welcome, {name} still needs {name} in the target. ICU plural syntax must remain valid. The application owns link destinations; translations can rearrange the named slots.

If the server rejects the edit, follow its validation message. Missing placeholders, invalid ICU, changed rich slots, and glossary violations must be corrected before saving. A length warning can remain attached to an accepted human edit.

3. Resolve review decisions

Use Review to approve, reject, or keep source wording for pending translations. You can select multiple items for a shared decision. Bulk results can include failures for individual items; inspect them before continuing.

• Approve accepts a new version for catalog preparation.
• Reject keeps that wording out of an accepted catalog and requires further work.
• Use source explicitly accepts the source wording for that target string.

In Strings, Approve selected and Reject selected act on selected reviewable versions. Use source is available in Review. The Strings filter labels accepted versions Ready; this is a string state, not confirmation that a complete catalog or published release exists. An accepted string can still be shown in its history after the pending item leaves the queue.

4. Check readiness, then publish

Saving and approval rebuild eligible catalogs. A catalog becomes ready only when the required strings are usable. Open Releases and inspect the ready catalog before choosing Publish ready catalog. A successful edit can remain saved even if catalog rebuilding fails; that does not mean it is ready or published.

An edit never changes the text inside an already published catalog. Restoring an earlier release selects its recorded catalog and preserves newer versions.