本地化 iPhone 应用程序很常见吗？默认情况下本地化吗？
试图解决与客户的争论。我没有本地化应用程序中的字符串和图像，并且在 3 周的定义和发现期间也没有出现。他们似乎认为这是一个基本的最佳实践，并且应该默认完成。我不同意，特别是如果没有计划语言的话。
看来你会把这个留给用户的需求
所以，我想请社区插话并告诉我你是否默认本地化了你的iPhone应用程序？
我要求这不仅可以帮助我了解我可能遗漏的地方，而且可以帮助将来的其他人了解什么被认为是“默认”和“最佳实践”
Trying to settle a debate with a client. I didnt localize the strings and images in the application and it didnt come up during the 3 week define and discover. They seem to think its a basic best practice and that it should have been done by default. I disagree, especially if there are no planned languages otw.
Seems like you would leave this for demand by users
So, Id like to ask the community to chime in on this and tell me if you by default have localized your iphone app or not?
I ask this to not only help me understand where I might have missed something but also to help others in the future as to what is considered "default" and "best practice"
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
这个问题将会引发很多意见。因为 Apple 让 iOS 上的字符串本地化变得异常简单，我个人认为你应该默认将所有应用程序设置为本地化。无论您发现自己在哪里定义了文字字符串，都可以将其替换为 NSLocalizedString() ，直到它成为您的第二天性。然后，如果您决定稍后进行本地化，则不必到处寻找和啄食。如果你从不进行本地化，除了几次击键之外，你什么也不会丢失。
真正的本地化可能会有本地化的 NIB（例如，对于不同的语言可能有不同大小的按钮）。不过，如果您使用
NSLocalizedString()代码（而不是在 Interface Builder 中）分配将出现在 NIB 中的所有字符串，从长远来看，您可能会节省时间。AppStore 使您的应用程序在如此多的国家/地区可见，这一事实极大地增加了本地化的需求。阅读威尔·希普利 (Wil Shipley) 发表的这篇文章，了解您所赚的钱可以通过进入许多市场来实现。
This question is going to spark a lot of opinion. Because Apple makes it ridiculously easy on iOS to localize strings, I personally feel you should set all apps up for localization by default. Anywhere you find yourself defining a literal string, substitute it with
NSLocalizedString(), until it becomes second nature. Then, if you decide you want to localize later, you don't have to hunt and peck all over the place. If you never localize, you lose nothing except a few keystrokes.A true localization will probably have localized NIBs to (may have different sized buttons for different languages, for instance). Still, if you assign all strings that will appear in the NIB in code with
NSLocalizedString(), rather than in Interface Builder, you'll likely save time in the long run.The fact that the AppStore makes your app visible in so many countries greatly increases the demand to localize. Read this post by Wil Shipley about the money you could be making by reaching many markets.
首先，您必须将其国际化，即编写代码以便可以轻松添加新语言。默认语言和第一语言通常是英语（如果从英语开始，苹果会让事情变得更容易，并且客户更有可能购买仅英语版本的应用程序，而不是仅斯瓦希里语版本的应用程序）。
其次，您可以将其本地化为对应用程序的客户重要的语言。西班牙语、中文、法语、波斯语...
First, you have to internationalize it, that is to write your code such that it is easy to add new languages. Default - and first - language is usually english (Apple makes things easier if you start with english and customers are more likely to buy an app in english only than in swahili only).
Second, you can localize it to languages that are important for customers of your app. spanish, chinese, french, farsi, ...
如果没有客户的输入，您怎么可能知道使用什么语言进行本地化？
假设在需求期间从未讨论过它，那么看来您是对的。如果他们想要应用程序的本地化版本，他们应该提出请求。
@greg 有一个非常好的观点，因为从一开始就使用本地化字符串是有益的，但是设置本地化应用程序并不是特别困难。真正的翻译是困难且昂贵的。
How could you possibly know what languages to use for localization without input from your client?
Assuming it was never discussed during requirements, it appears you are in the right here. If they wanted localized versions of their app, they should have requested it.
@greg has a very good point, in that it would have been beneficial to use localized strings from the very beginning, but setting up an app for localization isn't especially difficult. It's the actual translations that are difficult and expensive.
我的小样本表明，美国应用商店中的绝大多数应用程序都没有本地化为任何其他语言。
这在技术上可能很容易，但在编辑上可能非常困难，除非您有受过教育的多语言工作人员（雇用多个承包商来交叉审查翻译的语法正确性，进行多语言应用程序描述，应用程序文档，网站支持页面，营销材料等，这些语言可能是本地化应用程序所需的所有语言，使所有内容与每次更新/错误修复保持编辑同步。）
似乎许多应用程序仅在国际销售后才添加多语言支持。达到可以支持上述初始和持续成本的水平。
My small sample suggests that the vast majority of apps in the U.S. App store are not localized to any other language.
It may be technically easy, but can be editorially very difficult unless you have educated multi-lingual staff available (hiring multiple contractors to cross-review translations for grammatical correctness, doing multi-lingual app descriptions, app documentation, web site support pages, marketing materials, etc. in all the languages that might be expected for an app localized to those languages. Keeping all that editorially synchronized with every update/bug fix.)
It also appears that lot of apps add multi-lingual support only after International sales get to the level which can support the above initial and on-going costs.
我请他们深入探讨。
如果我需要默认答案，那就是“是的，准备本地化”。与删除、重建、重新测试周期相比，添加它所需的时间要少得多。
i ask them going into it.
if i need a default answer, it is 'yes, prepare for localization'. it takes far less time to add it as you go, than the remove, rebuild, retest cycles.