Last modified 16 months ago Last modified on 10/11/10 20:00:03

Mac Specific Translation

Table of Contents

  1. Introduction
  2. Getting started
    1. Example
  3. Getting your changes published
  4. Keeping translations up to date

The Mac has a few platform specific strings to translate that are not in the .po files. This is a quick guide to help you translate these strings.

Introduction

Translating the Mac specific strings is done by editing a small file that contains all the messages that defined in the info.plist file that the user will see.

There are two main parts to the file: The key (this tells it which message is being translated) and the localized string.

Getting started

To start translating, download the latest version of the .strings file from the appropriate .lproj folder found here: wzlocal (hint: it should have the same name as the .po file you have been working on). If your language doesn't exist yet, use a copy of this InfoPlist.strings file.

The easiest way to edit the files is editor that understands UTF-8 (such as ​Notepad++ for Windows, TextEdit or ​TextWrangler for Mac OS X, Kate or Gedit for Linux).

Example

/* Localized versions of Info.plist keys */

/* Only change the strings after the '='; '\n' gives you a new line, do not use it in the CFBundleName or CFBundleDisplayName strings */


/* Warzone */ /* Name in the menubar */
CFBundleName = "워존";

/* Warzone 2100 */ /* Name of the app bundle */
CFBundleDisplayName = "워존 2100";

/* Copyright © 1999-2004 Eidos Interactive.\nCopyright © 2005-2010 The Warzone 2100 Project */ /* Copyright string */
NSHumanReadableCopyright = "Copyright © 1999-2004 Eidos Interactive.\nCopyright © 2005-2010 워존 2100 프로젝트";


/* Warzone 2100 Map / Mod File */ /* Description of .wz files */
"Warzone 2100 Map / Mod File" = "워존 2100 맵 Mod File";

The part before the '=' is the key, do not change this; the part after that is what will be displayed to the user.

Getting your changes published

When you are finished open a new ticket (if you do not use this link be sure to set the type to 'patch', the OS to 'Mac 'and the component to 'Data: Translation'). Make sure you mention the language code the .strings file is for.

Make sure you are adding to the latest translation file, so that you aren't duplicating work that other people have already done.

Keeping translations up to date

Just as with the .po files the .strings files are occasionally updated (although much less often). You can keep track of this on the wzlocal log page or through the RSS feed found there.

Attachments