对较大的文本值进行较小的编辑时，如何有效地使用gettext PO文件 [英] How to efficiently work with gettext PO files when making small edits to large text values

问题描述

在对大型msgid值进行少量编辑时，寻找有关如何有效使用gettext PO文件的技巧和/或工具。

Looking for tips and/or tools on how to efficiently work with gettext PO files when making small edits to large msgid values.

示例：我们有很多-存储在我们的PO消息目录文件中的句子/多段消息。如果我们对消息进行非常小的更改，例如编辑单个句子甚至纠正标点符号，则在运行msgmerge实用程序时，我们将失去原始翻译。

Example: We have lots of multi-sentence/multi-paragraph messages that are stored in our PO message catalog files. If we make a very minor change to a message, perhaps editing a single sentence or even correcting punctuation, we lose our original translation when we run the msgmerge utility.

我们的翻译人员不会从头开始重新翻译长消息（已经通过编辑批准的过程），而是返回其PO文件的备份副本并手动搜索最后一个msgid / msgstr转换对的文本，然后将它们与当前msgid值进行比较以查看已更改的内容，然后复制并粘贴最后一个转换的文本，然后对其进行编辑以反映更新的msgid值。

Rather than re-translate long messages (that have already gone through an editorial approval process) from scratch, our translators return to backup copies of their PO files and manually search for the text of the last msgid/msgstr translation pair which they then diff against the current msgid values to see what has changed, followed by a copy and paste of the last translation which they then edit to reflect the updated msgid value.

工作量很大！当然，必须有更好的方法来处理这种类型的工作流程？

That's a lot of work! Certainly there must be a better way of handling this type of workflow?

是否有最佳实践方法来存档和查找不再存在于PO文件中的先前翻译？想到的一个想法是在邮件的文本或邮件前面的注释中存储唯一的msg ID，并使用该ID检索以前的msgid / msgstr翻译对以进行审核。还是有PO编辑器或在线服务可以使此过程更有效？

Is there a best practice way to archive and find previous translations that are no longer in a PO file? One idea that comes to mind is to store a unique msg id in the text of our messages or in the comments that precede our message and use this id to retrieve previous msgid/msgstr translation pairs for review. Or are there PO editors or online services that make this process more efficient?

谢谢您，马尔科姆（马尔科姆）

Thank you, Malcolm

推荐答案

Virtaal 的翻译记忆库支持可能对此有所帮助。如果您的原始单位在翻译记忆库中，则会在一定的变化范围内（基于Levenshtein距离）显示（有差异）。它仍将包含原始（未修改的）翻译，但是至少原始文本更易于访问并且突出显示了差异。

Virtaal's translation memory support can probably help with this. If your original units are in the translation memory, it will be shown (with differences) within a certain margin of change (based on Levenshtein distance). It will still contain the original (unmodified) translation, but at least the original text is more easily accessible and the differences highlighted.

我不确定100％，但是 Pootle 也可能提供基于Web的解决方案。如果您需要任何帮助，请在FreeNode上的#pootle中询问。

I'm not 100% sure, but Pootle might also offer a web based solution. If you need any help, ask in #pootle on FreeNode.

当然，更普遍的改进是尽可能地将单元分开/分段。

The more general improvement is, of course, to separate/segment the units as far as possible.

这篇关于对较大的文本值进行较小的编辑时，如何有效地使用gettext PO文件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！