Heartsome Truly and completely cross platform, supportive of all key industry standards, namely XLIFF, TMX, TBX, Unlimited support for languages
Heartsome's products are all dependent on the use of a recent version of Java Runtime (at least Version 1.4.2) together with a highly efficient database. These are applications that will only thrive in computer systems equipped with a relatively large RAM, at least 512KB for those running the server version and 256KB for those running the client version.
Apart from higher RAM, the other associated system requirements are not exceptional: a normal processor with a speed of 1 GHz or more, and a 40 GB hard disk with space enough to install the software and as much space as needed for the database, a few GB should be adequate for most individuals.
We consider ourselves the most unique in the light of the following:
The basic requirements are:
Ensure that you have correctly installed Java 1.4.x and that a JVM is in your path.
All Heartsome's software uses Java technology, a groundbreaking computing platform released by Sun Microsystems in 1995. Java technology opens up a wealth of new possibilities for IT users. It enables Heartsome as well to develop programs that are genuinely cross-platform, that is, programs that run on any given computer, which is equipped with the Java Runtime Environment (JRE).
The version of JRE required for running Heartsome's software is 1.4.2x or higher. This is a relatively new version of Java and we always opt for the newest technology. It is available for Windows (except Windows 95), Macintosh, Linux and UNIX operating systems.
Bi-directional languages are currently supported on Microsoft Windows only because the technology foundation of Heartsome's tools, Eclipse SWT, has yet to implement support for bidirectional languages in any other platform.Read more
This problem is unique to Windows 2000 users on their trying to run Java applications. It normally affects those who have failed to faithfully update their Windows operating systems. This applies as well to those using Microsoft Office software failing to update with patches and bug fixes made available by Microsoft. In simple language, it is caused by the existence of one or more empty spaces in the directory name (path to a file). There are two ways to resolve the problem:
Heartsome's tools are wholly compliant with TMX 1.1, 1.2, 1.3 and 1.4 at Levels 1 and 2.
TMX files generated with Heartsome's tools have successfully been tested with Trados version 6.5.5, SDLX and Déjà Vu X.
Yes, Heartsome's tools include XML catalogue management. Our tools and provide configuration options for converting, aligning and extracting terms from any XML document accompanied with a DTD.Read more
The technology that underlines the foundation of Heartsome's Translation tools is known as "translation memory" (TM). It is a language technology that enables the translation of segments (paragraphs, sentences or phrases) of documents by searching for similar segments in a database and suggesting matches that are found in the database as possible translations. It may further suggest several translations for a paragraph, a sentence or a phrase.
The translation memory application, which implements a search logic designed by the developer of the tool, is supported by a set of file format converters. These converters analyse the source file in such a manner that another tool, the segmenter, can come in to break the file into segments.
The database module, which serves as the core of Heartsome's tools, is specially designed to support unlimited languages across all operating systems. It comes complete with a cross-lingual search engine that automatically searches the translation memory database for matching entries for each and every segment. The level of match varies from 100% matches to a low of 35%. This facility enables users to locate, retrieve and reuse translations done previously, whether done several years ago or just a few minutes back. Without this facility, users may end up translating the same text repeatedly. Apart from duplicating the effort, it is also very likely that the same text may be translated differently, thus affecting the consistency in the document.
Heartsome's database engine is fully compliant with the one and only industry standard for managing and exchanging translation memory - TMX (Translation Memory eXchange). It is entirely possible to export databases generated or maintained by Heartsome translation tools for use in any other translation tools that support TMX Standard V1.4 or higher.
Three factors are relevant when importing a TMX file into a database. They are:
1. Source language settings
2. Duplicated entries
3. Presence/absence of "tuid" attribute in all
Source language settings
Every TMX file must declare a source language in its header. If the file can be used to translate from any language into any other language contained in the file, then the source language must be set to *all*.
Some CAT tools can only translate in one direction and thus they must indicate one of the languages present in the file as the "source language" and they usually restrict TMX files to having only two languages.
Importing a file that indicates that it can be only used to translate in one direction requires additional efforts for checking if there are legacy entries that need updates in the database and that procedure consumes time.
The following table shows the differences when storing a TMX file with 20,000 entries into a database:
If a file has many duplicated entries, it is better to remove them before storing in a database. When you use the Remove Duplicates feature of the TMX Editor, you work with a file stored in memory and the removal is fast. When you leave the task to be performed at import time, duplicates are checked against the data stored in the database and that procedure is noticeable slower. If you know that your file has many duplicates, remove them in advance.
Presence/absence of "tuid" attributes
When importing a file, translation units are processed one at a time.
Please note: It is strongly recommended that the "tuid" attribute be unique for all imported TMX files. If you import a TMX file with the same "tuid" for segments as the "tuid" for segments already in your database then you risk loosing the data entered previously in your database.
The TMX Editor includes an option called "Generate New TU IDs" in Tasks menu that you can use to generate new clean IDs for all TUs in a TMX file at once.
If you have a TMX document with 3 or more languages that looks like this:
you can reorder its translation units using Heartsome's TMX Editor and make them look like this:
The steps for performing the reorganization are:
Here is a short recipe for installing Aspell on Windows:
Since, unlike Linux users, Mac users often have little experience with a command-line interface, below is a step-by-step approach to installing Aspell for use with the Heartsome suite.
All Heartsome's tools require Java 1.5 or better. You can download Java for free here.
The programs may complain saying that Java is not properly installed. If you are sure that you have Java, you can follow the instructions from the Java Tutorial to verify and correct its configuration.
Heartsome Translation Suite works OK with Oracle 9.2. One very important detail to keep in mind: Oracle 9.2 installs and uses Java 1.3.1 and Java 1.1.8. Those two versions of Java are incompatible with Heartsome's tools so you must adjust the PATH environment variable to make Java 1.4 or better the default JRE when using Heartsome's tools in the server machine.Read more
Heartsome's XLIFF Translation Editor supports these formats:
Configuration files for the following XML formats are included with the editor: