它是“正确"的吗?翻译错误消息? [英] 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:
-
是针对设计师/程序员的. 程序员(甚至是设计师:))都应具备基本知识 对英语的了解，至少足以 他们可以在Google上搜索 他们不知道这意味着什么. (种族主义者?)
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.
推荐答案
一个包含内置错误消息的良好框架应该可以选择对它们进行错误提示.这对用户完全重要.
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屋！
