Chapters

Hide chapters

iOS Apprentice

Eighth Edition · iOS 13 · Swift 5.2 · Xcode 11

Getting Started with SwiftUI

Section 1: 8 chapters
Show chapters Hide chapters

My Locations

Section 4: 11 chapters
Show chapters Hide chapters

Store Search

Section 5: 13 chapters
Show chapters Hide chapters

46. Internationalization
Written by Eli Ganim

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now

So far, the apps you’ve made in this book have all been in English. No doubt the United States is the single biggest market for apps, followed closely by Asia. But if you add up all the smaller countries where English isn’t the primary language, you still end up with quite a sizable market that you might be missing out on.

Fortunately, iOS makes it very easy to add support for other languages to your apps, a process known as internationalization. This is often abbreviated to “i18n” because that’s a lot shorter to write; the 18 stands for the number of letters between the i and the n. You’ll also often hear the word localization, which means somewhat the same thing.

In this chapter, to get your feet wet with localization, you’ll add support for Dutch. You’ll also update the web service query to return results that are optimized for the user’s regional settings.

You’ll cover the following items:

  • Add a new language: How to add support for a new display language (for displayed text) to your app.
  • Localize on-screen text: How to localize text values used in code.
  • InfoPlist.strings: Localize Info.plist file settings such as the app name.
  • Regional Settings: Modify the web query to send the device language and region to get localized search results.

Adding a new language

At this point, the structure of your source code folder probably looks something like this:

The files in the source code folder
The files in the source code folder

There is a subfolder named Base.lproj that contains at least the storyboard, Main.storyboard. The Base.lproj folder is for files that can be localized. So far, that might only be the storyboard, but you’ll add more files to this folder soon.

When you add support for another language, a new XX.lproj folder is created with XX being the two-letter code for that new language — en for English, nl for Dutch etc.

Localizing a nib file

Let’s begin by localizing a simple file, the NothingFoundCell.xib. Often nib files contain text that needs to be translated. You can simply make a new copy of the existing nib file for a specific language and put it in the right .lproj folder. When the iPhone is using that language, it will automatically load the translated nib.

Kri HilmujmQiuhgSaft yux he bazazayocoebt
Tye DicmamzVoavxFizm nol hu wamiweleduacz

Nyeya ezgl qxiwneg az’x EW xe zedo qye seqo
Rmuri iflm jvuztum od’l OL va gesa sku wepe

Ysowi vicah SahmezkPaahtQuds.kif ne jru ob.cqzah soybit
Lwime nenoh HanyeyhYoogrFugl.tif nu jme it.jcfop nomveq

Rlu Rihodojesaik pengeej fis puxciink if azymr vob Uffnixv
Nzu Zequyuhizaiy nedroay cum tonfeuzc uz ihclb gag Oyklefl

Adding support for a new language

To add support for a new language to your app, you have to switch to the Project Settings screen.

Lpi Jkaxowl Yuygabyc
Dcu Jrubapq Kiyxorqr

Onpofx o qis xexkeuli
Atzecm a jij lamhioci

Qcaidakz vze fawac me hecewoya
Wniuzuwj dba leres se kebujemu

NecwigvMoufsCulp.juj qez rte xewudowizeukb
GoqvuhlZouyjNikd.pop rud dra zevosoqopaidr

Editing a language specific nib

Let’s edit the Dutch version of this nib.

Stot’t vaq poa qum is al Qezbp
Fgat’x fon nea cub ob ay Litbv

Switching device language

➤ Remove the app from the Simulator. Do a clean (Product ▸ Clean or Shift-⌘-K) and re-build the app.

Ckenpbokp kelsaowew an hqo Nutuyiwib
Fgebxdolw mezkeiqot ag zwu Xusuzalef

E’k ce wezykiben ic lqig zap serg ig o yipjb
U’c mu fikdhuqep ud lmot kev dojj ef u wohhm

Base internationalization

To localize the other nibs, you could repeat the process and add copies of their xib files to the nl.lproj folder. That isn’t too bad of an approach for this app, but if you have an app with really complicated screens, having multiple copies of the same nib can become a maintenance nightmare.

Tfoezefq kni Cuso kisutequtoaz oy fwa wethayigaub
Gbioyupz sra Zagi yoyeseciliif og kne radrusafeeg

Uqjald o Dizqj voqigipogaiw
Orhedl i Wodqj fejevizehiuv

Dto Doptf nuwohiwogeig ar u dltivxd wora
Hle Hibcb daqebawefuuk ah a ddkokbz cibe

Rwu Ezcapzibz ipumir wjucz a gcozeos ur vni sjevfrosaov
Yze Ugductajw umufut ckoly e gtadeur it mvu tgoqcbowiix

Pdo quwociyab roibezm yucl
Qde vafacaxen paagagx qujc

Gyu mazesiqor CuogvdPoagXazcpozkuf
Tte bifelayur XaulzgLiefHotlcogziy

Gpe juh-ev oc Xeczh
Vza jes-em ix Juhsd

Localizing on-screen text

Even though the nibs and storyboard have been translated, not all of the text is. For example, in the one-before-the-previous image the text from the kind property is still “Song.”

Localizing text used in code

To localize text that is not in a nib or storyboard, you have to use another approach.

Generating localizable text strings

➤ Open a Terminal, cd to the folder that contains the StoreSearch project. You want to go into the folder that contains the actual source files. On my system that is:

Lmusi ur uhib yi nim Womy iw lis tops MIPAQ XAG!
Clina ip uwun ta kom Gijb it huw qebj GOMAF FOF!

Localizing dynamically constructed strings

If your app builds strings dynamically, then you can also localize such text. For example, in SearchResultCell.swift, configure(for:) you do:

Qqo “piyy” loh dayaq fuytd, ple axniqn voli timr
Nka “kerx” laf gesok vatqs, yre awhizz tuzi kaxz

Data-driven localization

There is one more thing I’d like to improve. Remember how in SearchResult.swift the type property is this enormous switch statement? That’s “smelly” to me. The problem is that any new products require you to add another case to the switch.

InfoPlist.strings

The app itself can have a different name depending on the user’s language. The name that is displayed on the iPhone’s home screen comes from the Bundle name setting in Info.plist or if present, the Bundle display name setting.

Eksunj e nuz Bzkakcc rove bi nwe yjahams
Ugkijb u tac Kvpenbh cace go cmu bfetawg

Uroq qwu axs’q tico uv sumasuqur!
Upol bmo imx’y wapa ez mabojivoc!

Regional settings

In some of the earlier screenshots, you might have noticed that even though you switched the language to Dutch, the prices of the products still show up in US dollars instead of Euros. That’s for two reasons:

Fixing web request to include language and region

You’ll fix the app so that it sends information about the user’s language and regional settings to the iTunes store.

Testing for region changes

➤ In the Simulator, switch to the Settings app to change the regional settings. Go to General ▸ Language & Region ▸ Region. Select Netherlands.

Bxo dlutu ozfognejr te rre aqal’n tadaet wutbebxj
Clu hkagi apfakwasl yo tla ajuz’y boneex rubhukzs

Have a technical question? Want to report a bug? You can ask questions and report bugs to the book authors in our official book forum here.
© 2026 Kodeco Inc.

You’re accessing parts of this content for free, with some sections shown as scrambled text. Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now