是否“正确"?翻译错误信息? [英] Is it "right" to translate error messages?
问题描述
这在某种程度上是主观的，具体取决于目标翻译语言，但请耐心等待.
This is somehow subjective depending on the target translation language, but bear with me for a sec.
我最近参与了一个翻译项目.目标是将 MVC 框架的字符串翻译成希腊语.
I have recently been involved in a translation project. The goal was to translate the strings of an MVC framework to the Greek language.
70% 的框架语言字符串被翻译，但 30% 被有意遗漏.决定是我们不会翻译针对应用程序开发人员的错误消息.
70% of the language strings of the framework where translated, however 30% where intentionally left out. The decision was that we will not translate error messages aimed towards the developer of the application.
这背后的原因(简而言之)是:
The reasoning behind this (in short) was:
面向设计师/程序员.程序员(甚至设计师:))应该有一个基本的对英语的理解，至少足够他们可以在谷歌上搜索，如果他们不知道这意味着什么.(种族主义者?)
are aimed towards designers/programmers. Programmers ( and even designers :) ) should have a basic understanding of English, at least enough so they can search on it on Google if they do not know what it means. (racist?)
面向开发者在一个完美的世界里不应该显示给终端用户应用程序，因为它们涉及网络的内部运作应用程序本身.即你必须在您的数据库中设置数据库名称数据库配置文件."
are aimed towards the developer and in a perfect world should not be displayed to the end user of the application as they concern the inner workings of the web application itself. i.e "You must set the database name in your database config file."
也许最重要的是，他们创造了开发者的生活当他试图获得更多时更加努力有关的信息/帮助错误.比如上面的错误在 Google 中产生 8 个结果(在引号)，而它的希腊语翻译结果正好是 0.
and perhaps most importantly, they make the life of the developer harder when he tries to get more information/help regarding the error. For example the above error yields 8 results in Google (in quotes), whereas its Greek translation yields exactly 0.
我知道这取决于目标翻译语言的流行程度和应用程序本身.例如，我猜测有大量关于德语 SAP 错误消息的文档(我知道，我知道，SAP 是德语，但你明白了)，而不是关于随机应用程序 X 的希腊错误消息文档全球约有 500 台安装.
I know that this depends on the popularity of the target translation language and the application itself. For example I'm guessing that there are is vast amount of documentation regarding German SAP error messages (i know, i know, SAP IS German, but you get the point), as opposed to Greek Error Messages documentation regarding random application X which has about 500 installations worldwide.
总结一下:当您为应用程序开发语言翻译包时，您会翻译错误消息吗?你只为英语/西班牙语/德语/法语等主要语言做吗?还是你让它们完好无损?我不是在寻找正确"或正确"的答案，而是在寻找最佳实践"的答案，或者这个问题是否在您经历过的任何官方"标准/政策中定义.
So to summarize: When you develop language translation packs for your applications do you translate error messages? Do you only do for predominant languages like English/Spanish/German/French? Or do you leave them intact? I'm not looking for the "right" or "correct" answer, I'm looking for a "best-practices" answer, or if this problem is defined in any "official" standard/policy that you have had experience with.
推荐答案
一个包含内置错误消息的好的框架应该可以选择 i18n 它们.这对用户来说非常重要.
A good framework that includes built-in error messages should have an option to i18n them. This is important entirely for the user.
另一方面，不得翻译异常消息.你已经指出了一个重要的原因——搜索.是的，它们适用于开发人员，而不是最终用户.
Exceptions messages on the other hand must not be translated. You already pointed out an important reason - searching. And yes, they are for developers, not end-users.
如果异常消息也被用作向用户显示的消息，这是错误的设计.异常可能包含 i18n 键.
If an exception message is also used as a display message to the user, this is wrong design. Exceptions may contain i18n keys.
这篇关于是否“正确"?翻译错误信息?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
