使用Xamarin进行跨平台移动应用本地化

需积分: 9 16 浏览量更新于2024-07-20 1 收藏 2.75MB PDF 举报

"本书《Cross-platform Localization for Native Mobile Apps with Xamarin》由Microsoft MVP Chris Miller撰写，旨在引导开发者如何使他们的应用适应全球市场。通过.NET框架，作者展示了如何使用单一共享的语言资源来实现多语言支持。书中以一个简单的移动应用为例，逐步解释如何针对Android、iOS和Windows平台进行适应，包括如何处理不同平台的本地化和国际化，以及如何使用资源文件和处理文化差异如日期和货币。此外，还涵盖了如何利用Microsoft的Multilingual App Toolkit管理语言资源，以及如何使用Android Studio、Xcode、Xamarin和Visual Studio工具创建跨平台的本地化应用。书中还包括了获取翻译帮助的方法，适用于编写Windows Phone、Android和iOS原生应用的移动应用开发者。" 在这本书中，读者将学习到以下内容： 1. 了解本地化和国际化的概念及其重要性，理解全球化市场的价值。 2. 掌握在Android、iOS和Windows平台上如何支持多种语言，包括每个平台的本地化策略。 3. 学习如何处理文化差异，比如日期格式和货币表示，以确保应用在不同地区都能正确显示。 4. 使用Microsoft的Multilingual App Toolkit等工具，有效管理和更新语言资源。 5. 实践创建跨平台应用，通过Android Studio、Xcode、Xamarin和Visual Studio进行项目开发，实现99%的代码共享。 6. 学会测试应用的本地化支持，避免常见的本地化陷阱。 7. 获取帮助翻译应用程序中的文本，扩展应用的语言覆盖范围。本书适合已经有一定基础的移动应用开发者，特别是那些专注于Windows Phone、Android和iOS原生应用开发的开发者。书中的内容不仅涵盖理论知识，还包括大量实践操作，确保读者能够实际应用所学，构建出具有高度可扩展性和适应性的跨平台本地化应用。书中的章节安排如下： - 第1章：什么是本地化？介绍本地化的基本概念和重要性。 - 第2章：工作与资源文件，讲解如何利用资源文件进行本地化处理。 - 第3章：使用Multilingual App Toolkit，深入理解这个工具在管理语言资源上的作用。 - 第4章：Island Menu Application，通过实例应用展示本地化实践。 - 第5章：额外资源，提供进一步学习和参考的资料和建议。这本书是开发者进行跨平台移动应用本地化开发的重要指南，它提供了实用的技术和策略，帮助开发者克服不同平台之间的差异，打造具有广泛用户基础的全球化应用。

CHAPTER 1 ■ WHAT IS LOCALIZATION?

Identifying Language and Culture

The standard way of identifying language and country in software development is to use variations of the

Internet Engineering Task Force (IETF) language tag to identify language and culture in your code. The

IETF is a collection of groups that develop and promote Internet standards. Originally prompted by the US

government, the IETF is now an international nonprofit organization.

In 1995, an IETF group called the Network Working Group published RFC 1766: “Tags for the

Identification of Languages.” It defines the tag used to indicate a language. Although there are variations of

the tag definition, the focus here is on the common one- and two-part conventions. The syntax of this tag is

the primary tag ("-" subtag). For this book, the tag is referred to as the language or locale string.

The language codes are typically the two-letter codes from the ISO-639-1 table. Some common entries

are shown in Table1-1.

For script languages, you can use the ISO 15924 standard, which uses a four-letter code. The first letter

is uppercase; the remaining three are lowercase. Use this standard if you are supporting both the traditional

and simplified forms of the Chinese language. For example, Chinese in the simplified script is designated

as zh-Hans, and Chinese in the traditional script is zh-Hant. You can still append the region code after the

script code. For simplified Chinese for the Hong Kong region, use zh-Hans-HK.

The subtag represents the region in which the language is being used. The subtag is optional and is

prefixed with the "-" character when included. The subtags are defined by the two-letter country codes from

the ISO 3166 list. These codes are referred to as the Alpha-2 code (see Table1-2). There is a three-letter code

that is referred to as the Alpha-3 code, but it’s not used for the subtag.

Table 1-1. Selected ISO 639-1 Language Codes

Language name Native Name ISO 639-1 Code

English English en

Spanish Español es

French Français fr

Italian Italiano it

Japanese 日本語 ja

Russian Pуccкий ru

Portuguese Português pt

Arabic العربية ar

Hindi  hi

Chinese 中文 (Zhōngwén) zh

German Deutsch de

CHAPTER 1 ■ WHAT IS LOCALIZATION?

■ Note Because a locale string can be in the formats of xx, xx-XX, xx-Xxxx, or xx-Xxxx-XX, try to avoid

parsing and manipulating the string. With the exception of dealing with Android and the extra r, just pass the

locale string through and let the runtime pick the right set of resource files.

Prior to iOS 8, iOS supported only the primary tag. You could specify the language, but not the country. If you

were supporting the French language, you needed to make sure that the words and terms used were common

to multiple dialects.

When your application starts up, it attempts to match the closest language based on the language string

and the resource files included with the application. It tries to find the closest match first, based on the

primary tag and subtag. If that search fails, it attempts to locate the resource based on just the primary tag. If

that fails, it will just use the default language of the app. (That default is the language that the developer used

as the default.)

You don’t need to account for every variation of language and culture. If all the English strings in your

app are the same across multiple dialects, you just need to provide a single en language resource. If most of

the strings are the same, but a few are dialect specific, you can handle that as well. Let’s say that the English

strings in your app are 99% identical between the US and the UK version; the only difference in this app is

the word color. In the UK, the preferred spelling is colour. You can handle this by putting all the strings in an

en resource file. You would then also have an en-GB resource file that contained colour.

With the French language, two of the most popular dialects are the Metropolitan version used in France

(fr-FR) and the Canadian version (fr-CA). Canadian French is considered less formal than Metropolitan

French; for example, Canadian French uses fewer specifiers and instead uses que as a relative pronoun.

For example, for the sentence "I found the document I needed," the Canadian French translation would

be "J’ai trouvé le document que j’ai de besoin." The Metropolitan French version would be "J’ai trouvé le

document dont j’ai besoin." Another example is the term for weekend. In Metropolitan French, you use le

weekend; in Canadian French, you use la fin de semaine.

Portuguese is another language with dialect differences. I’ll refer to the dialect spoken in Portugal

as European Portuguese. Brazilian Portuguese has grammar rules and nouns that are different from the

European Portuguese. Some examples of these differences are shown in Table1-4.

Table 1-4. Selected Differences Between Brazilian and European Portuguese

English Brazilian Portuguese European Portuguese

media mídia media

train trem Comboio

bus Ônibus autocarro

brown marrom castanho

CHAPTER 1 ■ WHAT IS LOCALIZATION?

Be careful when doing partial resource files. Although they take up less space, you have a greater risk of

missing some of the translations.

Where Does the Language String Come From?

The language string is supplied to your application from the OS. Although the values that make up both

parts of the language string come from ISO 639 and ISO 3166 lists, they don’t contain all the values of

either list. Most mobiles support a subset of countries and languages. With iOS, Apple supports more than

30 languages for the OS, but the user can select any language and region. Windows 10 for desktop has an

extensive set of supported languages. Windows 10 for the phone supports a more limited set of languages,

and that list can be limited by the region in which the phone was sold.

The languages supported by a device can vary. Newer versions of an OS usually add more languages.

Some vendors may limit the number of languages supported by region.

For the most part, you do not need to do anything with the language string. The runtime code in

your application should manage parsing the language string and selecting the right resource file. When

you do locale aware formatting, the region code of the language string is used to manage the other part of

localization: the formatting of dates, times, numbers, and so on.

■ Note Although iOS supports almost any language and region combination, iTunes Connect supports a

smaller list of languages. So although your app can be localized in a language like Polish, the app descriptions

are not available in Polish; they default to English.

Other Things to Consider

In addition to handling internationalization and localization, you may need to also work with features that

are bigger in one market than in others.

Users in China do not have access to Facebook or Twitter. In their place, the popular social media

apps in China are WeChat and Weibo. With more than 300 million WeChat users, leveraging the WeChat

integration API from your app can provide added exposure to your app.

Which Languages Do You Need to Support?

If you are developing your app in English and you have decided to add support for other languages, you need

to decide which languages to add. If you need to support languages X, Y, and Z for contractual obligations,

your choices are already defined for you. You can build in the support for the cultural elements and have the

text translated by professionals.

If you are large company such as Facebook, you support as many languages as you possibly can. At the

time that this book was written, Facebook supports more than 70 languages. It is a large enough company to

have its own translation staff.

If you are the software development team or a significant portion of your company's software team,

you don’t have the same resources available that Facebook has. So you'll need to pick and choose which

languages to support. One way to choose languages to support is by the number of native speakers. The top

ten languages for native speakers is shown in Table1-5.

CHAPTER 1 ■ WHAT IS LOCALIZATION?

Let’s suppose that you wrote your app for just the English language. Your potential audience of native

speakers is approximately 340 million. The actual numbers would be a percentage of that 340 million

because there are fewer smartphone users. But the number gives you something to work with.

If you add support for just Chinese and Spanish, you expand your potential market from 340 million to

a combined total of 2 billion, roughly 5 times the size of your original market. You can't count on every single

person being a potential customer, but it does show that Chinese and Spanish speakers greatly outnumber

English speakers.

What’s Involved with Translation?

When you write an app that will support multiple languages, you have to separate the text and other assets

(images, videos, audio) from the code. Having the text strings in a resource file provides two benefits for you.

First, you can have the application framework select the appropriate language resource file at runtime;

you don’t need the code to pick the correct language. The application runtime will determine the user's

current language and culture and will load in the best match for the locale.

The second benefit is to be able to provide just the text resources to a translator. You don't need to

provide all your source code—only the resource files containing the text to translate. (Chapter 2 covers the

mechanics of how to work with language resource files.)

Text translation involves more than replacing one word or set of words with another. Other languages

can have different rules and usages. It's important to be aware of what needs to be translated and how

languages are handled differently between cultures.

One language can have multiple dialects or even character sets. For example, the written Chinese

language has two standard character sets: traditional and simplified.

Simplified Chinese was instituted by the People’s Republic of China (PRC) in the 1950s and ‘60s. It was

based on work started decades earlier. The simplified characters were created by reducing the number of

strokes required to create a character and simplifying the number for forms for a character.

After the implementation of simplified Chinese, the term traditional Chinese has been used to describe

the previous character set. Modern Unicode supports both simplified and traditional character sets.

If you are supporting mainland China (PRC) and Singapore, you need to support simplified Chinese. If

you are supporting Taiwan, Hong Kong, and Singapore, you need to support traditional Chinese. Adoption

of simplified Chinese has spread in recent years and support of simplified Chinese is needed to make your

product salable.

Table 1-5. Top Ten Languages by Population (2016) Source: Lewis, M. Paul, Gary F. Simons, and Charles D.

Fennig (eds.). 2016. Ethnologue: Languages of the World, 19th ed. Dallas, Texas: SIL International

Rank Language Native Speakers (in Millions)

1 Chinese 1,302

2 Spanish 427

3 English 339

4 Arabic 267

5 Hindi 260

6 Portuguese 202

7 Bengali 189

8 Russian 171

9 Japanese 128

10 Lahnda 117

剩余118页未读，继续阅读

ramissue

粉丝: 354
资源: 1487

使用Xamarin进行跨平台移动应用本地化

api-ms-win-core-localization-l1-2-1.dll

api-ms-win-core-localization-l1-2-0.dll

cross-platform-localization-xamarin:Christopher Miller的“使用Xamarin进行本地移动应用程序的跨平台本地化”的源代码-Mobile app source code

deprecated-Kf.Localization:基本.Net库，用于支持基于资源的本地化

Laravel开发-laravel-js-localization .zip

Aspnet-cms-localization.zip

mat-pso-localization-master.zip_Localization pso_SWARM WSN_pso

Autonomous-Robots-Localization-master.zip

android-gradle-localization-plugin-1.0.7.zip

内网sublime3-Chinese-Localization-master.zip

最新资源