FlexyTrans这个工具从未听说过，从Proz上了解到：FlexyTrans和Catalyst非常相似。翻译公司Berlitz向其部分供应商提供过许可。FlexyTrans许可分为企业版和Lite版本。
FlexyTrans 将翻译内容保存在 Microsoft Access 数据库中，因此是可以将FlexyTrans数据库后缀名更改为mdb，然后使用Microsoft Access打开。
以下转载自 http://gogolleo.blog.sohu.com/114735470.html。
Step 1: Create a new project file
GOAL: Prepare translatable files for a new project.
Import the translations from existing files, and then prepare the translateble files for an update version.
ACTION:
1. File -> New project
Note: Parsers
2. Add files
3. First update
Step 2: Preprocess
GOAL: Analysis, Pre-Translate, For-Translator
ACTION:
1. Upload
Tools -> Project -> Options -> Upload
2. Update project
Just copy the file of V1 to V2 folder.
– FTTools: Leverage -> Encode
– Leverage (protect the status)
– FTTools: Leverage -> Decode
Note: Leading/Trailing spaces are ignored. A string composed only of spaces stands for <Empty String>.
3. Wordcount
– Set status
– Analysis -> Update Statistics
– File -> Project Management -> Project Status Report
4. Prepare RTF file for translation
– Show how to process Updated strings in FlexyTrans
(1) Grid -> Suggest -> Updated Strings Info
(2) Grid -> Suggest -> Paste Suggestion
You can have this grid appear by clicking on Tools -> Project -> Options, and in the Suggest Tab click on Suggest On Line and Update Suggest. Setting as this, the old content will appear when you click the updated strings.
– Filter: Not localized
Action: Gird -> Filter -> New: Status <> Localized
– Set status: Set the status for strings needn’t to be translated to “Localized”.
– Prepare RTF
5. FlexyTrans can check some error automatically while translating
Settings: Tools -> Project -> Options -> Validate
Check point:
– Accelerator mismatch
– Blank string mismatch
– Control characters (e.g.\r, \n, \0, etc.)
– Hotkey mismatch and validity
– Incorrect Spelling
– Leading Punctuation
– Leading spaces
– Size excess (+- 10 characters)
– Trailing Punctuation
– Trailing spaces
– Variables placeholders (e.g. %s, %1, etc)
6. Autotranslate
Action: File -> Translation -> Autotranslate
Step 3: Postprocess
GOAL:
1. Check whether there are errors in the files back from translation.
2. Resizing
3. Generate new localized files
4. Export glossary
Check point:
1. Consistency
Action: File -> Translation -> Check consistency
2. Hot keys
Action: Analysis -> Check Localized Hotkeys
Note: Check duplicate hotkeys only.
3. Validate (FTTools)
Action: Create a file including the strings needs to check, such as \r, \n, &, numeric, some words needn’t to be localized and so on.
4. Truncation
Action: Analyze -> Check Truncated Dialog Items
Resizing
1. View -> Locate Record WYSIWYG
2. View -> Locate Record in Project, then right click the dialog name, and then choose Open WYSIWYG Resource -> Both.
3. View -> Locate Record in Source Files
Generate
Note: Don’t forget changing the code_page, and so on.
Export glossary
Action:
1. Grid -> Export -> Table
2. File -> Translation -> Terminology Candidate
– Don’t choose Show Terminology as it will be exported: (Read Only)
Duplicate and Hotkey will appear
– Choose Show Terminology as it will be exported: (Read Only)
Don’t check any other checkbox: Duplicate and Hotkey will disappear