关于本站 联系本站 English
首页
| 登录论坛|
| 新闻 | 观点 | 本地化 | 培训 | 测试 | 招聘 | 国际化 | 知识库 | 专题 | 会员区 | 本站月报 | 关于本站 | English |
用户: 密码: 验码:  
栏目导航 网站首页>>本地化>>本地化基础

精雕细琢的手机软件本地化
  发表日期:2008年12月5日  共浏览8356 次      作者:John White  【编辑录入:giltworld
     字体颜色:    【字体:放大 正常 缩小】  【双击鼠标左键自动滚屏】 【图片上滚动鼠标滚轮变焦图片】 

The Watchmaker Localizes Mobile Applications

Have you had to localize mobile applications yet? What's your favorite part?

They're a breed apart, these mobile app developers. The familiar model of handing off pure resource files, localizing them, then building them back into the executable doesn't appeal to them somehow, at least not in my experience.

They are fond of pulling the strings out of resource files, placing them in a spreadsheet with copious comments, and asking us to put the translations in Column B. It doesn't matter much to the localizers, but I think it results in more work for the developers.

These projects put the translators at something of a disadvantage in other ways:
  • In the ancient days of static, 80-character line lengths, translators often had to ensure that their strings contained no more characters than the original text. Mobile applications are similarly starved for UI real estate, but this time, length is measured more often in pixels than in characters, a metric difficult for most translators to work with.
  • There is still no context for a translator working on a batch of UI strings. What's worse now is that the text in many mobile apps is sparse to begin with, and it's rare that the translator can run the app to get the context for strings like "Up" and "Done". We pester our clients to provide screenshots, functionality descriptions, requirements documents, and anything else to help the translators.
  • The studio isn't easy to work with yet. With PC-based applications, localizers figured out how to build and test resource DLLs themselves to shorten the L10n QA cycle, instead of bugging clients' engineering teams all the time. It will be a while before localizers adopt the studios and toolkits used by mobile app developers, because there are lots of them.
  • Phones and mobile devices are in scant supply, and the localization process is at the bottom of the food chain. How can the localizer perform proper L10n testing on the device, when the client only has one phone - or none at all - and everybody else needs to use it? (Shameless plug: Our client NSTL performs L10n testing for situations like these.)
We've done several mobile app projects for a couple of clients since 2002. They're rather labor-intensive - especially before and after the localizer gets involved - and it always feels like making a watch: lots of small parts, small tolerances and high demands.

How do you get along with mobile app localization?

Source:http://www.1-for-all.com/l10n_blog/2008/11/watchmaker-localizes-mobile.html

13 November 2008


上一篇:本地化DITA项目
下一篇:2011年中国本地化服务行业高层论坛综述

 相关专题:

·专题1信息无

·专题2信息无
 
  热门文章:
 · 2007年全球翻译公司25 [39994]
 · 缺陷管理工具Bugzill [34756]
 · “本地化世界网”介绍 [32965]
 · XLSX,TBX,SDLT [32516]
 
 相关文章:

·没有相关文章

相关评论:(评论内容只代表网友观点,与本站立场无关!)
相关评论无
发表、查看更多关于该信息的评论 将本信息发给好友 打印本页
关于本站 | 网站历程 | 使用声明 | 网站地图 | 联系本站 |
本地化世界网版权所有,版权所有2003-2008
京ICP备05035404号
网站统计:    论坛统计:
页面执行时间:109.375毫秒