Anaphraseus

(8 votes)

Anaphraseus is a CAT (Computer Aided Translation) tool, an OpenOffice.org 2 macro set similar to the famous Wordfast. It works with the Wordfast Translation Memory format (*.TXT), and supports text segmentation.
Features:

  • Term Recognition.
  • Fuzzy Search.
  • Unicode UTF-16 TMX Export/Import
  • Plain text and Unicode UTF-16 TM, Glossary
  • User Glossary
  • German, Russian, Italian, Latvian localizations available at Sourceforge.net
Download extension
Operating System: System Independent
Compatible with: OpenOffice.org 2.0 or higher.
Official release: 1.23-beta
Date: 2009-Jul-02
Size: 82.19 KB
License: opensource | Read license
Further product information: Screenshots | Product details

Comments

new error

Anaphraseus 1.22b loaded my previous Wordfast TM fine, then I translated the first segment in my document and hit the "Translate" icon to move to the next segment. Now I got a new error: "OpenBasic Error in HideTranslation: 'Index out of defined range.' Line 53". No macro was opened. When I hit "OK", the next segment opens, and it seems I can translate it normally. Then I hit the "End Translation" icon and the "Clean-Up" icon. Then I opened my TM in a text editor but couldn't find the TU I just translated. Please help. I am using OpenOffice.org 3.0 and Windows XP Pro SP3. Thanks.

encountered error

I have been using Wordfast for years, so I would like to start using Anaphraseus, however after installing the extension and loading my existing Wordfast TM, I get the following error message: "Inadmissible value or data type. Index out of defined range." The macro LibAnaphrase/TMLoad is opened and the following statement in function GetTabVal() is selected: "GetTabVal = a(I)". 3150 of the 7249 TUs in the TM were loaded. The TM still works fine in Word with Wordfast. Please help. Thanks.

Since encountering the above error in Anaphraseus 1.21 (the latest version available at extensions.services.openoffice.org), I have installed version 1.22b (beta) available from sourceforge.net. The error seems to have been fixed. Now I will test the extension.