![]() I know about the Contributor products, but here you can't see the topic structure, add and edit topics and so on. They do not need the compiler, targets, master pages, conditions etc., they basically just need the editor part of Flare. Starting with Flare we are only few persons who build and maintain Flare projects, but we have a number of people who writes input to Flare. And here I find that Lingo (just like Flare) simply fails. In this case the translator is not a professional translator, he just want a simple tool to translate a text line to something in his language. Maybe I'm the only person who have requests from a sales office or even customers who wants to translate one of our manuals or software help texts. My problem is that every time MadCap is talking about translations they always refer to professional translation services (who of cause knows everything about translations, XLIFF file formats, translation memory etc.). I'm also new to Lingo, but now have some experience with Flare over the recent years. Is there a floating license that we could use for the various Selling Partners to use as they need it? Also, although Lingo is pretty straight-forward, it does require some knowledge of the tool and the Selling Partners would prefer a common tool.Īnyone have experience working with multiple users to translate Flare content with common tools?Ĭhris cjs Propeller Head Posts: 11 Joined: Fri 1:37 pm The cost of multiple licenses might make Lingo prohibitive. Of course one option is the Selling Partner to use Lingo. xlf to Excel or a tool that the Seller Partner can use to easily add translations into the. I am stuck on either finding a method to convert. xlf -> Convert to Excel or other pervasive tool -> Translations by Selling Partner -> Convert back to. The high-level flow is as follows:įlare -> Lingo -> Export to. I am new to Lingo and have spent many hours researching and experimenting to find a process that will support translations from a selling partner using ubiquitous tools.
0 Comments
Leave a Reply. |