Q: How are nested structures handled with Format Conversions?

Some formats, like JSON or YAML , support nested structures in translation files. Localazy’s Format Conversions preserve these nested structures during conversion. When converting from a format that supports nesting to one that does not (such as from JSON to XML ), Localazy flattens the structure to ensure compatibility without losing any translation data.

Question 1

Which localizable file format conversions do you support?

Accepted Answer

Localazy supports all major format conversions from Android XML and iOS .strings through multilingual JSON to XLIFF, qt-ts, and many more formats. You can learn more about supported file format conversions in the documentation.

Question 2

How can I convert different localization file formats?

Accepted Answer

In the File Management section of Localazy, when downloading your files, you can select the desired format and download your strings in any of the available file formats.

Format Conversions feature is also an integral part of the Localazy CLI tool, so if you want to automate format conversions, you will need to install Localazy CLI on your preferred platform.

Read the article: How to convert localization files into different formats?

Note: Format Conversions are available only as a part of the Professional plan

Question 3

How can I use Format Conversions for multiplatform development?

Accepted Answer

Format Conversions in Localazy allow you to convert translation files between different formats, making it easier to manage translations across multiple platforms. For instance, if you’re developing an app for iOS and Android, you can easily convert between .strings (iOS) and .xml (Android). This eliminates the need to manually maintain translations for each platform, saving time and reducing the risk of errors.

Question 4

How are placeholders handled with Format Conversions?

Accepted Answer

Format Conversions support placeholders across various formats, but their syntax can differ between platforms. For example, in Android, placeholders are typically in the format %1$s, while in iOS, they use %@. Localazy automatically converts these placeholders to the appropriate format for the target platform, ensuring that your translations work correctly without manual adjustments.

Question 5

How are nested structures handled with Format Conversions?

Accepted Answer

Some formats, like JSON or YAML, support nested structures in translation files. Localazy’s Format Conversions preserve these nested structures during conversion. When converting from a format that supports nesting to one that does not (such as from JSON to XML), Localazy flattens the structure to ensure compatibility without losing any translation data.

Question 6

How are plurals and arrays handled with Format Conversions?

Accepted Answer

Plurals and arrays are managed differently across platforms, but Localazy automatically handles these conversions for you. For example, Android uses specific plural keys (one, other), while iOS handles plurals with string tables. Localazy’s Format Conversions ensure that plurals and arrays are correctly mapped and formatted to suit the target platform’s specifications.

Find out more about Format Conversions in our documentation.

Features

💡 Enough theory, try Localazy now! 🚀