To localize your Xcode project you must create a Strings Catalog. To do this go to File > New > File from template… Type string in the filter entry at the top right hand side. Double click String Catalog, accept the name Xcode suggests and click create. Ensure the file is stored in the top level of your app's directory structure. This is so you can easily access the file in Project Navigator. You will see a new file called “Localizable.xcstrings” has appeared at the top of Xcode’s Project Navigator. It will be empty. Every time you build your project, Xcode locates all strings that will be presented to the user and copies them to Localizable.xcstrings. Build your project to see these strings.
At the bottom left of the Localizable.xcstrings window, click on the plus sign. This will show you a list of the most popular spoken languages you can choose. At the bottom of this list is “More Languages”. Click on this to see many more languages and their variants. However, do not be too liberal with choosing languages and variants. AkVox employs Google Cloud Translate API and although Google can translate into around 200 languages, it cannot translate into anywhere near the many hundreds of language variants presented by Xcode.
For example, if you click on English in the More Languages list, you’ll see over 130 possible variants of English. However, Google Cloud Translate has only one entry for English with no variants.
Click here to see the list of Google Cloud Translate Languages.
If you really need to translate your app into languages not supported by Google, you’ll need to seek the services of a professional translator.
With popular languages such as Arabic, Spanish and French, try to go for the standard language rather than any of the variants. Even if Google supports the variants you want, it is probably unlikely that there will be any difference in the translations required for your app.