This release is important because it overcomes some of the immediate shortcomings of the earlier release, such as the following: Version 1, released in late 2007, was notable for its Google translate integration, the ability to translate strings/callouts embedded in Capture screenshots, "diffing" of past projects, and simplified translation tracking. If you have been doing regular translation work of your Flare/Blaze documentation or outsourced translation work, you owe it to yourself to give Madcap Lingo a try at least. The more you translate with translation memory, the easier and better it becomes progressively. Translation memory goes beyond saving time it improves accuracy of future translations by retaining a history of used segments. Translations are stored in a SQL Server Express database. Measured against these, Lingo is relatively young.
Established translation tools include SDL Trados, Transit, Wordfast, and Alchemy Catalyst. As a translation memory system, Madcap Lingo helps translators speed up and simplify the translation process of Madcap Flare/Blaze projects into another language. Madcap Lingo is Madcap's offering in the XML-based translation authoring solution space. Madcap Lingo - A Fully Integrated Translation Memory and Authoring Solution Daniel is part of a small team with an in-house translator. They translate their own English Flare help projects to Simplified Chinese with Madcap Lingo and have been using Madcap Lingo since version 1.
This article is a guest post by Daniel Ng.
0 kommentar(er)
