Ed. Note. Thanks to GlobalVision for this post. They are one of the pre-eminent providers of software localization services in the USA. If you are struggling with software localization, you can count on GlobalVision for excellent results.
In a previous software localization blog post, we discussed Wordbee’s ability to parse and process PO files for translation and localization. Today, we are covering .resx files translation. It is the last post of the series on software localization with Wordbee.
What Is a .RESX File?
.Net Resource (.resx) files consist of a monolingual file format used in Microsoft .Net applications. They contain menu, dialog box, error message, other instructional strings as well as dialog box sizing dimensions.
The syntax of a .resx resource file format consists of XML entries specifying objects and strings inside XML tags. Entries in resources are described in and pairs.
Here is an example of a .resx file:
Comments are added to strings using the optional field. Comments provide instructions and more context around the message text. Comments are not seen by the end-user and therefore do not need translation. They should be eliminated from the word count when creating the translation spec, budget and schedule.
Here is an example of a .resx file with a comment:
Benefits of .RESX Localization in Wordbee
Wordbee parses the .resx file presenting only the “Value” text of each entry to the translator. Wordbee will extract all the values text and present them in the editor for translation. Translators can hence translate the strings in a user-friendly environment without having to worry about inadvertently omitting or corrupting any XML code. Here is an example of .resx content:
And here is what that content will look like in Wordbee:
Note that Wordbee maintains the same order of the strings as they show up in the .resx files. If the strings are interdependent, their interdependence is not lost. This will be useful when leveraging the text from the translation memory in future updates, particularly with the 110% match feature that Wordbee offers.
By hiding all the XML code and properly training translators on how to handle variables, translated .resx files can be exported after translation, intact from any coding errors. This can save endless time in testing and debugging.
It will be nice however if the translators could see the comments in a protected mode for their reference only. It will help them better understand the context around short strings to achieve more accurate and faster translations.
If there are strings’ length-restrictions on dialog boxes or menus, which might happen due to limited screen space, the QA checker in Wordbee can be configured to warn the translator when their proposed translated text length exceeds the allowed limit.
Challenges Localizing .RESX Files
Wordbee offers limited control over the text to be translated. Since most .resx files’ variables, which come under the {0} and {1} format, are embedded in the Value string, translators must be careful not to inadvertently delete them.
You should therefore train your translators to properly handle variables to ensure their placement in the proper location in each string.
Wordbee does offer the option to exclude the content of an entire value from translation. It can check for patterns using regular expression and will mark the segment as non-translatable if the pattern is found.
After Translating .RESX Files
.resx files are often associated with forms and dialog boxes. Translation strings tend to increase or decrease in size after translation. As such, additional effort outside of Wordbee is needed to resize the dialog boxes or abbreviate the text to fit into form components’ buttons, labels etc.
As mentioned before, if Wordbee QA checker is pre-configured to warn the translator when this takes place, the translator can attend to these changes prior to releasing the translation to the engineering team. This will ensure that the properly abbreviated translations are stored in the translation memory of Wordbee for future version updates.
We however recommend that an engineering QA step outside of Wordbee still takes place. This is to ensure that all translated texts do conform to size limits imposed by the software that is being localized.
Converting .RESX Strings to Glossaries
Wordbee has released a new Terminology Management tool that will be very useful in the translation of software applications along with their supporting documentation, like: online help, reference manuals, users’ guides and tutorials.
With software applications, it is very important that translators remain consistent between the translation of the software user-interface and its supporting material. This will simplify the use of the application by the international end-user and facilitate its learning.
For instance, you do not want the online help to be referencing a user-interface string differently than the way it appears in the running software.
To maintain consistency, translators need to use all user-interface terminology and strings correctly throughout the entire product line.
Converting each .resx source and target language message strings to a glossary is hence very useful. After translation and QA, one can generate all languages’ glossaries and import them into the Terminology Management tool. This will guide translators throughout the localization and translation process and help them provide consistent target strings in the entire product, for all languages.
Additional Benefits of Terminology Management in Software Localization
Approved glossaries are extremely important in the process of translating a software application. Each application is often dependent on local use of industry-expressions that should be obeyed. By having each country approve the glossaries that will be used by translators, software publishers can ensure that their internationally released products are accepted by their in-country support personnel and by the local end-users.
Proper use of terminology can therefore have a great impact on the product’s consistency, accuracy and brand. By offering an accessible terminology management solution, Wordbee transparently facilitates end-user acceptance and success.
Software Localization with Wordbee
When you read our entire series of software localization posts, you would realize how effective Wordbee is in facilitating the translation and localization of software application files. Its ability to accurately process software files and handle translations online in a common and easy user-interface while storing the translations for future reuse, significantly reduces errors and streamlines the translation process.
Software is ubiquitous. Being able to release it simultaneously into all required languages is now the norm. With the advent of Translation Management Systems like Wordbee, the days where international users had to wait months before they can use the latest version of the software are gone!
The team at GlobalVision International, Inc. wishes everyone successful use of Wordbee in performing software localization tasks. We hope you enjoyed this series of articles. For more information, or if you need help with any of your .Properties, .XLS, .CSV, .XML, .PO and .RESX projects, do not hesitate to contact us.
埃德。注。感谢 GlobalVision 提供这一职位。他们是美国著名的软件本地化服务提供商之一。如果您在软件本地化方面遇到困难,您可以依靠 GlobalVision 获得出色的结果。
在之前的软件本地化博客中,我们讨论了 Wodbee 分析和处理 PO 文件以进行翻译和本地化的能力。今天,我们正在报道。文件翻译。这是 Wodbee 软件本地化系列的最后一篇文章。
什么是。RESX 文件?
。NetResource (.resx )文件由 Microsoft 使用的单一语言文件格式组成。网络应用程序。它们包含菜单、对话框、错误消息、其他指令字符串以及对话框大小维度。
a 的语法。resx 资源文件格式包括指定 XML 标签中的对象和字符串的 XML 项。资源中的项在< data >和< value >对中描述。
下面是一个例子。resx 文件:
使用可选< comments >字段将注释添加到字符串中。注释提供了关于消息文本的说明和更多上下文。最终用户看不到评论,因此不需要翻译。在创建翻译规范、预算和时间表时,应该从单词计数中删除它们。
下面是一个例子。带注释的 rex 文件:
的好处。在 Wordee 中的 RESTX 本地化
Wodbee 解析。resx 文件仅向翻译员呈现每个条目的“值”文本。Wodbee 将提取所有的值文本并将它们呈现在编辑器中进行翻译。因此,翻译器可以在用户友好的环境中翻译字符串,而不必担心无意中省略或损坏任何 XML 代码。下面是一个例子。resx 内容:
这里是 Worsbee 中的内容:
请注意, Wordee 维护字符串的顺序与它们在。resx 文件。如果字符串是相互依赖的,它们的相互依赖就不会丢失。这对于在将来的更新中利用翻译内存中的文本非常有用,特别是对于 Wodbee 提供的110%匹配特性。
通过隐藏所有 XML 代码并正确地培训翻译人员如何处理变量,翻译。翻译后可以导出 resx 文件,不会出现任何编码错误。这可以节省测试和调试的时间.
不过,如果译者能在受保护的模式下看到这些评论,仅供参考,那将是件好事。它将帮助他们更好地理解短字符串的上下文,从而实现更准确和更快的翻译。
如果对话框或菜单上存在字符串长度限制,这可能是由于屏幕空间有限而发生的,则可以配置 Wordbee 中的 QA 检查器,以便在翻译器建议的翻译文本长度超过允许的限制时警告翻译者。
本地化的挑战.RESTX 文件
Wordee 对要翻译的文本提供了有限的控制。因为大多数。在 Value 字符串中嵌入符合{0}和{1}格式的 resx 文件变量,翻译员必须小心避免无意中删除它们。
因此,您应该培训您的翻译人员正确处理变量,以确保它们在每个字符串中的正确位置。
Wodbee 确实提供了将整个值的内容排除在翻译之外的选项。它可以使用正则表达式检查模式,如果发现模式,则将段标记为不可转换。
翻译后.RESTX 文件
。resx 文件通常与表单和对话框相关联。翻译后,字符串的大小往往会增加或减少.因此,需要在 Wordbe 之外进行额外的工作,以调整对话框大小或将文本缩略到窗体组件的按钮、标签等中。
正如前面提到的,如果 Wordbeee QA 检查器被预先配置为在发生这种情况时警告翻译员,则翻译员可以在向工程团队发布翻译之前关注这些更改。这将确保将适当缩写的翻译存储在 Wordee 的翻译内存中,以便将来的版本更新。
然而,我们建议工程质量保证步骤以外的沃德比仍然发生。这是为了确保所有翻译文本都符合本地化软件所施加的大小限制。
转换。RESX 对术语表的字符串
Wodbee 发布了一个新的术语管理工具,该工具将对软件应用程序的翻译及其支持文档非常有用,例如:在线帮助、参考手册、用户指南和教程。
对于软件应用来说,在软件用户界面的翻译和支持材料之间保持一致是非常重要的。这将简化国际最终用户对应用程序的使用,并促进其学习。
例如,您不希望在线帮助以不同于运行中的软件中出现的方式引用用户界面字符串。
为了保持一致性,翻译员需要在整个产品线中正确使用所有用户界面术语和字符串。
转换每一个。因此,将源代码和目标语言消息字符串转换为术语表非常有用。翻译和 QA 之后,可以生成所有语言的词汇表,并将它们导入到术语管理工具中。这将指导翻译人员在整个本地化和翻译过程中,并帮助他们在整个产品中为所有语言提供一致的目标字符串。
软件本地化中术语管理的额外好处
已批准的术语表在翻译软件应用程序的过程中非常重要。每个应用程序通常依赖于应该遵守的行业表达式的本地使用。通过让每个国家批准翻译人员使用的词汇表,软件出版商可以确保其国际发布的产品被其国内支持人员和当地最终用户接受。
因此,正确使用术语可能对产品的一致性、准确性和品牌产生重大影响。通过提供可访问的术语管理解决方案, Wodbee 透明地促进了最终用户的接受和成功。
使用 Wordee 的软件本地化
当您阅读我们整个系列的软件本地化文章时,您将认识到 Wodbee 在促进软件应用程序文件的翻译和本地化方面是多么有效。它能够准确地处理软件文件,并在一个通用且简单的用户界面中在线处理翻译,同时存储翻译以供将来重用,大大减少了错误并简化了翻译过程。
软件无处不在。能够同时将其发布到所有必需的语言中是现在的标准。随着像 Wodbee 这样的翻译管理系统的出现,国际用户不得不等上几个月才能使用最新版本的软件的日子已经过去了!
GlobalVisionInternational , Inc .的团队希望每个人都能成功地使用 Wodbee 来执行软件本地化任务。我们希望你喜欢这一系列文章。要了解更多信息,或者如果您需要帮助您的任何一个。物业,。XLS ,。CSV ,。XML ,。采购订单和。RESX 项目,请随时与我们联系.
以上中文文本为机器翻译,存在不同程度偏差和错误,请理解并参考英文原文阅读。
阅读原文