什么东西应该在应用程序中本地化

时间：2021-07-12 16:16:19

When thinking about what areas should be taken into account for a localized version of an application a number of things pop up right away:

在考虑应用程序的本地化版本应考虑哪些方面时,会立即弹出许多内容:

  • Text display
  • Date and time

    • 日期和时间

  • Units
  • Numbers and decimals

    • 数字和小数

  • User input formats

    • 用户输入格式

  • LeftToRight support
  • Dialog and control sizes

    • 对话框和控件大小

Are there other things/areas to remember or keep in mind when building a localizable application? Are there any resources out there which provide a listing of best practices not just for text localization but for all things around localization?

在构建可本地化的应用程序时是否还有其他事项/要记住的事项?是否有任何资源可以提供最佳实践列表,不仅适用于文本本地化,还适用于本地化的所有事项?

3 个解决方案

#1

6  

After Kudzu's talk about l10N I left the room with way more questions then I had before and none of my old questions answered. But it gave me something to think about and brought the message "depends on how far you can/want to go" accross.

在Kudzu关于l10N的谈话之后,我离开房间时遇到的问题比我之前遇到的更多,而且我的旧问题都没有得到解答。但它给了我一些思考的东西,并带来了“取决于你能走/走多远”的信息。

  • Translate text bodies with aforementioned things

    • 用上述内容翻译文本主体

  • Test all your controls for length/alignment in LTR/RTL, TTB(TopToBottom) BTT and all it's combinations.

    • 在LTR / RTL,TTB(TopToBottom)BTT及其所有组合中测试所有控件的长度/对齐。

  • Look out for special characters and encodings

    • 留意特殊字符和编码

  • Look out for combinations of different alignments (LTR, RTL, TTB, BTT) and how they effect punctuation and quotation signs.

    • 注意不同比对的组合(LTR,RTL,TTB,BTT)以及它们如何影响标点符号和引号。

  • Align controls according to text alignment (Hebrew Win has its start menu at the right

    • 根据文本对齐方式对齐控件(希伯来语Win在右侧显示其开始菜单

  • Take string lengths into account. They can overflow in other languages.

    • 考虑字符串长度。他们可以用其他语言溢出。

  • Put labels at the correct side of icons (LTR, TTB etc)

    • 将标签放在图标的正确位置(LTR,TTB等)

  • Translate language selection controls

    • 翻译语言选择控件

  • No texts in images (can't be translated)

    • 图像中没有文字(无法翻译)

  • Translate EVERYTHING (headers, logos, some languages use different brand names, product names etc)

    • 翻译一切(标题,徽标,某些语言使用不同的品牌名称,产品名称等)

  • Does the region have a 24:00 or a 00:00 (changes the AM/PM that goes with it too)

    • 该地区是否有24:00或00:00(更改AM / PM也是如此)

  • Does the region use AM/PM or the 24:00 system

    • 该地区是使用AM / PM还是24:00系统

  • What calendar system are they using

    • 他们使用什么日历系统

  • What digit is for what part of the date (day, month, year in all its combinations)

    • 日期的哪个部分(所有组合中的日,月,年)的数字是多少

  • Try to avoid "copying [number] files" equivalents. Some regions have different rules about changing words according to quantities. (This is an extremely complicated topic that I will elaborate on if desired)

    • 尽量避免“复制[数字]文件”等价物。一些地区根据数量改变单词有不同的规则。 (这是一个非常复杂的话题,如果需要,我会详细说明)

  • Translate sentences, not words. Syntax rules are too complicated to put in your business logic.

    • 翻译句子,而不是单词。语法规则太复杂,无法放入业务逻辑中。

  • Don't use flags for regions. Languages != countries

    • 不要在区域使用标志。语言!=国家

  • Consider what languages / dialects you can support (e.g. India has a gazillion of languages)

    • 考虑一下你可以支持的语言/方言(例如印度有多种语言)

  • Encoding
  • Cultural rules (some western images displaying business woman can be near offensive in some other cultures)

    • 文化规则(一些展示商界女性的西方形象在其他一些文化中可能近乎令人反感)

  • Look out for language generalizations (e.g. boot(UK) != boot(US))

    • 注意语言概括(例如boot(UK)!= boot(US))

Those are the ones from the top of my head. The list just went on and on...

那些是我头脑中的那些。这个名单刚刚开始......

#2

1  

Don't forget the overhead of converting all documentation and help files.

不要忘记转换所有文档和帮助文件的开销。

#3

1  

a couple hints from my J2ME apps days:

我的J2ME应用程序日的一些提示:

  1. don't translate separate words, translate whole phrases, even if there are matching repetitions. You'll later have to translate to a language where words have to be modified differently in different contexts and you may end up with an analog of "color: greenish"

    不翻译单独的单词,翻译整个短语,即使有匹配的重复。你以后必须翻译成一种语言,在不同的语境中,单词必须以不同的方式进行修改,你最终可能会得到“颜色:绿色”的模拟结果。

  2. Right2Lelf includes numbering of lists, alignment, and alternative scroll bars

    Right2Lelf包括列表编号,对齐方式和替代滚动条

  3. Arabic languages write the same letter differently based on surrounding letters. You can't just print a string from a character buffer, you'll need a special control to output those or support from you platform

    阿拉伯语根据周围的字母以不同的方式书写相同的字母你不能只是从字符缓冲区打印一个字符串,你需要一个特殊的控件来从你的平台输出那些或支持

  4. alphabetical sorting is HARD. No native Chinese could ever explain me the rules, but they will always spot wrongly sorted words. There appear to be a number of options to sort Chinese. I guess other languages may have the same problem

    字母排序很难。没有中国人可以解释我的规则,但他们总会发现错误排序的单词。似乎有很多选项可以对中文进行排序。我猜其他语言也可能有同样的问题

#1

6  

After Kudzu's talk about l10N I left the room with way more questions then I had before and none of my old questions answered. But it gave me something to think about and brought the message "depends on how far you can/want to go" accross.

在Kudzu关于l10N的谈话之后,我离开房间时遇到的问题比我之前遇到的更多,而且我的旧问题都没有得到解答。但它给了我一些思考的东西,并带来了“取决于你能走/走多远”的信息。

  • Translate text bodies with aforementioned things

    • 用上述内容翻译文本主体

  • Test all your controls for length/alignment in LTR/RTL, TTB(TopToBottom) BTT and all it's combinations.

    • 在LTR / RTL,TTB(TopToBottom)BTT及其所有组合中测试所有控件的长度/对齐。

  • Look out for special characters and encodings

    • 留意特殊字符和编码

  • Look out for combinations of different alignments (LTR, RTL, TTB, BTT) and how they effect punctuation and quotation signs.

    • 注意不同比对的组合(LTR,RTL,TTB,BTT)以及它们如何影响标点符号和引号。

  • Align controls according to text alignment (Hebrew Win has its start menu at the right

    • 根据文本对齐方式对齐控件(希伯来语Win在右侧显示其开始菜单

  • Take string lengths into account. They can overflow in other languages.

    • 考虑字符串长度。他们可以用其他语言溢出。

  • Put labels at the correct side of icons (LTR, TTB etc)

    • 将标签放在图标的正确位置(LTR,TTB等)

  • Translate language selection controls

    • 翻译语言选择控件

  • No texts in images (can't be translated)

    • 图像中没有文字(无法翻译)

  • Translate EVERYTHING (headers, logos, some languages use different brand names, product names etc)

    • 翻译一切(标题,徽标,某些语言使用不同的品牌名称,产品名称等)

  • Does the region have a 24:00 or a 00:00 (changes the AM/PM that goes with it too)

    • 该地区是否有24:00或00:00(更改AM / PM也是如此)

  • Does the region use AM/PM or the 24:00 system

    • 该地区是使用AM / PM还是24:00系统

  • What calendar system are they using

    • 他们使用什么日历系统

  • What digit is for what part of the date (day, month, year in all its combinations)

    • 日期的哪个部分(所有组合中的日,月,年)的数字是多少

  • Try to avoid "copying [number] files" equivalents. Some regions have different rules about changing words according to quantities. (This is an extremely complicated topic that I will elaborate on if desired)

    • 尽量避免“复制[数字]文件”等价物。一些地区根据数量改变单词有不同的规则。 (这是一个非常复杂的话题,如果需要,我会详细说明)

  • Translate sentences, not words. Syntax rules are too complicated to put in your business logic.

    • 翻译句子,而不是单词。语法规则太复杂,无法放入业务逻辑中。

  • Don't use flags for regions. Languages != countries

    • 不要在区域使用标志。语言!=国家

  • Consider what languages / dialects you can support (e.g. India has a gazillion of languages)

    • 考虑一下你可以支持的语言/方言(例如印度有多种语言)

  • Encoding
  • Cultural rules (some western images displaying business woman can be near offensive in some other cultures)

    • 文化规则(一些展示商界女性的西方形象在其他一些文化中可能近乎令人反感)

  • Look out for language generalizations (e.g. boot(UK) != boot(US))

    • 注意语言概括(例如boot(UK)!= boot(US))

Those are the ones from the top of my head. The list just went on and on...

那些是我头脑中的那些。这个名单刚刚开始......

#2

1  

Don't forget the overhead of converting all documentation and help files.

不要忘记转换所有文档和帮助文件的开销。

#3

1  

a couple hints from my J2ME apps days:

我的J2ME应用程序日的一些提示:

  1. don't translate separate words, translate whole phrases, even if there are matching repetitions. You'll later have to translate to a language where words have to be modified differently in different contexts and you may end up with an analog of "color: greenish"

    不翻译单独的单词,翻译整个短语,即使有匹配的重复。你以后必须翻译成一种语言,在不同的语境中,单词必须以不同的方式进行修改,你最终可能会得到“颜色:绿色”的模拟结果。

  2. Right2Lelf includes numbering of lists, alignment, and alternative scroll bars

    Right2Lelf包括列表编号,对齐方式和替代滚动条

  3. Arabic languages write the same letter differently based on surrounding letters. You can't just print a string from a character buffer, you'll need a special control to output those or support from you platform

    阿拉伯语根据周围的字母以不同的方式书写相同的字母你不能只是从字符缓冲区打印一个字符串,你需要一个特殊的控件来从你的平台输出那些或支持

  4. alphabetical sorting is HARD. No native Chinese could ever explain me the rules, but they will always spot wrongly sorted words. There appear to be a number of options to sort Chinese. I guess other languages may have the same problem

    字母排序很难。没有中国人可以解释我的规则,但他们总会发现错误排序的单词。似乎有很多选项可以对中文进行排序。我猜其他语言也可能有同样的问题

标签：

相关文章