Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Dear Friends,

I would like to announce that we have just released version 0.8beta of the WordForge localization editor.

The WordForge Editor is specially prepared for working with either XLIFF or PO OpenOffice files.

If XLIFF files are used, then the number of features is much bigger, as it is possible to keep much more information in the files.

Some of its most important features are:

1) Immediate testing of quality of translation

-It recognizes OpenOffice variables, XML structures, and other constructions that must be replicated identically in the target, and gives an error if they are not present. - It recognizes OpenOffice accelerator keys, and ignores them in glossary and TM use. - It can also test the most usual problems in strings, such as extra or missing spaces, punctuation (it can check punctuation in scripts other than English).
- It can test correct use of glossary, if glossary is available.
- It can test correct replication of functions, URLs, e-mail addresses and many other types of objects in the target.

Errors can be overidden by the user, but they are recorded in XLIFF files (not the case in POs). Files and full projects can be tested, and the strings that have errors will be marked for analysis.
Which tests to run in real time can be easily parametrized by user.

A file that is translated in the WordForge Editor with the testing feature enabled should always pass GSICHECK without any problems.

2) Glossary support.

- Glossaries are entered in the system, and then glossary words are indicated in the source string, and translation is given in a separate window.

3) Translation memory.

- Translation memory can be applied to files in a very flexible way, in some cases putting suggestions in the target (if the user wants to) and in some other cases it is stored in XLIFF files (or as temporary suggestions if working with PO).

4) Use of reference (third) languages

5) Embedding of glossary and Translation memories in XLIFF files.

- A translation manager can take all the files of a project, and embed in them the relevant glossary and translation memory. Only the glossary terms that are relevant to a file are embedded in the file (a subset of the complete glossary), and only TM suggestions that the translation manager choses to embed are embedded (percentage of match, etc.). - Using this, the translation manager can send out files for translation to the team without needing them to have either the glossary or the TM, as everything is in the file.

6) Spell-checking of target.

7) Thesaurus for both source and target.

8) Filters for OpenOffice and other formats are accessed through the graphic user interface.

- Fully functional filters for OpenOffice SDF to/from XLIFF format are available, as well as an XLIFF upgrade filter

9) Files are packed into projects

- Batch operation on glossary and TM can be done on all the files of a project at the same time.

Linux and Windows version of the editor are available in:

https://sourceforge.net/projects/wordforge2/

Regards,

Javier




--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://www.libreoffice.org/lists/l10n/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.