Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2342

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2343

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2344

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2345

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2346

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2347

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2348

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2349

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2350

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2342

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2343

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2344

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2345

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2346

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2347

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2348

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2349

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2350

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2342

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2343

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2344

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2345

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2346

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2347

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2348

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2349

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2350

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2342

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2343

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2344

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2345

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2346

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2347

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2348

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2349

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2350

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2342

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2343

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2344

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2345

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2346

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2347

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2348

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2349

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2350

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2342

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2343

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2344

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2345

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2346

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2347

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2348

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2349

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2350
Changes - Heartsome Europe Arayapedia

Changes


Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2342

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2343

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2344

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2345

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2346

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2347

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2348

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2349

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/23/d187578198/htdocs/mediawiki/includes/parser/Parser.php on line 2350
From Heartsome Europe Arayapedia

Jump to: navigation, search
(Changes in the last versions)
 
Line 1: Line 1:
-
Araya 16.00
+
'''27.7e - 20.12.2012'''
-
Araya Xliff Editor
+
# Improved display for askAddTranslation; texts in red and bold and bigger
-
- correcting display and use default database after close / open database. Now after a xliff file is closed (and the database has changed for the closed xliff file) the editor reinstatiates the old (default) database again. The default data base is only stored when xliff editor finishes.
+
-
TMX Database:
+
'''27.7c - 16/17.12.2012'''
 +
 
 +
# added check single " />" and "/>". The "/>"  and replace "/>" with " />" for monolingual objects
 +
 
 +
'''27.7 - 16/17.12.2012'''
 +
 
 +
# added removing duplicate ph elements which end like this: " />" and "/>". The "/>" monolingual entries will be removed if the mono is equal ecept this difference. Done in TMX Editentry as now tool.
 +
# added check for single " />" and "/>". The "/>"  and replace "/>" with " />"
 +
# removed bug when displaying changes in the properties window of tmx edit entry; date now displayed.
 +
'''27.6a - 12.12.2012'''
 +
# allow disable / enable additional approve item tools with eaglememex.ShowAdditionalApproveToolItems=false in eaglememex properties; only for the add button used
 +
 
 +
'''27.5 - 12.12.2012'''
 +
 
 +
# save and restore position of xliff editor in user configuration filename
 +
# remove bug when checking for format tags
 +
# allow disable / enable additional approve item tools with eaglememex.ShowAdditionalApproveToolItems=false in eaglememex properties
 +
# correct setting eaglememex.usePartiallyTranslatedTargetsForRepetions=true to eaglememex.usePartiallyTranslatedTargetsForRepetitions=true
 +
# remove <ph> part from AskAddTranslation; display only contents
 +
# mark blanks at the end of a segment
 +
 
 +
 
 +
'''27.4 - 06.12.2012'''
 +
 
 +
# adapted dialogue for checking dublicate entries; corrected spelling errors
 +
# eaglememex.UseOldAskAddTranslation = false for activating the new dialogue version
 +
# added new tool item for saving translations
 +
green: use dialogue box for asking saving new translations
 +
grren to red: save and add new translaton to existing translations
 +
blue: replace existing translations
 +
 
 +
'''27.1 - 04.12.2012'''
 +
 
 +
# new dialogue for checking dublicate entries
 +
# eaglememex.UseOldAskAddTranslation = false for activating the new dialogue version
 +
# slider for font size changing
 +
 
 +
 
 +
'''27.0 - 13.11.2012'''
 +
 
 +
# Using partially translated segments
 +
# Setting the visibility in the options menu (in eaglememex.properties)
 +
# Menu Item: Use not approved translations for repetitions
 +
# usePartiallyTranslatedRepetions=true,false
 +
# Setting the global initial value (both properties below)
 +
 
 +
# use partially translated targets for translation matches
 +
- eaglememex.usePartiallyTranslatedTargetsForRepetions=true
 +
 
 +
- usePartiallyTranslatedTargetsForRepetitions=true
 +
 
 +
'''26.7 - 07.11.2012'''
 +
 
 +
usePartiallyTranslatedRepetions - default is now true
 +
 
 +
'''26.7 - 07.11.2012'''
 +
corrected handling:
 +
 
 +
Testserver: <ph ctype="bold" id="0">&lt;geraetetyp /&gt;</ph>
 +
 
 +
Prodserver: <ph ctype="bold" id="0">&lt;geraetetyp/&gt;</ph>
 +
 
 +
Reason:XML converter now adds all the default attributes and chanes <x/> to <x />! Thus matching with entries may cause a difference.
 +
 
 +
 
 +
'''26.6 - 17.09.2012'''
 +
 
 +
- minor corrections
 +
 
 +
Using Java 6 or Java 7: Both versions of Java are supported.
 +
 
 +
Using the 64bit version of Java: 64bit Java is much faster and supports much more memory. Thus it is receommended to use the 64bit version. It does not really matter if Araya is installed into Program Files or Program Files (x86). Most import ist that the correct java version is called.
 +
 
 +
There are two exe's available (the same procedure applies to all Araya based applications, all in the mai directory of Araya):
 +
XLFEdit.exe
 +
XLFEdit64.exe
 +
 
 +
XLFEdit.exe uses the file xliffeditorclasspath to read the configuration for 32bit Java,
 +
XLFEdit64.exe uses the file xliffeditorclasspath64 to read the configuration for 64bit Java,
 +
 
 +
The configuration files use the following structure:
 +
 
 +
 
 +
lib\Win32\4233\swt.jar;lib\arayaserver.jar;lib\external.jar;lib\jaybird-full-2.2.0.jar;lib\hsqldb.jar;lib\mysql-connector-java-5.1.7-bin.jar;lib\derby.jar;lib\db2jcc.jar;lib\db2jcc_license_c.jar;lib\axion-1.0-M2.jar;lib\h2.jar;lib\jtds-1.2.jar;lib\sqljdbc4.jar;lib\hunspell\hunspell.jar;lib\hunspell\hunspell-win32-x86.jar;lib\hunspell\jna-win32-x86.jar;lib\hunspell\jna.jar;lib\hunspell\jna-jws.jar;lib\hunspell\hunspell-jws.jar;lib\postgresql-8.3-604.jdbc4.jar;dbjars\antlr-2.7.6.jar;dbjars\asm.jar;dbjars\cglib-2.1.3.jar;dbjars\commons-collections.jar;dbjars\commons-dbcp.jar;dbjars\commons-logging-1.0.4.jar;dbjars\commons-pool.jar;dbjars\dom4j-1.6.1.jar;dbjars\ejb3-persistence.jar;dbjars\hibernate-annotations.jar;dbjars\hibernate-cglib-repack-2.1_3.jar;dbjars\hibernate-commons-annotations.jar;dbjars\hibernate-entitymanager.jar;dbjars\hibernate-search.jar;dbjars\hibernate-testing.jar;dbjars\hibernate-validator.jar;dbjars\hibernate3.jar;dbjars\javassist-3.4.GA.jar;dbjars\jta.jar;dbjars\log4j-1.2.9.jar;dbjars\lucene-core.jar;dbjars\lucene-analyzers.jar;lib\araya-tokenizer.jar;lib\LexTo.jar;lib\jconn4.jar;lib\jconn3.jar
 +
 
 +
-Xms128M
 +
 
 +
-Xmx1550M
 +
 
 +
-XX:-UseGCOverheadLimit
 +
 
 +
javaw
 +
 
 +
-Djava.library.path=.\\lib\\Win32\\4233
 +
 
 +
 
 +
The first line with the jar libraries should not be changed.
 +
 
 +
-Xms128M
 +
 
 +
-Xmx1550M
 +
 
 +
define the available memory. If problems with starting Araya appear changing the value of -Xmx1550M to a smaller value should solve the problem (e.g. to -Xmx1000M). This memory allocation is dependent on the available memory and thus ajustments should help
 +
 
 +
 
 +
The line "javaw" defined which java version to use (in this case the default Java virtual machine) is used. It can be changed to the path where Java ist isntalled.
 +
 
 +
The follwowing lines from the 64bit version (xliffeditorclasspath64) demonstrate this:
 +
 
 +
lib\Win64\4233\swt.jar;lib\arayaserver.jar;lib\external.jar;lib\firebirdsql-full.jar;lib\hsqldb.jar;lib\mysql-connector-java-5.1.7-bin.jar;lib\derby.jar;lib\db2jcc.jar;lib\db2jcc_license_c.jar;lib\axion-1.0-M2.jar;lib\h2.jar;lib\jtds-1.2.jar;lib\sqljdbc4.jar;lib\hunspell\hunspell.jar;lib\hunspell\hunspell-win32-x86.jar;lib\hunspell\jna-win32-x86.jar;lib\hunspell\jna.jar;lib\hunspell\jna-jws.jar;lib\hunspell\hunspell-jws.jar;lib\postgresql-8.3-604.jdbc4.jar;dbjars\antlr-2.7.6.jar;dbjars\asm.jar;dbjars\cglib-2.1.3.jar;dbjars\commons-collections.jar;dbjars\commons-dbcp.jar;dbjars\commons-logging-1.0.4.jar;dbjars\commons-pool.jar;dbjars\dom4j-1.6.1.jar;dbjars\ejb3-persistence.jar;dbjars\hibernate-annotations.jar;dbjars\hibernate-cglib-repack-2.1_3.jar;dbjars\hibernate-commons-annotations.jar;dbjars\hibernate-entitymanager.jar;dbjars\hibernate-search.jar;dbjars\hibernate-testing.jar;dbjars\hibernate-validator.jar;dbjars\hibernate3.jar;dbjars\javassist-3.4.GA.jar;dbjars\jta.jar;dbjars\log4j-1.2.9.jar;dbjars\lucene-core.jar;dbjars\lucene-analyzers.jar;lib\araya-tokenizer.jar;lib\LexTo.jar;lib\jconn4.jar;lib\jconn3.jar
 +
 
 +
-Xms128M
 +
 
 +
-Xmx4000M
 +
 
 +
-XX:-UseGCOverheadLimit
 +
 
 +
c:\Program Files\Java\jre6\bin\javaw
 +
 
 +
-Djava.library.path=.\lib\Win64\4233
 +
 
 +
Here Java is used from the directory "c:\Program Files\Java\jre6\bin\javaw". Adapatations to other version can be done, e.g. "c:\Program Files\Java\jre7\bin\javaw"
 +
 
 +
Please also note that in this example the memory is extended to 4GB using  -Xmx4000M.
 +
 
 +
'''26.3 - 19.06.2012'''
 +
 
 +
- non breakable space show in add tmx entry dialog
 +
 
 +
- removed bug when merging entries (entries not added)
 +
 
 +
'''26.2 - 18.06.2012'''
 +
 
 +
- removed bug wenn similarity searching with TMXEditEntry
 +
 
 +
- added replaceall translation in query dialog
 +
 
 +
- internal matches not duplicated any more
 +
 
 +
'''26.1 - 25.05.2012'''
 +
 
 +
Intern existing not approved translations are now added as alt-trans, shown in yellow. Those translations are not stored in the xliff alt-trans list!
 +
 
 +
 
 +
'''26.0 - 23.05.2012'''
 +
 
 +
Approve Log modified
 +
TranslationStatus display - cirrected display of translated segments (now they are also counted even if approved!)
 +
 
 +
'''25.9 - 11.05.2012'''
 +
 
 +
Removed a problem aith approved = yes and translate = no
 +
 
 +
'''25.8'''
 +
 
 +
Removed a problem in phrase translation with -, [, ] characters
 +
 
 +
'''25.7'''
 +
 
 +
Removed problem when searchin with cocordancy and languages.
 +
 
 +
'''25.6'''
 +
 
 +
Removed bug when importing all approved translation and delete old (if several translations existed and the same one as the target translation was in the tmx database the old translations where not removed).
 +
 
 +
'''25.4 '''
 +
# Removed Right Click Disapprove / Approve bug
 +
# Change Title According to Review Status
 +
# Added Import all approved translations and delete existin translations
 +
 
 +
'''25.3 (a) - 12.12.2011'''
 +
 
 +
Corrected time and date saving in export and import
 +
 
 +
'''25.3 - 08.12.2011'''
 +
 
 +
remove bug in word counint (tags not counted anymore).
 +
 
 +
HTML Preview now adds ".context" to the file name to differentiate it from the status analysis html file
 +
 
 +
'''25.2 - 17.11.2011'''
 +
 
 +
Removed a problem when using PT traslate; added regex char quoting for -, []
 +
 
 +
'''25.0 - 14.10.2011'''
 +
 
 +
Changed type of times functions from int to long
 +
 
 +
Removes probelm when determining the lats change done to database
 +
 
 +
'''24.9a - 05.10.2011'''
 +
added export for term extraction
 +
 
 +
REM 1 term extraction csv file
 +
 
 +
REM 2 format (TBX)
 +
 
 +
REM 3 export approved only (true / false)
 +
 
 +
REM 4 export > score value
 +
 
 +
SET JARS=lib\arayaserver.jar;lib\Win32\swt.jar;lib\external.jar
 +
 
 +
call java -Xmx1024m -cp .;%JARS% com.araya.BiExtractor.Exporter %1 %2 %3 %4
 +
 
 +
 
 +
'''24.9 - 22.09.2011'''
 +
 
 +
Procect Conversion: Corrected Max match usage.
 +
 
 +
'''24.8 - 14.09.2011'''
 +
 
 +
Removing intermediate xlf file produced during xslt transformation
 +
 
 +
'''24.7 - 31.8.2011'''
 +
Direct Search - bug removed for update questions
 +
LogFile read and displayed as UTF-8 now
 +
 
 +
'''24.6 - 09.8.2011'''
 +
improved full text search in SQL Server - adaptave ranking depening on blanks in segment: if no rank = 0 used
 +
Ranking can be set now in config file
 +
 
 +
<directFuzzyKeyRank>50</directFuzzyKeyRank>
 +
 
 +
'''24.4 - 12.07.2011'''
 +
 
 +
- Support 32bit and 64bit Java
 +
 
 +
64bit: exes ending with 64.exe; requires 64-bit Java found in c:\Program Files\Java\jre6\bin\javaw
 +
 
 +
# biedit64.exe
 +
# bitmx64.exe
 +
# tmxedit64.exe
 +
# tmxeditentry64.exe
 +
# XLFEdit64.exe
 +
 +
If not in c:\Program Files\Java\jre6\bin\javaw changes required in the files
 +
 
 +
# tmxeditentryclasspath64
 +
# xliffeditorclasspath64
 +
# datasourceeditorpath64
 +
# bitmxclasspath64
 +
# biextractclasspath64
 +
 
 +
java path can now be configured in the *classpath files
 +
 
 +
Advantage: More memory supported (up to the limit of installed memory)
 +
 
 +
# Error correct in tmxeditentry (editing crash removed)
 +
# Improvements and new format in term extraction
 +
# Databases: db-MsSQL2008FT.xml
 +
 
 +
Loading the whole tmx database in main meory can be now controlled thrue menu item in Database menu
 +
This switch is only available for SQLServer 2008 with full text index installed
 +
 
 +
 
 +
'''24.3 - 30.03.2011'''
 +
 
 +
Option: Do not Search in TMX Database with Arrows - corrected the string; before the real action was the other way round
 +
 
 +
'''24.2 - 24.03.2011'''
 +
 
 +
- removed some bugs and update problems; add on creating translation packages in Menu "File"
 +
 
 +
 
 +
 
 +
'''23.12 - 16.02.2011'''
 +
 
 +
- additional check added for length of segment when writting to database
 +
'''23.12 - 31.01.2011'''
 +
 
 +
Added to eaglememex.properties
 +
 
 +
when running accept all ignore term db look up if true
 +
 
 +
eaglememex.Acceptallnotermlookup=false
 +
 
 +
false - Term search will be done / true - no term search done
 +
 
 +
'''23.10 - 20.01.2011'''
 +
 
 +
databases can uses now use alias names.
 +
 
 +
AN alias is defined in the eaglememex.properties file as
 +
 
 +
aliasname=databasename
 +
 
 +
Example:
 +
 
 +
150000=ed2
 +
 
 +
In this case if a xliff file is loaded where the tmxdatabase to automatically load has the name 150000 then the real database ed2 is loaded.
 +
 
 +
'''23.09 - 20.12.2010'''
 +
 
 +
Directly saving the open tmx file to a choosen TMX Database (Bilingual TMX Editor)
 +
 
 +
Directly saving a selected entry to a choosen TMX Database (Bilingual TMX Editor)
 +
 
 +
Directly saving the open tmx file to a choosen TMX Database (Multilingual TMX Editor)
 +
 
 +
'''23.07 - 06.12.2010'''
 +
 
 +
- added check for getdeepchild if not exists
 +
 
 +
'''23.06 - 05.12.2010'''
 +
 
 +
- Full text Support with MS SQL Server
 +
- Spellchekcer corrections
 +
 
 +
'''23.05 - 03.09.2010'''
 +
 
 +
- corrected a bug in correct tag funktion in tags menu (a ";" was added after the corrected tags); now works correctly
 +
 
 +
'''23.04 - 01.09.2010'''
 +
 
 +
plicsmenu - Xml2Xliff - auskommentiert -
 +
if (1 == 2) // wk 01.08.2010
 +
{
 +
translatelanguage = EMXProperties
 +
.getInstance()
 +
.getEMXProperty(
 +
"eaglememex.translate.plicsmenue.default");
 +
 
 +
'''23.03 - 31.08.2010'''
 +
 
 +
- added "Correct Tags in Target Segments" in Task menu: This function allows to correct "ph tags" which have - for what ever reason be incorrectly written to the target.
 +
common error &lt;ph id="0"&gt;&lt;stichwort&gt;&lt;/ph&gt; -> correct is <ph id="0">&lt;stichwort&gt;</ph>
 +
Pattern is:
 +
String replacePattern = Pattern.quote("&lt;ph") + "(.*?" + Pattern.quote("id=\"") + ".*?"
 +
+ Pattern.quote("\"") + ".*?)" + Pattern.quote("&gt;") + "(.*?)"
 +
+ Pattern.quote("&lt;/ph&gt");
 +
 +
Menu Activation pattern for eaglememex.properties
 +
# Menu Item: Correct Tags in Target Segments
 +
correctTagsinTarget=true,true
 +
 
 +
- if an invalid xliff file is opened or dropped an error message is displayed now
 +
 +
'''23.02 - 10.08.2010'''
 +
 
 +
- tmx database now automatically selected based on the prop database attribute - first if the givend name = string equal, next if the the database name can be found within an existing database as part of the database name
 +
 
 +
- corrected detection of type in xml conversion...
 +
 
 +
'''23.01 - 10.08.2010'''
 +
 
 +
eaglememex.properties: xmlentitylist feature
 +
 
 +
# xml Entity-List Section - this specifies the list wehere the entities which can be inserted are read from
 +
 
 +
xmlentitylist=%CURRENTDIRECTORY%/ini/edqm-ent.txt
 +
 
 +
List looks like that:
 +
 
 +
Ar
 +
 
 +
ASSAY
 +
 
 +
CHARACTERS
 +
 
 +
DEFINITION
 +
 
 +
IDENTIFICATION
 +
 
 +
IMPURITIES
 +
 
 +
etc....
 +
 
 +
The eaglememex.properties file supports now variables for the file pathes: %CURRENTDIRECTORY% is replaced by the current directory where the tool (editor etc.) is started from.
 +
 
 +
Example:
 +
 
 +
eaglememex.Araya.dir=%CURRENTDIRECTORY%/
 +
 
 +
It can be used for all path relevant features.
 +
 
 +
Because of this change the path names are not adapted anymore when Araya is installed.
 +
 
 +
'''23.00 - 16.07.2010'''
 +
 
 +
- support Windows Authentication for Ms drivers added; requires user Field when creating kept empty
 +
- skl Environment shown as tool tip wen moving the mouse to the out bounds of the source / target window: only shown when an skl file is available (either intern or extern)
 +
- dropdown menus for (external) entities and format tags of the curretn source window added in the segment line
 +
- Right click:
 +
a) Insertion (copy) of actually selected entiyt or formaat tag added
 +
b) Direct (copy)  insertion of format tags added
 +
c) Deletion of format tag/entity in target window supported
 +
- Options Menu: Added select how many translation should be displayed in the match window
 +
- TM Search: Support returning only the best max matches when searching
 +
- Tasks Menu: Remove all TMX Database matches from a specific tmx database (specified as origin in alt-trans)
 +
 
 +
Alignment BiTMX Editor 1.70 - 16.07.2010
 +
- supports now alignment dialog in Plugins menu too / including drag and drop into source and target file controls
 +
- Alignment project dialogas also supported
 +
 +
Alignment TMX Editor 6.00 - 16.07.2010
 +
- dran and drop support added
 +
if the input files are not TMX files the alignment dialog is opened.
 +
if just one file is supplied the file si set to the source file box, if two the target file box is filled too
 +
in the dialogue box drag and drop can be used to fill the source and target control boxes resp.
 +
- Alignment project dialogas also supported
 +
 +
22.00 / 22.01 - 23.06.2010
 +
 
 +
Corrected type / ctype handling. using type resp. ctype in a dtd could conflict with the type / ctype attribute of xliff/tmx; this has now been corrected.
 +
 
 +
Support no searching for regexp in formatted segment too
 +
 
 +
21.00
 +
 
 +
Addded the option to specify a (UNC) based path for csv files in the tmx database import.
 +
 
 +
Note on Windows 7: If Windows 7 is used as the operating system do not install Araya in the directory c:/Program Files as this likely results in execution problems due to read / write rights.
 +
20.00 a
 +
 
 +
Add for TermDB Delete
 +
a) Recreate Term DB
 +
b) Remove all Entries
 +
20.00
 +
BOM is added now in back conversion of xml file if one of the follwoing encodings is used. Currently no BOM is added for UTF-8 encoding!
 +
bWriteUTF8Encoding is always set to false
 +
        if ((encoding.equals("UTF-8")) && bWriteUTF8Encoding)
 +
        {
 +
            bom = new byte[3];
 +
            bom[0] = (byte) 0xEF;
 +
            bom[1] = (byte) 0xBB;
 +
            bom[2] = (byte) 0xBF;
 +
            return bom;
 +
        }
 +
        else if (encoding.equals("UTF-16BE"))
 +
        {
 +
            bom = new byte[2];
 +
            bom[0] = (byte) 0xFE;
 +
            bom[1] = (byte) 0xFF;
 +
            return bom;
 +
        }
 +
        else if (encoding.equals("UTF-16LE"))
 +
        {
 +
            bom = new byte[2];
 +
            bom[0] = (byte) 0xFF;
 +
            bom[1] = (byte) 0xFE;
 +
            return bom;
 +
        }
 +
        else if (encoding.equals("UTF-32BE"))
 +
        {
 +
            bom = new byte[4];
 +
            bom[0] = (byte) 0x00;
 +
            bom[1] = (byte) 0x00;
 +
            bom[2] = (byte) 0xFE;
 +
            bom[3] = (byte) 0xFF;
 +
            return bom;
 +
        }
 +
        else if (encoding.equals("UTF-32LE"))
 +
        {
 +
            bom = new byte[4];
 +
            bom[0] = (byte) 0xFF;
 +
            bom[1] = (byte) 0xFE;
 +
            bom[2] = (byte) 0x00;
 +
            bom[3] = (byte) 0x00;
 +
            return bom;
 +
        }
 +
18.00
 +
New task reTranslateAll (ALT F2) "(Re)translate And Approve All Translations", "Alles (wieder) Neu übersetzen und Annehmen" in the Task menu added. It is a combination of
 +
        // 1. Zurücknehmen aller Übersetzungen (Umsch+F3)
 +
        // 2. Entferne alle Zielübersetzungen im Dokument (Alt+F10)
 +
        // 3. F2
 +
        // 4. F3 (Alle Übersetzungen annehmen)
 +
       
 +
Files for loading the initional jar files and commands for the exes (located in the Araya directory)
 +
 
 +
BiEdit.exe biextractclasspath
 +
bitmx.exe bitmxclasspath
 +
TMXEdit.exe tmxeditclasspath
 +
XLFEdit.exe xliffeditorclasspath
 +
tmxeditentry.exe tmxeditentryclasspath
 +
 
 +
17.06
 +
 
 +
Added the option
 +
# do final encoding adaptation processing false = no / true = yes - only for xml files!
 +
eaglememex.xml.AdaptEncodingAfterConversion=true
 +
 
 +
This option is checked if eaglememex.xml.DoFinalXMLProcessing is set to false. Difference is that in this case the characters are not converted to entities, they are kept as they are. With this option the character encoding of the <!xml ...> is adapted to the chosen encoding in the back conversion dialogue (applies only to xml files).
 +
 
 +
# do final xml processing false = no / true = yes
 +
eaglememex.xml.DoFinalXMLProcessing=false
 +
 
 +
Removed bug in Notes handling (add tagret now) now copies the target text from the currently selected segment.
 +
 
 +
17.05
 +
 
 +
Modified Anywhere support
 +
 
 +
# Anywhere Section
 +
#
 +
ianywhere.startserver="C:\\Program Files\\SQL Anywhere 11\\Bin32\\dbsrv11" -gk all -x tcpip(port=__PORT_NUMBER__) -n __ANYWHERESERVERNAME__ __DATABASE_NAME__
 +
ianywhere.createdb="C:\\Program Files\\SQL Anywhere 11\\Bin32\\dbinit" -dba "__USER__,__PASSWORD__" "__DATABASE_NAME__"
 +
ianywhere.pingdb="C:\\Program Files\\SQL Anywhere 11\\Bin32\\dbping" -d -c "ENG=__ANYWHERESERVERNAME__;UID=__USER__";PWD=__PASSWORD__"
 +
ianywhere.stopdb="C:\\Program Files\\SQL Anywhere 11\\Bin32\\dbstop" -y __ANYWHERESERVERNAME__
 +
 
 +
This is new. The semicolon sep. strings are needed to identify the result of a ping and stop to an Anywhere database.
 +
ianywhere.pingdb.detecion=erfolgreich;success
 +
ianywhere.stopdb.detecion=erfolgreich;success
 +
 
 +
Araya 17.04:
 +
 
 +
Changes for displaying the menus
 +
 
 +
Araya 17.03:
 +
 
 +
a) Added iAnyWhere support.
 +
 
 +
Requires some lines to be added to the eaglememex.properties file:
 +
 
 +
# Anywhere Section
 +
#
 +
ianywhere.startserver="C:\\Program Files\\SQL Anywhere 11\\Bin32\\dbsrv11" -gk all -x tcpip(port=__PORT_NUMBER__) -n __ANYWHERESERVERNAME__ __DATABASE_NAME__
 +
ianywhere.createdb="C:\\Program Files\\SQL Anywhere 11\\Bin32\\dbinit" -dba "__USER__,__PASSWORD__" "__DATABASE_NAME__"
 +
ianywhere.pingdb="C:\\Program Files\\SQL Anywhere 11\\Bin32\\dbping" -d -c "ENG=__ANYWHERESERVERNAME__;UID=__USER__";PWD=__PASSWORD__"
 +
ianywhere.stopdb="C:\\Program Files\\SQL Anywhere 11\\Bin32\\dbstop" -y __ANYWHERESERVERNAME__
 +
 
 +
The __variable__ parts have to be written as they are! Ev. the path C:\\Program Files\\SQL Anywhere 11\\Bin32\\ needs to be adapted. The jar Driver jconn4.jar (jConnect driver syy base required! Normally contained somewhere in the Java part of the iAnywhere installation.
 +
 
 +
 
 +
b) Error removed after tmx import (connection was closed which required restart of the editor).
 +
 
 +
Araya 17.02:
 +
 
 +
a) Support now for specifications like
 +
xml.tmxdatabase.WEBVVResources.dtd=internalArayaTM
 +
using the Araya Internal TM
 +
 
 +
b) Added now disable for ontrolling the menus displayed in the menu bar, the menu bar and the tool buttons shown.
 +
 
 +
Tool buttons can als be disabled an removed.
 +
 
 +
Example is given in lib/eaglememex.example.config.properties
 +
 
 +
#[Section for controlling the display of the toolbar items in the toolbar to be displayed
 +
# definitions like for the menu items
 +
#
 +
# Main Toolbar:
 +
#
 +
# mainToolbar.Open XLIFF file [open_file]
 +
mainToolbar.open_file=true,true
 +
 
 +
c) Support SQL Anywhere TMX databases added / term databases will follow)
 +
 
 +
Araya 17.00:
 +
 
 +
1) removed a bug in the copy source to target menu (sometime entries containing a ">" in a format tag could not be copied
 +
2) add a line terminator string for bulk insert (supports now reaing of CR/LF contained in tmx files when importing too)
 +
3) Add three new tasks menu entries
 +
# Menu Item: Change Target Translation Status to "Needs Translation" Shift + F7:  changes the attribute state in target to "Needs Translation"
 +
# Menu Item: Change Target Translation Status to "To Validation" Shift + F4:  changes the attribute state in target to "To Validation"
 +
# Menu Item: Change Target Translation Status to "Translated" Shift + F5:  changes the attribute state in target to "Translated"
 +
 
 +
4) TMX Edit Entry and TmxEditSegment
 +
 
 +
The follwoing functions have been added or modified:
 +
 
 +
a) TmxEdit Entry
 +
 
 +
The order of the menu items has been changed.
 +
Search Similar Segments
 +
Clear TMX Language Entry
 +
Add New Segment
 +
 
 +
Copy TMX Segment to Search Window
 +
Copy TMX Segment with format to Search Window (new)
 +
Copy TMX Segment with format to Clipboard (new)
 +
 
 +
The two previous functions copy the segment including the format information (<ph> Tags to the search window or clipboard.
 +
Example:
 +
Die <ph>xxxxx</ph> als xxxxxxm.
 +
 
 +
b) Tmx Edit Segment
 +
Clear TMX Language Entry
 +
Inserted formatted TMX Segment from Clipboard (new) - this allows to copy a formatted segment into the segment text (e.g. copied to the clipboard using "Copy TMX Segment with format to Clipboard"
 +
Copy Format from Segment: (change: The languages which can be used are shown now in a submenu)
 +
 
 +
 
 +
5) It is now possible to control the number of menus displayed in the menu bar and with the menus available in the menu bar to control the menu items displayed there.
 +
This is done in the eaglememex.properties file:
 +
 
 +
5a) Controlling the menus displayed in the menu bar
 +
 
 +
#[Section for controlling the display of the menus in the menu bar to be displayed
 +
# depending on the setting a menu item is displeayed or not
 +
# <menuitem>=<value>,<value>
 +
# where value is either true or false
 +
# if false the menu item is not displayed
 +
# where value is either true or false
 +
# if false the menu  is not displayed
 +
# true,true means that the menu is displayed for an admin user and a normal user
 +
# true,false means that the menu is displayed for an admin user, but not for a normal user
 +
# false,false means that the menu is displayed neither for an admin user nor for a normal user
 +
# false,true means that the menu is displayed not for an admin user but for a normal user
 +
#
 +
# Menu: &File
 +
Menu_File=true,true
 +
# Menu: &Edit
 +
&Edit_55=true,true
 +
 
 +
 
 +
5b) Controlling the menu item displayed in the menus of the menu bar
 +
 
 +
#[Section for controlling the menu items (which are part of menu in the menu bar list) to be displayed]
 +
# depending on the setting a menu item is displayed or not
 +
# <menuitem>=<value>,<value>
 +
# where value is either true or false
 +
# if false the menu item is not displayed
 +
# true,true means that the menu item is displayed for an admin user and a normal user
 +
# true,false means that the menu item is displayed for an admin user, but not for a normal user
 +
# false,false means that the menu item is displayed neither for an admin user nor for a normal user
 +
# false,true means that the menu item is displayed not for an admin user but for a normal user
 +
#
 +
# Menu Item: &Open File Ctrl + O
 +
&Open_tCtrl_+_O_105=true,true
 +
 
 +
The names are given in the eaglememex.properties file. Currently the following entries are supported.
 +
The line with # gives the name given in the menu as an explanationn which menu is meant.
 +
Within <menuitem>=<value>,<value> line the menuitem is an abstract name (not to be changed!).
 +
 
 +
# Menu Item: &Open File Ctrl + O
 +
&Open_tCtrl_+_O_105=true,true
 +
# Menu Item: Close File Ctrl + F4
 +
Close_File=true,true
 +
# Menu Item: &Save File Ctrl + S
 +
&Save_tCtrl_+_S_106=true,true
 +
# Menu Item: &Save as... Alt + F6
 +
&Save_as..._107=true,true
 +
# Menu Item: Create Backup File F6
 +
backupXliffFile=true,true
 +
# Menu Item: Convert File to XLIFF Format Shift + F6
 +
Convert_to_xliff=true,true
 +
# Menu Item: Convert XLIFF File to Original Format Ctrl + F6
 +
Reverse_conversion=true,true
 +
# Menu Item: Convert XLIFF Files in Directory to Original Format ... Shift + Ctrl + F6
 +
Reverse_convert_Directory=true,true
 +
# Menu Item: Document Properties Alt + F7
 +
Document_Properties=true,true
 +
# Menu Item: Document History Alt + F8
 +
docHistory=true,true
 +
# Menu Item: E&xit Alt + X
 +
E&xit_tAlt_+_X_108=true,true
 +
# Menu Item: Undo Ctrl + Z
 +
undo=true,true
 +
# Menu Item: Redo Ctrl + Y
 +
redo=true,true
 +
# Menu Item: Cut Ctrl + X
 +
Cut=true,true
 +
# Menu Item: Copy Ctrl + C
 +
Copy_Clipboard=true,true
 +
# Menu Item: Paste Ctrl + V
 +
Paste_Clipboard=true,true
 +
# Menu Item: Search/Replace Ctrl + F
 +
Search=true,true
 +
# Menu Item: Search in TMX Database Ctrl + M
 +
Search_in_TMX_Database_tM=true,true
 +
# Menu Item: Concordance Search F5
 +
concordanceSearch_tF5=true,true
 +
# Menu Item: Spell Check Ctrl + H
 +
Check_Spelling1=true,true
 +
# Menu Item: Spell Check All Ctrl + J
 +
Check_Spelling2=true,true
 +
# Menu Item: &Copy Source to Target Ctrl + T
 +
Copy_Source_to_Target=true,true
 +
# Menu Item: Insert Tag Ctrl + I
 +
Insert_tag=true,true
 +
# Menu Item: New Translation Project
 +
New_Project=true,true
 +
# Menu Item: Open Translation Project
 +
Open_Project=true,true
 +
# Menu Item: Convert Translation Project Files to XLIFF format
 +
Convert_Files_to_XLIFF=true,true
 +
# Menu Item: Convert Translation Project Files to original format
 +
Reverse_convert_Project=true,true
 +
# Menu Item: Export Project as TMX
 +
Export_Project_As_TMX=true,true
 +
# Menu Item: Project Translation Status Analysis
 +
Repetition_Analysis=true,true
 +
# Menu Item: New Alignment Project
 +
New_Alignment_Project=true,true
 +
# Menu Item: Open Alignment Project
 +
Open_Alignment_Project=true,true
 +
# Menu Item: Align Project
 +
alignProject=true,true
 +
# Menu Item: Next Segment PgDn
 +
Next_segment=true,true
 +
# Menu Item: Previous segment PgUp
 +
Previous_segment=true,true
 +
# Menu Item: First Segment Ctrl + Home
 +
Editor.936=true,true
 +
# Menu Item: Last Segment Ctrl + End
 +
Editor.937=true,true
 +
# Menu Item: &Go to Segment... Ctrl + G
 +
&Jump_to_segment..._tCtrl_+_G_58=true,true
 +
# Menu Item: Next Matching Translation Shift + PgDn
 +
Editor.938=true,true
 +
# Menu Item: Previous Matching Translation Shift + PgUp
 +
Editor.939=true,true
 +
# Menu Item: Next Fuzzy Ctrl + N
 +
Next_fuzzy=true,true
 +
# Menu Item: Previous Fuzzy Ctrl + P
 +
Previous_fuzzy=true,true
 +
# Menu Item: Next To Check Ctrl + 1
 +
Next_To_Check=true,true
 +
# Menu Item: Previous To Check Ctrl + 2
 +
Previous_To_Check=true,true
 +
# Menu Item: Next Note Shift + Ctrl + N
 +
Next_Note=true,true
 +
# Menu Item: Previous Note Shift + Ctrl + P
 +
Previous_Note=true,true
 +
# Menu Item: Next Untranslated Segment Ctrl + U
 +
Next_untranslated=true,true
 +
# Menu Item: Previous Untranslated Segment Shift + Ctrl + U
 +
Editor.940=true,true
 +
# Menu Item: Next Unapproved Segment Ctrl + Q
 +
Next_unapproved=true,true
 +
# Menu Item: Previous Unapproved Segment Shift + Ctrl + Q
 +
Editor.941=true,true
 +
# Menu Item: Next Target not equal to 100% Match Ctrl+3
 +
NextTargetTextUnEqual100MatchS=true,true
 +
# Menu Item: Previous Target not equal to 100% Match Ctrl+4
 +
PreviousTargetTextUnEqual100MatchS=true,true
 +
# Menu Item: &Select Font
 +
&Select_Font_72=true,true
 +
# Menu Item: Set Minimum Match Percentage
 +
Select_autoFuzzy_Level=true,true
 +
# Menu Item: Show Tags Ctrl + K
 +
Show_Tags=true,true
 +
# Menu Item: Show Context View Ctrl + L
 +
Show_Context_View_t=true,true
 +
# Menu Item: Show Translation Notes Shift + Ctrl + S
 +
Show_Translation_Notes=true,true
 +
# Menu Item: Show Translation Check Status Progress
 +
bShowCheckTranslationsMessage=true,true
 +
# Menu Item: Catalogue Manager
 +
Editor.423=true,true
 +
# Menu Item: XML Converter Configuration
 +
Editor.XML_Converter_Configuration=true,true
 +
# Menu Item: Default Viewers
 +
Editor.425=true,true
 +
# Menu Item: Ask before Adding New Translations to TMX Database
 +
Editor.427=true,true
 +
# Menu Item: Ask before Adding Merge Translations to TMX Database
 +
Editor.428=true,true
 +
# Menu Item: Ask before Adding New Source Translations to TMX Database
 +
Editor.429=true,true
 +
# Menu Item: Ask before Adding New Target Translations to TMX Database
 +
Editor.430=true,true
 +
# Menu Item: Run Accept All without TM Lookup
 +
Accept_all_withoutTM_lookup=true,true
 +
# Menu Item: Accept All without synchronizing with currently loaded TMX Database
 +
Accept_all_withoutTMSync_lookup=true,true
 +
# Menu Item: Do not use Phrase Translation (Term Lookup) for Accept All
 +
Accept_all_withoutterm_lookup=true,true
 +
# Menu Item: Run TMX Database Lookup when using Search Arrow Buttons
 +
searcharrowslookup=true,true
 +
# Menu Item: Search TMX DB for Accept All only in case of Empty Translations
 +
Accept_all_SearchEmpty=true,true
 +
# Menu Item: Use Term Extraction with Concordancy
 +
extractOnConcordancyEmpty=true,true
 +
# Menu Item: Segment Paragraphs for Extraction
 +
segmentMultiExtract=true,true
 +
# Menu Item: Read TMX Entries Attributes
 +
readAttributes=true,true
 +
# Menu Item: Do not update window contents while Accept... functions
 +
MenuDoNotUpdateDisplaySegment=true,true
 +
# Menu Item: Do not save Term Entry Segment Matches in TMX Database
 +
DoNotSaveTermEntriesInTMXDBSegment=true,true
 +
# Menu Item: Use Replacement Classes
 +
UseReplacementClasses=true,true
 +
# Menu Item: English
 +
Editor.lang.1=true,true
 +
# Menu Item: German
 +
Editor.lang.2=true,true
 +
# Menu Item: Save Action History
 +
commentHistory=true,true
 +
# Menu Item: Show Segment as tree
 +
showTreeview=true,true
 +
# Menu Item: Special Characters
 +
VirtualKeyboardDialog.title=true,true
 +
# Menu Item: Change Logging Level
 +
changeloglevel=true,true
 +
# Menu Item: Backup Time Interval
 +
backupmenu=true,true
 +
# Menu Item: &Preview Translation Ctrl + F5
 +
&Preview_Translation=true,true
 +
# Menu Item: Preview XSLT based Translation
 +
Preview_XSLT_Translation=true,true
 +
# Menu Item: Add Segment to TMX database Ctrl + W
 +
Editor.452=true,true
 +
# Menu Item: Approve Segment Ctrl + E
 +
Approve_Segment_tCtrl_+_E_59=true,true
 +
# Menu Item: Accept all Translations Shift + F2
 +
Accept_all_translationsShiftF2=true,true
 +
# Menu Item: Accept only 100% Translations Ctrl + F2
 +
Accept_all_100translationsCtrlF2=true,true
 +
# Menu Item: Accept only 100% Translations with Identical Formatting F2
 +
Accept_all_100Formattranslations=true,true
 +
# Menu Item: Approve all Translations F3
 +
Approve_all_translations=true,true
 +
# Menu Item: Disapprove all Translations Shift + F3
 +
Disapprove_all_translations_textShiftF3=true,true
 +
# Menu Item: Import all approved Translations into TMX Database
 +
importAllTranslations=true,true
 +
# Menu Item: Remove TMX DB Translations in Segment Shift + F10
 +
Remove_TranslationsSHIFTF10=true,true
 +
# Menu Item: Remove all TMX DB Translations in Document Crtl + F10
 +
Remove_All_TranslationsCTRLF10=true,true
 +
# Menu Item: Remove all Target Translations in Document Alt + F10
 +
Remove_All_Target_TranslationsALTF10=true,true
 +
# Menu Item: Change Target Translation Status to "Needs Translation" Shift + F7
 +
changeToNeedsTranslation=true,true
 +
# Menu Item: Change Target Translation Status to "To Validation" Shift + F4
 +
changeToNeedsValidation=true,true
 +
# Menu Item: Change Target Translation Status to "Translated" Shift + F5
 +
changeToTranslated=true,true
 +
# Menu Item: Export File as TMX
 +
Export_as_TMX=true,true
 +
# Menu Item: Export Targets as HTML
 +
Export_as_HTML=true,true
 +
# Menu Item: Export Internal Terminology Database
 +
Export_Internal_Term_Database=true,true
 +
# Menu Item: Analyze Tags &Report F9
 +
&Analyze_Tags_Report=true,true
 +
# Menu Item: Remove Note History
 +
removeNoteHistory=true,true
 +
# Menu Item: Remove all Notes
 +
removeAllNotes=true,true
 +
# Menu Item: Remove all User Specific Notes
 +
removeUserNotes=true,true
 +
# Menu Item: Remove all intermediate Notes
 +
removeIntermediateNotes=true,true
 +
# Menu Item: Add Term From Selection Ctrl + A
 +
Add_Term_From_Selection=true,true
 +
# Menu Item: Add Term to database Ctrl + B
 +
Add_Term_To_Database=true,true
 +
# Menu Item: Search Terms Ctrl + D
 +
Search_in_Term_Database=true,true
 +
# Menu Item: Phrase Translation Ctrl + R
 +
Phrase_Translation=true,true
 +
# Menu Item: Use Stemming
 +
Use_Stemming=true,true
 +
# Menu Item: Create TMX Database
 +
Create_TMX_Database=true,true
 +
# Menu Item: Add TMX Database
 +
Add_TMX_Database=true,true
 +
# Menu Item: Remove/Recreate TMX Database
 +
Remove_TMX_Database=true,true
 +
# Menu Item: Import TMX File
 +
Import_TMX_Document=true,true
 +
# Menu Item: Export TMX Database
 +
Export_TMX_Database=true,true
 +
# Menu Item: Export currently loaded TMX Database to CSV File (UTF8) Format
 +
Export_TMX_Database_CVS_Normal=true,true
 +
# Menu Item: Export currently loaded TMX Database to Internal CSV File (UCS) Format
 +
Export_TMX_Database_CVS=true,true
 +
# Menu Item: Export currently loaded TMX Database to Internal CSV File (UTF8) Format
 +
Export_TMX_Database_CVS_UTF8=true,true
 +
# Menu Item: Import CSV File
 +
Import_CSV_Document=true,true
 +
# Menu Item: Select TMX Database
 +
Select_TMX_Database=true,true
 +
# Menu Item: Synchronize currently loaded TMX Database F10
 +
refresh_TMX_Database=true,true
 +
# Menu Item: Load EagleMemex Server Sided Databases
 +
loadServerSidedDatabases=true,true
 +
# Menu Item: Unload EagleMemex Server Sided Databases
 +
unloadServerSidedDatabases=true,true
 +
# Menu Item: Edit TMX Database Entries F7
 +
editTMXDataBASE=true,true
 +
# Menu Item: Serialize TMX Database
 +
serialiseTMXDataBASE=true,true
 +
# Menu Item: Deserialize TMX Database
 +
deserialiseTMXDataBASE=true,true
 +
# Menu Item: (Re)Word index TMX database
 +
reWordIndexDB=true,true
 +
# Menu Item: Create Terminology Database
 +
createTermDatabase=true,true
 +
# Menu Item: Add Terminology Database
 +
addTermDatabase=true,true
 +
# Menu Item: Remove Terminology Database
 +
Remove_Terminology_Database=true,true
 +
# Menu Item: Import Terminology File
 +
Import_Term_Document=true,true
 +
# Menu Item: Export Terminology Database
 +
exportTermdb=true,true
 +
# Menu Item: Select Terminology Database
 +
selectTerm=true,true
 +
# Menu Item: Edit Terminology Database Entries F8
 +
EditTermatabase=true,true
 +
# Menu Item: Database List Location
 +
Configure_Database=true,true
 +
# Menu Item: Word Index Stopwords
 +
indexstopwords=true,true
 +
# Menu Item: Word Index Numbers
 +
indexnumbers=true,true
 +
# Menu Item: Word Index Special Characters
 +
indexspecialchars=true,true
 +
# Menu Item: Index Word Stems
 +
indexstems=true,true
 +
# Menu Item: Translation Status Analysis Ctrl + F9
 +
Translation_Analysis1CtrlF9=true,true
 +
# Menu Item: Send XLIFF File as EMail Shift + F9
 +
Email.titleShiftF9=true,true
 +
# Menu Item: Preview Translation in HTML Browser Alt + F9
 +
preview_file=true,true
 +
# Menu Item: Preview XSLT based Translation Shift + Alt + F9
 +
Preview_XSLT_TranslationShiftAltF9=true,true
 +
# Menu Item: Log in as Different User
 +
Log_as_Different_User=true,true
 +
# Menu Item: Activate Review Mode [klemens] F4
 +
SetReviewMode=true,true
 +
# Menu Item: Restrict to Note User Alt + F4
 +
noteSearchUser=true,true
 +
# Menu Item: Configure Aspell
 +
Configure_aspell=true,true
 +
# Menu Item: Display ARAYA Properties
 +
EMXEditor.0=true,true
 +
# Menu Item: Convert Files between Character Encodings
 +
DocumentEncoder_conversion=true,true
 +
# Menu Item: Check TMX File Languages
 +
CheckTMXLanguages=true,true
 +
# Menu Item: Split TMX File
 +
splitTMXFile=true,true
 +
# Menu Item: Merge TMX Files
 +
mergeTMXFile=true,true
 +
# Menu Item: Count TMX TU File Entries
 +
countTMXFile=true,true
 +
# Menu Item: Check File Encoding
 +
checkEncoding=true,true
 +
# Menu Item: Validate XML File
 +
validateFile=true,true
 +
# Menu Item: Create Test Files
 +
testdata.0=true,true
 +
# Menu Item: Monolingual Terminology Extraction
 +
monotermextract.0=true,true
 +
# Menu Item: Show Log File
 +
ShowLog.0=true,true
 +
# Menu Item: Print Fuzzy Index to Logfile
 +
PrintFuzzy.0=true,true
 +
# Menu Item: Translate XLIFF File using OpenTMS Data Source
 +
openTMSTranslate=true,true
 +
# Menu Item: Reverse Conversion to Original Document Format
 +
openTMSReverseConvert=true,true
 +
# Menu Item: Create OpenTMS Database
 +
createopenTMSDatabase=true,true
 +
# Menu Item: Delete OpenTMS Database
 +
deleteopenTMSDatabase=true,true
 +
# Menu Item: Import OpenTMS Database
 +
importopenTMSDatabase=true,true
 +
# Menu Item: Export OpenTMS Database
 +
exportopenTMSDatabase=true,true
 +
# Menu Item: OpenTMS Website
 +
OpenTMSHomepage=true,true
 +
# Menu Item: User manual F1
 +
User_manual_tF1_100=true,true
 +
# Menu Item: Display Araya Wiki Documentation Ctrl + F1
 +
Wiki_manual_tF1_100=true,true
 +
# Menu Item: Technics and Revsion manual
 +
Update_manual=true,true
 +
# Menu Item: Change History
 +
changesUpdate=true,true
 +
# Menu Item: Araya Homepage
 +
ArayaHomepage=true,true
 +
# Menu Item: &About...
 +
&About...=true,true
 +
 
 +
 
 +
Araya 16.09: Use synchronized feature for update objects
 +
 
 +
Araya 16.08: No question anymor if source exists-> target does not exist (but source to another language exists)
 +
 
 +
Araya 16.07: Correcte Lookup for Search Arrow TMX Search: now only checks/jumps in tmx db if this feature is set; now it only performs a database lookup if the switsch is set.
 +
 
 +
Araya 16.03: Description of TmxObject tables
 +
 
 +
 
 +
 
 +
monoLingualObjectLanguageHashtable(aus MultiLingualObject!!) Hashtable<String, Hashtable<String, MonoLingualObject>> -> (String language, Hashtable<String, MonoLingualObject> mit (segmentfull, MonoLingualObject)
 +
 
 +
tableSegments - Hashtable<String, String> (segment, multiObj.getIdref()); - also segmentForTable (constructSegmentForTable(monoObj.getSegmentfull(), monoObj.getLanguage());) -> auf IdRef des Multiobjects
 +
 
 +
tableIdMonoLingualObject - Hashtable<String, MonoLingualObject> - eindeutige ID -> MonoLingualObject
 +
 
 +
tableIdRefMultiLingualObject - Hashtable<String, MultiLingualObject> (multiObj.getIdref(), multiObj)
 +
 
 +
 
 +
 
 +
languageVector Vector<String> enthält alle geladenen Sprachen
 +
 
 +
Araya 16.03: Search TMX database: Additional check if target really exists after not existing mono ids have been removed.
 +
 
 +
It is essential that the option in eaglememex.properties is set to true for this check:
 +
 
 +
# checks every time an mono object is accessed if the mono (resp. its id) exists in the attached database
 +
eaglememex.database.CheckIfIdExists=true
 +
 
 +
 
 +
Araya 16.02: Update TMX database: Moved checking when searching after Levenshtein check.
 +
 
 +
Araya 16.01: Update TMX database: Improved checking if entry was deleted.
 +
 
 +
Overview of options controlling the access to the database:
 +
 
 +
Method:                checkIfIdExists
 +
Variable:              bCheckIfIdExists
 +
Class:                TmxObject
 +
Description:          method checks if for given monoid like the MonoLingualObject still exists (could have been deleted by another application).
 +
EagleMemex properties: eaglememex.database.CheckIfIdExists=false/true String CheckIfIdExists = EMXProperties.getInstance().getEMXProperty("eaglememex.database.CheckIfIdExists");
 +
User configuration:    --
 +
Method setting it:    TmxObject(...)
 +
Method using it:      public MultiLingualObject removeDeletedMonoLingualObjects(MultiLingualObject multiObj)
 +
                      public Vector SearchSimilarSegment(String searchsegment, String sourcelanguage, String targetlanguage, int percent, int matchMaximum) throws EMXException
 +
 
 +
 
 +
Method:               
 +
Variable:              bNoSyncWithDatabase (setter / getter)
 +
Class:                TmxObject
 +
Description:          method controls if the database is accessed for a read operation
 +
EagleMemex properties: --
 +
User configuration:    --
 +
Method setting it:    TmxObject(...)
 +
Method using it:      public Vector SearchSimilarSegment(String searchsegment, String sourcelanguage, String targetlanguage, int percent, int matchMaximum) throws EMXException (by updateTmxObject(bNoSyncWithDatabase);)
 +
                                  if (bNoSyncWithDatabase == false)
 +
                                      multiObj = this.removeDeletedMonoLingualObjects(multiObj); // 25.11.2009
 +
                                  if (!bNoSyncWithDatabase && bCheckIfIdExists && (this.tmxDatabase != null))
 +
                                  {  int monoid = mono.getId();  boolean bExists = checkIfIdExists(monoid);...
 +
(as param)            public Element translateSegment(Element seg, String srcLang, String tgtLang, float quality, int maxMatches, boolean bAddemptytarget, Document doc, int iSegmentNumber, boolean bNoSyncWithDatabase)
 +
                      this.bNoSyncWithDatabase = bNoSyncWithDatabase;
 +
                      translations = SearchSimilarSegment(searchsegment, srcLang, tgtLang, (int) quality, matchMaximum);
 +
                      this.bNoSyncWithDatabase = false;
 +
                     
 +
 
 +
Method:               
 +
Variable:              bDoNotSyncWithDatabase
 +
Class:                Editor
 +
Description:          method controls if the database is accessed for a read operation
 +
EagleMemex properties: eaglememex.database.AcceptAllNoSynchronize String Acceptallnodblookup = EMXProperties.getInstance().getEMXProperty("eaglememex.database.AcceptAllNoSynchronize");
 +
User configuration:    bAcceptallnodblookup (true / false)
 +
Menu:                  acceptallnodblookupMenu
 +
Method setting it:    TmxObject(...)
 +
Method using it:      public static boolean checkTranslations(Vector translations)
 +
                              seg = internalTM.translateSegment(seg, sourceLanguage, targetLanguage, minFuzzyMatch, -1, true, doc, segnum, bDoNotSyncWithDatabase);
 +
eaglememex.database.AcceptAllNoSynchronize=true
 +
 
 +
Method:               
 +
Variable:              bAcceptalllookup
 +
Class:                Editor
 +
Description:          method controls if the database is accessed for a read operation
 +
EagleMemex properties: eaglememex.database.CheckIfIdExists=false/true String CheckIfIdExists = EMXProperties.getInstance().getEMXProperty("eaglememex.database.CheckIfIdExists");
 +
User configuration:    acceptall (true / false)
 +
Menu:                  acceptalllookupMenu
 +
Method setting it:    TmxObject(...)
 +
Method using it:      private static void acceptAll(int quality, boolean bCheckFormat)
 +
                      public static boolean bShowPreviousTargetTextUnEqual100Match(int iSegment)
 +
 
 +
Method:               
 +
Variable:              bsearcharrowslookup
 +
Class:                Editor
 +
Description:          method controls if the database is accessed for a read operation
 +
EagleMemex properties: eaglememex.database.CheckIfIdExists=false/true String CheckIfIdExists = EMXProperties.getInstance().getEMXProperty("eaglememex.database.CheckIfIdExists");
 +
User configuration:    searcharrowslookup (true / false)
 +
Menu:                  searcharrowslookupMenu
 +
Method setting it:    TmxObject(...)
 +
Method using it:      public static boolean bShowFuzzySegment(int iSegment)
 +
                            if (Editor.bsearcharrowslookup)
 +
                                  Editor.checkTranslations(iSegment);
 +
                      public static boolean bShowCheckSegment(int iSegment)
 +
 
 +
eaglememex.database.AcceptAllNoSynchronize=true
 +
 
 +
'''Araya 16.00'''
 +
 
 +
''Araya Xliff Editor''- correcting display and use default database after close / open database. Now after a xliff file is closed (and the database has changed for the closed xliff file) the editor reinstatiates the old (default) database again. The default data base is only stored when xliff editor finishes.
 +
 
 +
''TMX Database:''
Improved concurrent access to one sql database by several sources. Now the tmx database always checks before an operation if changes have been doen to the database. Esp. the case of delete entries is now handeled correctly.
Improved concurrent access to one sql database by several sources. Now the tmx database always checks before an operation if changes have been doen to the database. Esp. the case of delete entries is now handeled correctly.
Line 14: Line 1,093:
If true "int" is assumed as the basic data type for creation and modification date.
If true "int" is assumed as the basic data type for creation and modification date.
-
XML Converter:
+
''XML Converter:''
Added rewritting the xml file before conversion so that default attributes etc. are written into the xml file.
Added rewritting the xml file before conversion so that default attributes etc. are written into the xml file.
Line 24: Line 1,103:
If "config_BA.xml" is used (detected), the catalogue "catalogue-vega.xml" will be used. The ini dir is automatically added. Real path would be e.g. "c:/Program Files/Araya/ini/catalogue-vega.xml"
If "config_BA.xml" is used (detected), the catalogue "catalogue-vega.xml" will be used. The ini dir is automatically added. Real path would be e.g. "c:/Program Files/Araya/ini/catalogue-vega.xml"
-
Araya 15.34 Araya Xliff Editor
+
'''Araya 15.34 Araya Xliff Editor'''
Improved texts for querying for existing translations
Improved texts for querying for existing translations
-
Araya 15.33 Araya Xliff Editor
+
'''Araya 15.33 Araya Xliff Editor'''
Added checking dialog @ databases if source or target segment exists
Added checking dialog @ databases if source or target segment exists
-
Araya 15.32a Araya Xliff Editor
+
'''Araya 15.32a Araya Xliff Editor'''
Removed yes/no bug with Cancel button for TM Update Question dialog and changed dialog text
Removed yes/no bug with Cancel button for TM Update Question dialog and changed dialog text
Line 38: Line 1,117:
Removed a bug in the xml converter dealing with "single" >
Removed a bug in the xml converter dealing with "single" >
-
Araya 15.32 Araya Xliff Editor
+
'''Araya 15.32 Araya Xliff Editor'''
Added Cancel button for TM Update Question dialog
Added Cancel button for TM Update Question dialog
-
15.31c
+
'''15.31c'''
TagAnalysis: remove id in string when comparing
TagAnalysis: remove id in string when comparing
-
Araya 15.30
+
'''Araya 15.30'''
Error message added for importing tmx and csv file if bulk insert fails
Error message added for importing tmx and csv file if bulk insert fails
Line 57: Line 1,136:
-
Araya 15.29
+
'''Araya 15.29'''
Reading UTF16-x xliff files added
Reading UTF16-x xliff files added
Line 66: Line 1,145:
Term Editor is kept in memory and reused as long as not closed
Term Editor is kept in memory and reused as long as not closed
-
Araya 15.28
+
'''Araya 15.28'''
a) TMX File cozunter for tu/tuv
a) TMX File cozunter for tu/tuv
Line 74: Line 1,153:
editor.autoselectdatabase=false
editor.autoselectdatabase=false
-
Araya 15.26
+
'''Araya 15.26'''
TMX File Spilt und Merge added to Xliff Editor.
TMX File Spilt und Merge added to Xliff Editor.
-
Araya 15.25
+
'''Araya 15.25'''
Removed some static variables in xml/html conversion which may result in problems when converting with xml-rpc server!
Removed some static variables in xml/html conversion which may result in problems when converting with xml-rpc server!
-
Araya 15.23
+
'''Araya 15.23'''
Removed bug in xmlö rpc conversion processing!
Removed bug in xmlö rpc conversion processing!
-
Araya 15.20d
+
'''Araya 15.20d'''
Added Accept_all_withoutterm_lookup=Do not use Term Lookup for Accept All
Added Accept_all_withoutterm_lookup=Do not use Term Lookup for Accept All
If true (set in options menu) no term look up (phrase) translation will be done when running accept all
If true (set in options menu) no term look up (phrase) translation will be done when running accept all
-
Araya 15.05
+
'''Araya 15.05'''
Added OpenTMS support as special plugin
Added OpenTMS support as special plugin
Line 98: Line 1,177:
Term Editor is kept in memory and reused as long as not closed
Term Editor is kept in memory and reused as long as not closed
-
Araya 15.04a
+
'''Araya 15.04a'''
Modified tmx database creation - show database types and associated server / port when loading.
Modified tmx database creation - show database types and associated server / port when loading.
-
Araya 15.04
+
'''Araya 15.04'''
csv Import for TMX database added.
csv Import for TMX database added.
-
Araya 15.03d
+
'''Araya 15.03d'''
a) removed bug in AcceptAll
a) removed bug in AcceptAll
b) removed bug in reming alt-trans elements when searching
b) removed bug in reming alt-trans elements when searching
-
Araya 15.03c
+
'''Araya 15.03c'''
a) Added under Files to convert all the xlf files in a directory back to its original format.
a) Added under Files to convert all the xlf files in a directory back to its original format.
b) Corrected bug in Accept All for server sided databases
b) Corrected bug in Accept All for server sided databases
c) Back conversion now deletes unnecessary intermediate files (for xml back conversion: *.copy and *.skl if generated from the internal skl file, for general back conversion *.temp)
c) Back conversion now deletes unnecessary intermediate files (for xml back conversion: *.copy and *.skl if generated from the internal skl file, for general back conversion *.temp)
-
Araya 15.03a/b
+
'''Araya 15.03a/b'''
Added "Load EagleMemexServerSided databases" in database menu; allow to load the server database from the XLIFF editor 8requires running EagleMemex XML-RPC server
Added "Load EagleMemexServerSided databases" in database menu; allow to load the server database from the XLIFF editor 8requires running EagleMemex XML-RPC server
-
Araya 15.00 - 15.03
+
'''Araya 15.00 - 15.03'''
a) the property CheckIfIdExists checks every time an mono object is accessed if the mono (resp. its id) exists in the attached database. Setting to true speeds up search.
a) the property CheckIfIdExists checks every time an mono object is accessed if the mono (resp. its id) exists in the attached database. Setting to true speeds up search.
eaglememex.database.CheckIfIdExists=false
eaglememex.database.CheckIfIdExists=false
Line 127: Line 1,206:
Problem starting the EagleMemex Service: If there is a problem that the EagleMemex service does not start, one reason maybe that the dll "msvcr71.dll" cannot be found (seems to be a Java packaing problem). This dll is normally located in the Java installation directory Java/bin. To remove the problem copy the msvcr71.dll from the bin directory into the directory "c:/Windows/System32".
Problem starting the EagleMemex Service: If there is a problem that the EagleMemex service does not start, one reason maybe that the dll "msvcr71.dll" cannot be found (seems to be a Java packaing problem). This dll is normally located in the Java installation directory Java/bin. To remove the problem copy the msvcr71.dll from the bin directory into the directory "c:/Windows/System32".
-
Araya 14.18-20 - 12.11.2008
+
'''Araya 14.18-20 - 12.11.2008'''
a) Several Shortcuts added
a) Several Shortcuts added
b) Concordanc Search Added
b) Concordanc Search Added
Line 133: Line 1,212:
d) Search in Concordamnce Window
d) Search in Concordamnce Window
-
Araya 14.18 - 31.10.2008
+
'''Araya 14.18 - 31.10.2008'''
a) Backup functionality added default = 60 sec: this feature automatically creates a backup of the current changes using loaded filename + ".bak.xlf"
a) Backup functionality added default = 60 sec: this feature automatically creates a backup of the current changes using loaded filename + ".bak.xlf"
The time intervall can be set in the eaglememex.properties file; default = 60; no backup = -1
The time intervall can be set in the eaglememex.properties file; default = 60; no backup = -1
Line 140: Line 1,219:
-
Araya 14.17 - 22.10.2008
+
'''Araya 14.17 - 22.10.2008'''
a) Adaptation to XLIFF standard
a) Adaptation to XLIFF standard
b) Term Editor - show loading term entries
b) Term Editor - show loading term entries
Line 148: Line 1,227:
-
Araya 14.16 - 19.10.2008
+
'''Araya 14.16 - 19.10.2008'''
a) Support of XML RPC server sider TMX databases
a) Support of XML RPC server sider TMX databases
Line 192: Line 1,271:
-
Araya 14.15 - 13.10.2008
+
'''Araya 14.15 - 13.10.2008'''
a) Improved context view - displays now all segments in a table; by clicking on a segment in the context view the corresponding segment in the main source and target window is shown. One can scroll through the whole document now. No editing is currectly possible in this table, but intended in the future.
a) Improved context view - displays now all segments in a table; by clicking on a segment in the context view the corresponding segment in the main source and target window is shown. One can scroll through the whole document now. No editing is currectly possible in this table, but intended in the future.
Line 199: Line 1,278:
-
Araya 14.14 - 07.10.2008
+
'''Araya 14.14 - 07.10.2008'''
a) Adding progress dialog support in TMX file langiage recoder / added preserve whitespace
a) Adding progress dialog support in TMX file langiage recoder / added preserve whitespace
Line 207: Line 1,286:
-
Araya 14.13 - 29.09.2008
+
'''Araya 14.13 - 29.09.2008'''
a) Added csv export for terminology databases, output isUTF-8 encoded
a) Added csv export for terminology databases, output isUTF-8 encoded
Line 213: Line 1,292:
-
Araya 14.09/10 - 13/14.09.2008
+
'''Araya 14.09/10 - 13/14.09.2008'''
a) input para,eter "-p <property file> - allows supply of eagle,memex.properties file - full path name required
a) input para,eter "-p <property file> - allows supply of eagle,memex.properties file - full path name required
Line 220: Line 1,299:
d) doc WinWord - fileforma conversion support - converts doc to docx Format and than converts; requires office converter (FileFormatConverters.exe from Microsoft - http://www.microsoft.com/downloads/details.aspx?FamilyId=941B3470-3AE9-4AEE-8F43-C6BB74CD1466&displaylang=de) installed.
d) doc WinWord - fileforma conversion support - converts doc to docx Format and than converts; requires office converter (FileFormatConverters.exe from Microsoft - http://www.microsoft.com/downloads/details.aspx?FamilyId=941B3470-3AE9-4AEE-8F43-C6BB74CD1466&displaylang=de) installed.
e) eaglememex.<company>.properties suppored - the eaglememe.poperties file depends now on the license key used
e) eaglememex.<company>.properties suppored - the eaglememe.poperties file depends now on the license key used
-
f) removed bug in string segmenting with regard to abbreviations; added support of "e. g." like (blanks in between) abbreviations too.
+
f) removed bug in string segmenting with regard to abbreviations; added support of "e. g." like (blanks in between) abbreviations too
-
Araya 14.03/04/05 - 07.08.2008
+
'''Araya 14.03/04/05 - 07.08.2008'''
a) Terminology export: Error in exporting empty entries resolved
a) Terminology export: Error in exporting empty entries resolved
Line 234: Line 1,313:
g) Added options: Import All approved Translations: This allows to import translations even if they are marked approved. Usual double detection applies. Ths is esp. helpfull if one wants to update a TMX database with the translations approved) sent by a translator and the translations have been done on another machine.
g) Added options: Import All approved Translations: This allows to import translations even if they are marked approved. Usual double detection applies. Ths is esp. helpfull if one wants to update a TMX database with the translations approved) sent by a translator and the translations have been done on another machine.
h) Replacement classes: Now both "." and "," can be used for numbers. Replacements of "," or "." are corrected automatically depending on the source and target tmx combination.
h) Replacement classes: Now both "." and "," can be used for numbers. Replacements of "," or "." are corrected automatically depending on the source and target tmx combination.
-
i) eaglememex.properties file now can contain license name - eaglememex.heartsome.properties
+
i)eaglememex.properties file now can contain license name - eaglememex.heartsome.properties
j) xslt support now in addition to standard html output; allows display of translated text with xsl conversion
j) xslt support now in addition to standard html output; allows display of translated text with xsl conversion
k) Removed bug in replacement classes.
k) Removed bug in replacement classes.
l) Replacement classes detect now 2.3.4 and similar too and makes corect replacement (numbering schemes)
l) Replacement classes detect now 2.3.4 and similar too and makes corect replacement (numbering schemes)
-
Araya 14.02 / XLIFF Editor 14.00 - 17.05.2008
+
'''Araya 14.02 / XLIFF Editor 14.00 - 17.05.2008'''
a) solved a problem with reg exp chars appearing format information when using phrase translation
a) solved a problem with reg exp chars appearing format information when using phrase translation
b) Optimised loading of tmx database when needs changed because of xliff file
b) Optimised loading of tmx database when needs changed because of xliff file
-
Araya 14.00 / XLIFF Editor 14.00 - 17.05.2008
+
'''Araya 14.00 / XLIFF Editor 14.00 - 17.05.2008'''
XML Conversion: Minor change in handling end tags of entries which contains attributes which are displayed as segments. In this case the (end) tag now is written to the skl file is possible (and tag itself is a segment end).
XML Conversion: Minor change in handling end tags of entries which contains attributes which are displayed as segments. In this case the (end) tag now is written to the skl file is possible (and tag itself is a segment end).
-
Araya 12.56 / XLIFF Editor 12.57 - 27.03.2008
+
'''Araya 12.56 / XLIFF Editor 12.57 - 27.03.2008'''
Status Analysis - improvement supporting more files to be analysed in projects
Status Analysis - improvement supporting more files to be analysed in projects
Line 256: Line 1,335:
-
Araya 12.56 / XLIFF Editor 12.56 - 17.03.2008 - 20.03.2008
+
'''Araya 12.56 / XLIFF Editor 12.56 - 17.03.2008 - 20.03.2008'''
# repetition cost analysis
# repetition cost analysis

Current revision as of 11:52, 20 December 2012

Retrieved from "https://heartsome.de/mediawiki/index.php5?title=Changes"
Personal tools