您如何管理字符串翻译过程? [英] How do you manage the String Translation Process?

问题描述

我正在从事一个软件项目，该项目需要翻译成30种语言.这意味着更改任何字符串都将导致较高的成本.此外，翻译不会一overnight而就，因为翻译包需要由不同的翻译人员处理，因此可能需要一段时间.

I am working on a Software Project that needs to be translated into 30 languages. This means that changing any string incurs into a relatively high cost. Additionally, translation does not happen overnight, because the translation package needs to be worked by different translators, so this might take a while.

以某种方式添加新功能很麻烦.在实际编写UI之前，我们可以考虑所有需要的字符串，但是有时由于错误修复或疏忽，我们仍然需要添加新的字符串.

Adding new features is cumbersome somehow. We can think up all the Strings that will be needed before we actually code the UI, but sometimes still we need to add new strings because of bug fixes or because of an oversight.

问题是，您如何管理所有这些过程?关于如何减轻翻译对软件项目的影响的任何技巧?如何统治字符串，而不是让字符串统治你?

So the question is, how do you manage all this process? Any tips in how to ease the impact of translation in the software project? How to rule the strings, instead of having the strings rule you?

我们正在使用Java，并且所有字符串都使用Resource Bundles进行了国际化，因此问题不在于本身的国际化，而是字符串的管理.

We are using Java and all Strings are internationalized using Resource Bundles, so the problem is not the internationalization per-se, but the management of the strings.

推荐答案

我不确定您要进行国际化的平台.之前，我已针对il8n应用程序的最佳方法写了一个答案.请参阅我该怎么办需要知道全球化一个asp.net应用程序吗?

I'm not sure the platform you're internationalizing in. I've written an answer before on the best way to il8n an application. See What do I need to know to globalize an asp.net application?

也就是说，管理翻译本身很困难.问题在于您将在多个页面上使用相同的文本.但是，您的框架可能不支持仅在一个文件中包含该文本(例如，asp.net中的资源文件，鼓励您使用每种语言使用一个资源文件).

That said - managing the translations themselves is hard. The problem is that you'll be using the same piece of text across multiple pages. Your framework may not, however, support only having that piece of text in one file (resource files in asp.net, for instance, encourage you to have one resource file per language).

我们发现处理事物的方式是拥有一个中央翻译数据库.我们创建了一个小型的.net应用程序，用于将资源文件中的译文导入到该数据库中，并将该数据库中的译文导出到资源文件中.因此，在构建过程中还有一个额外的步骤来构建资源文件.

The way that we found to work with things was to have a central database repository of translations. We created a small .net application to import translations from resource files into that database and to export translations from that database to resource files. There is, thus, an additional step in the build process to build the resource files.

您将要遇到的另一个问题是将翻译传递给翻译供应商，然后再传递回去.有两种方法-查看您的翻译供应商是否愿意接受XML文件并返回格式正确的XML文件.实际上，这是最好的方法之一，因为它允许您自动执行翻译文件的导入和导出.如果您的供应商允许，另一种选择是创建一个网站，让他们编辑翻译.

The other issue you're going to have is passing translations to your translation vendor and back. There are a couple ways for this - see if your translation vendor is willing to accept XML files and return properly formatted XML files. This is, really, one of the best ways, since it allows you to automate your import and export of translation files. Another alternative, if your vendor allows it, is to create a website to allow them to edit the translations.

最后，对于其他需要重复和手动操作的过程，翻译的答案将相同.自动化，自动化，自动化.自动化每件事.在这种情况下，复制粘贴不是您的朋友.

In the end, your answer for translations will be the same for any other process that requires repetition and manual work. Automate, automate, automate. Automate every single thing that you can. Copy and paste is not your friend in this scenario.

这篇关于您如何管理字符串翻译过程?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！