These files can be translated with Tageditor through setting ini. They should be translated in most circumstances. Those files can be translated with Tageditor through setting ini. The glossary files in Flare project are generally located in ProjectGlossariesfolder with extension name of. The catalogue files in Flare project are generally located in ProjectTOCs folder with extension name of. They share the same ini with the topic during translation and are processed by Tageditor. They are usually some saved topics to facilitate repeated uses under Help Topic. The main content to translate in a Flare project is the web pages included in the Content folder.
The localization of a Flare project involves the following parts which need careful attention: (1) Identify translatable content (2) convert encoding and set up tools (3) edit and proof outputs. Presently, therefore, people are still used to handling directly Flare files with Computer-Aided Translation (CAT) tools.
But it may also extract some parts which do not require translating, such as parameters, resulting in a more complicated job. It is able to extract all translatable contents in order to reduce the editor’s workload. Madcap’s Lingo can be used for Flare for localization. And as a tool with one source but multiple outputs, Flare is now getting more and more popular. Like RoboHelp, Madcap Flare is a Help authoring tool loved by technical writers.
0 kommentar(er)
