1	User Manual Araya XLIFF Editor Description how to use Araya to translate documents
2	Installation Installation goes into directory c:/Program Files/Araya. It is recommended not to change this as all initialization files map towards this directory. When the XLIFF Editor is started the first time it adapts the directory names in the various configuration files.
3	Before the first start… If you have receive a license file you need to copy the license file to the directory „ini“ before you start the XLIFF Editor the first time. Name of the license file: license.<name>.key
4	Starting Araya XLIFF Editor Go to directory: c:/Program Files/Araya Run: XLFEdit.exe Or double click
5	Special Actions when starting Araya XLIFF Editor for the first time During the first start the several files are rewritten and adapted to the current Araya path Several files are saved as backup All files in the Araya, lib and ini directory with ending .bak are back ups of the original files from the installation File installed indicates that XLIFF Editor has not yet been executed. After first XLIFF Editor start it is renamed to installed.bak Files involved in rewriting are: ARRAYPATHDIRECTORY/lib/eaglememex.ini ARRAYPATHDIRECTORY/eaglememex.properties ARRAYPATHDIRECTORY/lib/eaglememex.properties ARRAYPATHDIRECTORY/ini/catalogue.xml ARRAYPATHDIRECTORY/lib/emx_service_install.bat ARRAYPATHDIRECTORY/lib/getjavahome.bat ARRAYPATHDIRECTORY/lib/getold.bat ARRAYPATHDIRECTORY/lib/hsql_service_install.bat ARRAYPATHDIRECTORY/lib/rpcserver-install.bat ARRAYPATHDIRECTORY/lib/saveold.bat
6	Araya XLIFF Editor Start Screen
7	Translation Approach Usage of a translation memory model Re-usage of existing translation New translations are stored in TMX format in a database TMX = XML exchange format for translation databases; vendor independent Usage of a phrase translation approach Terms = (words, phrases) are automatically replaced within segments Roughly simulates a word by word translation approach
8	Segment Translation is done on a segment basis. A segment is either be defined as a sentence or a paragraph. This can be defined by the user (during the document conversion process). Segmentation methods should not be mixed up. For XML paragraph based segmentation is recommended.
9	XLIFF Editor
10	TM Datenbanktreffer
11	Right Mouse Button Functions 1
12	Right Mouse Functions 2
13	Right Mouse Functions 3
14	Right Mouse Functions 4
15	TM Database Matches
16	Format Display
17	Format Handling Format information is sequentially numbered. Format information is either displayed with green background color (matching format information) or red back ground color (not matching format information) Format information can only be deleted as a whole. It is not possible to add or remove characters in the format information.
18	Moving Format Information Sometimes it is necessary to move format to another position in the translation. This can simply be done by cut and paste the format information. It has to be remembered that such operation should take into account that the resulting movements should be done in such a way that the format ordering is still valid with regard to the original file format (e.g. XML).
19	Moving Format Information
20	Information and Icon bars
21	Icon Bar – Part 1
22	Icon Bars –Part 2
23	Navigation Buttons - Arrows
24	Navigation Buttons
25	Navigation Buttons
26	Translation Control Buttons Source
27	Translation Control Buttons TM Window
28	Information- and Status lines
29	The Four Translation Steps Convert Translate Check Convert back
30	Example Website
31	Step 1: Conversion Convert document or a set of documents (project) into an XLIFF document XLIFF – XML Standard supporting document format independent exchange for translating Translator should concentrate on text and not on layout Menu: File -> Convert File to XLIFF Format Or using Drag&Drop into an Araya window
32	Converter dialog
33	WinWord / RTF / OpenOffice Support In order to convert WinWord or RTF documents two options exist. Usage of OpenOffice for conversion Open Office must be installed. OpenOffice must be started as a service. The eaglememex.properties Datei must contain the entry:
34	WinWord / RTF / OpenOffice Support If MS Office is installed the conversion tools of MS can be used instead. The eaglememex.properties file must contain the entry: Old WinWord formats are converted to docx format. RTF can be converted by the standard Araya RF converter if both above options do not apply..
35	Segmentation Parameters
36	Translation of Segments
37	A New Translation
38	Modify a Match
39	Approving a Translation
40	Approve all and Approve (Checkbox) Translations are added to the TMX database, if either the source, the target or both segment do not exist in the database. The editor checks the correctness of the format information for “Approve All”, if the property eaglememex.RunFormatCheckBefore=true is set in the eaglememex.properties file. If the formats do not match Approve All only can be finished if all formats of all segments are correct. If OK is clicked approval process continues, if cancel ic clicked it is stopped.
41	Controlling TM Update Approval If entries are added to the TMX database, the option eaglememex.database.CheckAddingTMXEntry - in the eaglememex.properties file - controls, if an approval question is asked for or not. true asks for approval, false not. Approval is further more detailed through true activates approval questions for the operations false deactivates approval questions for the operations
42	Controlling Goto Approval Questions If a Go To operation is done, the option eaglememex.database.RunGotoCheckBefore - in the eaglememex.properties file - controls, if an approval question is asked for or not before the next segment is jumped to. true asks for approval, false not. Approval is further more detailed through true activates approval questions for the operations false deactivates approval questions for the operations
43	Modifying TMX Database Entries
44	Modifying a TM Entry
45	Buttons for Changing Entries
46	Functionality of the Buttons 1
47	Functionality of the Buttons 2
48	Validating length of TMX entries
49	Validation of Entries
50	Checking for not translated entries 1
51	Checking for not translated entries 1
52	Comparing Format of Entries
53	Searching using Entry ID
54	Right mouse click for Validate Entries etc.
55	Editing a Segment when Modifying a TMX Entry
56	Properties of an Entry
57	Splitting Entries These button splits up one entry into two different entries. First select all the segments which should go into a new entry. The press the Split Entry button. The selected segments in the entry are written into a new entry and deleted from the old entry. Function is mainly useful if two entries have been merged and one wants to correct this
58	Filtering Properties 1
59	Filtering Properties 2
60	Back Conversion
61	Back Converting all XLIFF Files in a Directory
62	Partially Translated Document
63	Creating TM Databases
64	Create TM Database Tables This option only creates the database tables, not the database itself. This option should be used if the database exists, and only the database tables should be created. This is useful, if an (Internet) provider provides access to a predefined database, which the user cannot create by himself. This option then enables the user to create the tables for that database. It access the existing database.
65	Internal Database If no database is activated, an internal database is automatically created or re-used. Its name is „InternalArayaTM“. It will be load automatically on start-up – if no other database is defined – and saved upon Exit.. When starting a warning is issued, if this database is loaded. If the internal database is used existing matches from other TMX databases or phrase translations are not removed. The standard case is that all matches are removed from a segment if the segment is displayed.
66	Creating Terminology Databases
67	Add an existing Database
68	Phrase/Word-by-Word Translation This translates words or phrased within a segment from the terminology database. This requires post processing of the translation. If the eaglememex property eaglememex.database.AutoSearchInTerm is true phrase translation is run automatically when a terminology database is selected (active).
69	Terminology Database
70	Terminology
71	Phrase Translation
72	Add Term to Terminology Database
73	Searching a Term or Phrase
74	Editing of Terminology Entries
75	Spell Checking The text contained in the target windows can be checked with a spell checker. This requires that ASPELL is configured. Plugins->Configure ASPELL Dictionary list is automatically recognized
76	Spell Checking Current segment Edit -> Spell Check All segments Edit -> Spell Check All Approved segments are not checked.
77	File Menu
78	Edit Menu
79	Project Menu 1
80	Project Menu 2
81	Go to Menu
82	Checking of the translations If a segment is left for another one, the option eaglememex.RunGotoCheckBefore=true checks, if the current translation exists in the TMX database. Depending on the settings of Options Menu, it is checked, if Source/Target are new Source exists in the database Translation already exists – this would lead to an additional translation for the source segment Source and target segment (translation) exist in different TMX database entries. This would lead to a merging of this entries. If „yes“ is chosen the next segment is chosen, in case of „No“ not. This would allow to correct the translation (target segment).
83	Options Menu
84	Special Options
85	Option Menu and Logging Araya writes a Log-file into the directory „log“. The name consists of „araya.“ + user name + „.“ + unique number (e.g.. araya.waldhoerk.6262.log). Within the file eaglememex.properties (lib directory) the gobal value is controlled thru. # Araya loglevel - influences the amount of log information written (this is comment!) eaglememex.log.loglevel=0 The higher the value the more information is written. Standard case should be 0. Values 1-4 are mainly needed for diagnosis purposes.
86	Options Menu
87	Tasks Menu
88	Terminology Menu
89	Database Menu
90	Database Menu 1
91	Database Menu 2
92	Database Menu 3
93	Database Menu 4
94	Database Menu 5
95	Import a csv file into a TMX database
96	Import csv Format 1. line - language code 2. … lines the entries to import Here the language separator is “;” (Semicolon)
97	Database Menu Terminology
98	Importing Terminology Files
99	Import Terminology Formats TBX Multiterm Csv
100	Export Terminology Export formats are TBX TMX XLIFF Multiterm CSV Output contains languages in the first line followed by the entries Separated by “,”
101	Das Review Menü
102	Plug-in Menu 1
103	Plug-in Menu 2
104	Help Menu
105	Araya Properties
106	Araya Log File
107	Monolingual Terminology Extraction 1
108	Monolingual Terminology Extraction 2
109	Monolingual Terminology Extraction 3
110	Example Output Term Extraction
111	Extraction Terms in TBX Format
112	Extraction Terms in TMX und XLIFF Format
113	Split TMX File
114	Merge TMX Files
115	Validate XML File
116	Count TUs/TUVs in a TMX File
117	About Araya Basic information about the Araya configuration is shown here. This can be important for error diagnosis E.g. if spell checking is configured correctly Using „Save…“ the information is stored in the specified file.
118	Translation Status Analysis 1
119	Translation Status Analysis 2
120	Translation Status Analysis 3
121	Ask before Adding Translations to TMX Database If those option are activated Araya asks if either new entry, a new translation, a new source segment (when translations exists) or if entries would be merged, should be added to the TMX database before adding to TMX database This question will not be asked if both source and target segment exist within one database entry.
122	Document Properties
123	Search and Replace Dialogue
124	Special Characters / Keyboard Special characters allows to enter characters not directly available from the keyboard. Special characters are defined with the property „eaglememex.specialchars.file=c:\\Araya\\ini\\specialchars.txt“ within the eaglememex.properties file.
125	Translation Projects
126	Project Details
127	Convert projects to XLIFF
128	Convert Projects back to Original Format
129	Project Translation Status Analysis
130	Creation of an Alignment Project Use „Projects -> Create Alignment Project“ Enter the name of the new alignment project
131	Alignment Projects
132	Comments Adding Files to Alignment Project Add Many Files Requires exactly the same number of files in source and target directory; otherwise noting is added Choose encoding and language before choosing files as the language codes will then be added automatically to the TMX output file name Based on the filename of the source directory file
133	Align Projects Files Align Projects aligns all the files specified in the project For conversion it uses the parameters like in Convert File to XLIFF Format…
134	Import TMX File
135	Import TMX File
136	Export TMX Database
137	Removing and Recreating TMX Databases
138	Translation Preview
139	Analyzing Format Information
140	Context View
141	Translation Annotations
142	Converting Files between different Character Encodings
143	Check and Recode TMX Files
144	Creation of TMX/XLIFF Test Files
145	Creation of TMX/XLIFF Test Files
146	Send XLIFF File
147	Adding Language Codes A set of predefined language codes is defined in the file „ini/lancodes.txt“. Additional language codes can be added by modifying this file. Here is an example:
148	Concordance Search
149	Concordance Search with Term Extraction
150	Tracing Modifications in the TMX Database
151	Example of a Trace File 1
152	Example of a Trace File 2
153	Example of a Trace File 3
154	Example of a Trace File 4
155	OpenTMS Integration Araya supports the OpenTMS tools See www.opentms.de or www.folt.de The OpenTMS tools are available in the free version of Araya or by setting the following lines in the eaglememex.properties file
156	Open TMS Tools
157	Impressum Heartsome Europe GmbH Friedrichstr. 17 D-90574 Roßtal Email: info@heartsome.de www.heartsome.de © 2006, 2007, 2009 Heartsome Europe GmbH