编程中的非英文域名命名问题 [英] Non-English domain naming issues in programming

问题描述

大多数编程代码，我想象是用英文写的。但是我很好奇，人们如何处理这里的命名问题。在一些商务领域内进行了大量的编程，通常对于某些程序，项目通常具有良好的规定。

我来自丹麦，我从事的工作很多有一个名为indblikskode的术语，这种翻译成洞察代码。那么我在C＃代码中使用与这个相关的一些Web服务的string indblikskode = ...这一行呢？或者我是否尝试使用翻译，例如insightcode？我所使用的商务语言甚至不一致，例如使用术语organisatorisk enhed（组织单位），但同样经常使用缩写OU，这显然是英文缩写。

其他人如何处理这个命名问题，同时保持一致和稳定（从代码中的简单变量名称到数据库表到服务器名称）？ p>

重复：

• 标识符和注释应始终是英文还是应用程序和开发人员的母语？


• 您是否使用其他语言而不是英语？

解决方案

查看我的问题和答案这里。

基本上它取决于您的组织和应用程序。如果您的公司，开发人员和客户都使用相同的母语，并且期望它能够保持这种状态，那么让每个人都成为兼职翻译人员也是非常有效的。纯粹假设未来优势的生产力损失相当大。 YAGNI。

如果这是一家大型国际公司，或者如果有具体计划在国际上扩张或在海外完成一些工作，那当然是另一回事。 p>

Most programming code, I imagine is written in English. But I'm curious how people are handling the issue of naming herein. A lot of programming is done within some bussiness domain, usually with well established terms for certain procedures, items.

I'm from Denmark for instance, and something I work a lot with has a term called "indblikskode", which sort of translates to "insight code". So, do I use the line "string indblikskode = ..." in the C# code for some web service related to this? Or do I try to use a translation, such as "insightcode"? The bussiness I'm in isn't even consistent in its language, for instance using the term "organisatorisk enhed" (organizatorical unit), but just as often using the abbreviation "OU", which is obviously abbreviated from the English.

How do other people handle this naming issue, while keeping consistent, and sane (in everything from simple variable names in your code, to database tables, to server names)?

Duplicates:

• Should identifiers and comments be always in English or in the native language of the application and developers?
• Do you use another language instead of English?

解决方案

See my question and answer here.

Basically it depends on your organization and the application. If your company, developers and customers all speak the same native language and you expect it to stay that way, then it would be extremely counter-productive to have everyone become a part-time translator as well. Considerable productivity loss for a purely hypothetical future advantage. YAGNI.

If it's a large international company, or if there are concrete plans to expand internationally or have some work done offshore, it's a different matter, of course.

这篇关于编程中的非英文域名命名问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！