#import <UIKit/UIKit.h>

@interface UIColor (Helper)
+ (UIColor *)colorWithRGBA:(NSUInteger)color;
@end


#import "UIColor+Helper.h"

@implementation UIColor (Helper)

+ (UIColor *)colorWithRGBA:(NSUInteger)color
{
    return [UIColor colorWithRed:((color >> 24) & 0xFF) / 255.0f
                           green:((color >> 16) & 0xFF) / 255.0f
                            blue:((color >> 8) & 0xFF) / 255.0f
                           alpha:((color) & 0xFF) / 255.0f];
}

@end

iOS Localization Tutorial: Localize Your Apps to Support Multiple Languages

Editor’s note: This week let’s talk about localization. In brief, localization is a process to adapt a product to a particular language. Not all iPhone users can read or write English. If you just release your app in English, it may be ignored by user from other parts of the world. In this tutorial, Ziad will go through the localization process with you. You’ll see how easy you can localize an app and make it available in multiple languages by using the built-in function of Xcode and iOS API.

Enter the iOS localization tutorial.

The iOS devices including iPhone and iPad are available globally. Obviously, iOS users are from different countries and speak different languages. To deliver a great user experience, you may want to make your app available in multiple languages. The process of adapting an app to support a particular language is usually known as localization.

Xcode has the built-in support of localization. So it’s fairly easy for developer to internationalize an app through the localization feature and some API calls.

Some people think of localization as the same process of translation. That’s partially correct. Translating static or visible text is just part of the localization process. Localization involves other elements such as images, graphics and sound. You’ll also need to handle the different display format of numeric values, as well as, date and time.

In this tutorial, we’ll show you the step-by-step on how to localize the storyboard file, strings, images and app name. As usual, we’ll demonstrate the process by building a simple app and make it available in French.

Localization Overview

We are going to create a small application called “Book Store”, which will displays the details of a book with a cover image, title, author and description. The original app is in English. We’ll localize the app together and make it available in French. So at the end of the tutorial, you’ll have an app that supports two localizations: English and French.

To make the app available in French, we’ll demonstrate how to localize:

• the text in the storyboards
• the cover image
• the dynamic message displayed by code
• the name of the app as displayed in home screen

For those of you who don’t know how an app selects a localization, it refers to the language settings of iOS (General > International > Language). An app uses this preference as the key for accessing the localized resources for the requested language.

Getting Started

It’s time to set up the project by creating a new project based on the Single View Application iOS app template. In the project options, you’ll need to check the storyboard and Automatic Reference Counting Boxes. This app will provide only iPhone Views, so choose iPhone for the device family and save the project. Open the Storyboard, design the user interface as shown below:

Storyboards of BookStore

The focus of this tutorial is on Localization. So to save you time from setting up the project, you can download this project template to start with. The template already pre-built the user interface.

Tip: If you have no idea about how to work with storyboard, check out our tutorials in the free iOS course.

Localizing the Storyboard

Now, let’s start to localize the project. In Xcode, click on Book Store in the project navigator and select the Info tab of the project. Look for the localizations section in the Info tab. Apparently, it shows a single localization: English. Check the “Use Base Internalization” checkbox.

You’ll then be prompted to select the storyboard to use for the base internationalization.

Make sure that MainStoryboard.storyboard is selected and that the reference language is English. Click the Finish button.

What we just did is to create a base storyboard. The concept of base internationalization was first introduced in Xcode 4.5. An app has just one set of storyboards that is localized to the default language. These storyboards is known as the base internationalization. Later when we create a localization, Xcode automatically generates a strings file containing all the text in the base storyboard.

With the base storyboard configured, it’s now ready to add a localization for French. First, select the view controller in Storyboard. Then switch back to the project info. Click the + button at the bottom of the Localizations section and choose French from the popup list.

Adding a new localization

Next, you’ll be asked to choose the resource files and language for creating the French localization. You can refer to the below screenshot for the selected options. Leave all the files checked and click Finish.

Once done, you should notice in the project navigator that there is now a triangle symbol next to the MainStoryboard.storyboard. Expand it and you’ll find both the base storyboard and a strings file of the storyboard in French.

Select the french strings file (i.e. MainStoryboard.strings (French)) and you should find a list of strings in key/value pairs:

When we add a new localization, Xcode scans through the base storyboard, extracts those textual items to be localized and put them into the strings file. As you can see above, the visible strings of storyboards such as label, title of the navigation bar and button title are put into the strings file. All entries are in key/value pairs. The first part of key is the object ID of the UI item. You can find the object ID of the UI object under Identity Inspector. For instance, the object ID of the Buy button is shown here:

With the strings file generated, your job is to translate all the values into French. The contents of the MainStoryboard.strings file for the French localization will look like this:

Localizing Image

It’s very easy to localize image using Xcode. As a demo, we will localize the cover image. Select the “cover.jpeg” in the project navigator. Next, bring up the file inspector, and locate the localization section, in which you’ll see a button named “Localize…”. Click the button and you’ll be prompted for confirmation. Choose English and click the “Localize” button to confirm.

Localizing Cover Image

After that, you’ll see the French option in the localization section. Select the “French” localization and you’ll find two versions of cover.jpeg.

Adding French Localization for Image

Switch back to the finder and local the project directory. You’ll find two folders: en.lproj and fr.lproj. Both folders are automatically generated by Xcode for localization. The en.lproj folder stores resource files for English localization, while fr.lproj folder is for French localization. If you look into both folders, each one contains the cover.jpeg file. Download the French version of the cover image from here (or use whatever image you like). Copy the cover image just downloaded and replace the one in fr.lproj folder.

Now it’s time to test out the app. If you’ve got everything right, here are what you’ll see in English and French.

Localizing Dynamic Strings

So far we just demonstrated the localization of static items. But in many places in applications, you create NSString instances dynamically or display string literals to the user. These strings will also need to be localized in a localized application.

To demo how to localize text displayed by code, I’ve added a few lines of code for the “Buy” action:

The code is simple. It just shows up an alert displaying the “Thanks for Your Purchase!” message. But instead of using a hardcoded message, we use the NSLocalizedString macro to get the string. The NSLocalizedString macro fetches a localized string from the Localizable.strings file for the current localization. It takes two arguments: a key and a comment. At runtime, the macro returns the value for the key in the localization that corresponds to the user’s preferred language. The comment is for your own reference only.

If you run the app and tap the Buy button, you’ll only see an alert view with “BOOK_PURCHASE” message as we haven’t created the Localizable.strings file. This is the default file for storing localized strings that are used by code.

Now let’s create the Localizable.strings file. In the project navigator, create a new file under the Supporting Files folder. Select the Strings file template and click the Next button.

When prompted, save the file as Localizable.strings. Next, we’ll use the similar procedures to localize the file. Select the Localizable.strings and click the “Localize…” button in the File Inspector.

When the confirmation dialog appears, make sure that English is selected and then click the Localize button. Next, select the French checkbox to add a Localizable.strings file to the French localization. If you’ve got everything correct, you should have two version of Localizable.strings file.

Localizable.strings File in English and French

Put the following message in the English version of Localizable.strings file:

Translate the message and put it in the French version of Localizable.strings file:

You’re done. Compile and run the app again. Depending on the language setting, you should get different alert message when tapping the Buy button.

Localizing the App Name

In some cases, you may also want to localize the app name. When we create the French localization, Xcode already generates the French version of InfoPlist.strings. You can put key/value pairs in the InfoPlist.string file to override the values stored in Info.plist file.

So to display a different app name in the French version, simply add the following string in the InfoPlist.string (French) file:

This will change the name of app as appeared on the springboard. Compile and run the app again to test it out.

App Name in French

Summary

In this tutorial, we covered the localization process in iOS programming. Now you should have a basic idea of localizing an iPhone app.

For your complete reference, you can download the source code of the Xcode project from here. Please remember that the project should be run on Xcode 4.6 or up.

As always, please leave us comment and share your thought about the tutorial.

프라퍼티의 어트리뷰트에는 3종류의 값을 설정할 수 있다.

먼저, setter의 동작방식이 있다. 프라퍼티가 최종적으로 넘겨진 매개변수를 가지는 방식이다.

assign은 넘어온 값을 그대로 가진다. 주로 int, float이나 BOOL 같은 스칼라값을 다루는 프라터티가 assign방식을 사용한다.

retain은 넘어온 오브젝트의 리테인 카운트를 1 증가시켜 보관하며 이전 값은 release된다. 코코아 오브젝트는 대부분 retain방식을 사용하게 된다.

copy는 넘어온 매겨변수를 복사해서 보관하며 이전 값은 release된다. 프로그램의 로직 상 필요한 경우에는 매개변수를 copy를 사용하여 오브젝트를 복사해 사용할 수 있다. 이때 주의할 점은 매개변수로 넘어온오브젝트가 NSCopying프로토콜을 준수하는 오브젝트여야 한다는 것이다. 대부분의 코코아 오브젝트는 NSCopying 프로토콜을 준수하고 있지만 사용자가 만드는 커스텀 클래스나 CoreData의 오브젝트들은 NSCopying프로토콜을 기본적으로 준수하지 않기 때문에 직접 copyWithZone:메소드 구현을 통해 NSCopying 프로토콜을 구현해야 한다.

두번째로 nonatomic이 있다 (atomic 어트리뷰트는 사용하지 않는다).

nonatomic이 보다 리소스를 적게 소모하지만 프라퍼티에 접근하는 모든 메소드들이 쓰레드를 사용하지 않는다는 보장이 있지 않은 이상 기본값인 atomic을 사용하는 것이 좋다.

마지막으로 readwrite와 readonly가 있다.

글자 그대로 읽기만 할 수 있는 프라퍼티와 읽고 쓸 수 있는 프로퍼티를 만드는 설정이다. readonly로 설정되면 setter가 제공되지 않고 getter만 제공된다.

Menu Command Shortcuts (By Menu)

Each table in this section lists the commands in an Xcode application menu and the keyboard shortcuts associated with each command. Entries appear in the order in which they appear in the menu. The following tables are available:

• Table 1-1  Xcode menu

• Table 1-2  File menu

• Table 1-3  Edit menu

• Table 1-4  View menu

• Table 1-5  Navigate menu

• Table 1-6  Editor menu

• Table 1-7  Product menu

• Table 1-8  Window menu

• Table 1-9  Help menu

¹ Opens the scheme editing dialog for editing prior to performing the chosen command.

- (void)viewDidLoad

{

    [super viewDidLoad];

// Do any additional setup after loading the view, typically from a nib.

    NSFileManager *filemgr;

    NSString *docsDir;

    NSArray *dirPaths;

    filemgr = [NSFileManager defaultManager];

    // documents 디렉터리 얻기.

    dirPaths = NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES);

    docsDir = dirPaths[0];

    // 데이터 파일에 대한 경로 구축.(.h 파일에 @property (strong, nonatomic) NSString *dataFilePath; 정의 되어 있어야함).

    _dataFilePath = [[NSString alloc] initWithString:[docsDir stringByAppendingPathComponent:@"data.archive"]];

    // 그 파일이 이미 있는지 검사.

    if ([filemgr fileExistsAtPath:_dataFilePath])

    {

        NSMutableArray *dataArray;

        // 아카이브에서 데이터 가져오기.

        dataArray = [NSKeyedUnarchiver unarchiveObjectWithFile:_dataFilePath];

        // 이름 텍스트 필드.

        _name.text = dataArray[0];

        // 주소 텍스트 필드.

        _address.text = dataArray[1];

        // 전화 텍스트 필드.

        _phone.text = dataArray[2];

    }

}

// 저장 버튼에 바인딩한 메소드.

- (IBAction)saveData:(id)sender {

    NSMutableArray *contactArray;

    contactArray = [[NSMutableArray alloc] init];

    // 이름 텍스트 필드.

    [contactArray addObject:self.name.text];

    // 주소 텍스트 필드.

    [contactArray addObject:self.address.text];

    // 전화 텍스트 필드.

    [contactArray addObject:self.phone.text];

    // 아카이브에 저장하기.

    [NSKeyedArchiver archiveRootObject:contactArray toFile:_dataFilePath];

}

UIApplication *app = [UIApplication sharedApplication];
   
    NSArray *scheduled = [app scheduledLocalNotifications];
    if (scheduled.count)
    {
        [app cancelAllLocalNotifications];
    }
   
    UILocalNotification *alarm = [[UILocalNotification alloc] init];
    if (alarm)
    {
        alarm.fireDate = [NSDate dateWithTimeIntervalSinceNow:5.0f];
        alarm.timeZone = [NSTimeZone defaultTimeZone];
        alarm.repeatInterval = 0;
        alarm.alertBody = @"Five Seconds Have Passed";
        [app scheduleLocalNotification:alarm];      
       
    }

#import <AudioToolbox/AudioToolbox.h>

- (void)playClick
{
    NSString *sndpath = [[NSBundle mainBundle] pathForResource:@"click" ofType:@"wav"];
    CFURLRef baseURL = (CFURLRef)CFBridgingRetain([NSURL fileURLWithPath:sndpath]);
   
    SystemSoundID sysSound;
    AudioServicesCreateSystemSoundID(baseURL, &sysSound);
    CFRelease(baseURL);
   
    AudioServicesAddSystemSoundCompletion(sysSound, NULL, NULL, _systemSoundDidComplete, NULL);

    AudioServicesPlaySystemSound(sysSound);
}

void _systemSoundDidComplete(SystemSoundID ssID, void *clientData)
{
    AudioServicesDisposeSystemSoundID(ssID);
}

UIActionSheet *sheet = [[UIActionSheet alloc] initWithTitle:nil
                                                       delegate:self
                                              cancelButtonTitle:@"취소"
                                         destructiveButtonTitle:nil
                                              otherButtonTitles:@"액션1", @"액션2", nil];
   
    [sheet showInView:self.view];

// *********** ActionSheet 버튼 클릭시 실행하는 메소드. ***************************************

- (void)actionSheet:(UIActionSheet *)actionSheet clickedButtonAtIndex:(NSInteger)buttonIndex
{
    if (buttonIndex == actionSheet.cancelButtonIndex)
    {
        NSLog(@"취소 버튼 클릭");
    }
}

UIAlertView *alert = [[UIAlertView alloc] init];
    alert.delegate = self;
    alert.title = @"타이틀입니다.";
    alert.message = @"메세지를 적습니다. ^^";
    [alert addButtonWithTitle:@"아니오"];
    [alert addButtonWithTitle:@"예"];
    alert.cancelButtonIndex = 0;
    [alert show];

// ********************* 버튼 선택에 따른 처리 *******************************************

- (void)alertView:(UIAlertView *)alertView clickedButtonAtIndex:(NSInteger)buttonIndex
{
    // 버튼이 취소버튼인지 비교.
    if (buttonIndex != alertView.cancelButtonIndex)
    {
        // 예 버튼이 눌렸을때.
        UIAlertView *alert = [[UIAlertView alloc] init];
        alert.title = @"참! 잘했어요.";
        alert.message = @"예를 눌렀군요.";
        [alert addButtonWithTitle:@"OK"];
        [alert show];       
    }
   
}