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

问题描述

我正在处理一个需要翻译成 30 种语言的软件项目.这意味着更改任何字符串都会产生相对较高的成本.另外，翻译不是一朝一夕的事，因为翻译包需要由不同的翻译人员共同完成，所以这可能需要一段时间.

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，所有字符串都使用资源包进行国际化，所以问题不在于国际化本身，而是字符串的管理.

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屋！