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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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 'CET/1.0/no 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  
+
'''Araya 16.00'''
-
Araya Xliff Editor
+
''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.
-
- 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:
+
''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 13:
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 23:
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 37:
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 56:
-
Araya 15.29
+
'''Araya 15.29'''
Reading UTF16-x xliff files added
Reading UTF16-x xliff files added
Line 66: Line 65:
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 73:
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 97:
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 126:
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 132:
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 139:
-
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 147:
-
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 191:
-
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 198:
-
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 206:
-
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 212:
-
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 219:
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 233:
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 255:
-
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

Revision as of 08:06, 27 November 2009

Personal tools