Localizar cadenas y String Catalogs

Localization translates your app's text so people read it in their own language. It widens your audience around the world. 🌍

In SwiftUI, a Text("Hello") literal is automatically treated as a localizable key. You often get translation for free.

A modern String Catalog (.xcstrings) gathers every key in one editable table with a column per language.

Add a String Catalog via File, New File, then build once. Xcode auto-collects the strings used across your app.

In project settings, add a language under Localizations. A new column appears in the catalog, ready for translations.

Insert dynamic values right inside Text. Swift turns them into a format key so each language can place them correctly.

Add a comment so translators know what a string means. The same word can be a noun or a verb.

Languages pluralize differently. A String Catalog supports plural variations so "1 item" and "5 items" both read naturally.

Outside a Text view, wrap user-facing strings in String(localized:) so they still get translated.

Translations can be much longer than English. Let views resize instead of using fixed widths so text never gets clipped.

Run the scheme in a pseudolanguage to expand and accent text. It surfaces clipped labels before real translation begins.

Which file type is the modern, recommended way to manage translations in Xcode?

You can reach a global audience: Text literals are keys, a String Catalog holds translations, and comments plus plurals keep them accurate. 🌟