Skip to content

docs(import): update the supported formats for the Unify Placeholders… #553

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
andrii-bodnar merged 2 commits into from
Dec 23, 2025
Merged

docs(import): update the supported formats for the Unify Placeholders… #553

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9686060
docs(import): update the supported formats for the Unify Placeholders…
rohalskyy Dec 23, 2025
8cb9010
section text rewrite
rohalskyy Dec 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions src/content/docs/crowdin/project-management/project-settings/import.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,13 +18,9 @@ Improve the translation consistency and streamline your workflow by unifying pla

### Unify Placeholders

Enable the transformation of the placeholders to the unified format to improve the work with TM suggestions. On export, the placeholders in translations are transformed back to the original format.
Enable this option to transform placeholders into a unified format within the Editor (e.g., displaying both Android `%s` and iOS `%@` as `[%s]`). This improves Translation Memory efficiency by making suggestions completely interchangeable across platforms.

If your project contains iOS strings, iOS XLIFF, and Android XML files, you can enable the **Unify placeholders** option, and the system will transform placeholders into a unified look. For example, Crowdin will make the Android string `Hello, %s!`, and the iOS string `Hello, %@!` look in the Editor this way: `Hello, [%s]!`.

This option is beneficial when you work with TM since TM suggestions from iOS strings, iOS XLIFF, and Android XML will be completely interchangeable.

Crowdin will transform the translation placeholders back to the original format on export. This option only applies to iOS strings, iOS XLIFF, and Android XML formats.
On export, placeholders are converted back to the original syntax. This feature applies only to Android XML, iOS strings, iOS XLIFF, and Apple Strings Catalog.

### Duplicate Strings

Expand Down
8 changes: 2 additions & 6 deletions src/content/docs/enterprise/project-management/project-settings/import.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,13 +20,9 @@ Improve the translation consistency and streamline your workflow by unifying pla

### Unify Placeholders

Enable the transformation of the placeholders to the unified format to improve the work with TM suggestions. On export, the placeholders in translations are transformed back to the original format.
Enable this option to transform placeholders into a unified format within the Editor (e.g., displaying both Android `%s` and iOS `%@` as `[%s]`). This improves Translation Memory efficiency by making suggestions completely interchangeable across platforms.

If your project contains iOS strings, iOS XLIFF, and Android XML files, you can enable the **Unify placeholders** option, and the system will transform placeholders into a unified look. For example, Crowdin Enterprise will make the Android string `Hello, %s!`, and the iOS string `Hello, %@!` look in the Editor this way: `Hello, [%s]!`.

This option is beneficial when you work with TM since TM suggestions from iOS strings, iOS XLIFF, and Android XML will be completely interchangeable.

Crowdin Enterprise will transform the translation placeholders back to the original format on export. This option only applies to iOS strings, iOS XLIFF, and Android XML formats.
On export, placeholders are converted back to the original syntax. This feature applies only to Android XML, iOS strings, iOS XLIFF, and Apple Strings Catalog.

### Duplicate Strings

Expand Down