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
 
Line 1: Line 1:
 +
'''27.7e - 20.12.2012'''
 +
 +
# Improved display for askAddTranslation; texts in red and bold and bigger
 +
 +
'''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'''
'''27.4 - 06.12.2012'''
Line 28: Line 54:
- usePartiallyTranslatedTargetsForRepetitions=true
- usePartiallyTranslatedTargetsForRepetitions=true
-
26.7 - 07.11.2012
+
'''26.7 - 07.11.2012'''
usePartiallyTranslatedRepetions - default is now true
usePartiallyTranslatedRepetions - default is now true
-
26.7 - 07.11.2012
+
'''26.7 - 07.11.2012'''
corrected handling:
corrected handling:
 +
Testserver: <ph ctype="bold" id="0">&lt;geraetetyp /&gt;</ph>
Testserver: <ph ctype="bold" id="0">&lt;geraetetyp /&gt;</ph>
 +
Prodserver: <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.
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
+
'''26.6 - 17.09.2012'''
- minor corrections
- minor corrections
Line 56: Line 85:
The configuration files use the following structure:
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
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
-Xms128M
 +
-Xmx1550M
-Xmx1550M
 +
-XX:-UseGCOverheadLimit
-XX:-UseGCOverheadLimit
 +
javaw
javaw
 +
-Djava.library.path=.\\lib\\Win32\\4233
-Djava.library.path=.\\lib\\Win32\\4233
-
==============================================
+
 
The first line with the jar libraries should not be changed.
The first line with the jar libraries should not be changed.
 +
-Xms128M
-Xms128M
 +
-Xmx1550M
-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
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 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:
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
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
-Xms128M
 +
-Xmx4000M
-Xmx4000M
 +
-XX:-UseGCOverheadLimit
-XX:-UseGCOverheadLimit
 +
c:\Program Files\Java\jre6\bin\javaw
c:\Program Files\Java\jre6\bin\javaw
 +
-Djava.library.path=.\lib\Win64\4233
-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"
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.
Please also note that in this example the memory is extended to 4GB using  -Xmx4000M.
-
26.3 - 19.06.2012
+
'''26.3 - 19.06.2012'''
- non breakable space show in add tmx entry dialog
- non breakable space show in add tmx entry dialog
 +
- removed bug when merging entries (entries not added)
- removed bug when merging entries (entries not added)
-
26.2 - 18.06.2012
+
'''26.2 - 18.06.2012'''
- removed bug wenn similarity searching with TMXEditEntry
- removed bug wenn similarity searching with TMXEditEntry
 +
- added replaceall translation in query dialog
- added replaceall translation in query dialog
 +
- internal matches not duplicated any more
- internal matches not duplicated any more
-
26.1 - 25.05.2012
+
'''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!
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
+
'''26.0 - 23.05.2012'''
Approve Log modified
Approve Log modified
TranslationStatus display - cirrected display of translated segments (now they are also counted even if approved!)
TranslationStatus display - cirrected display of translated segments (now they are also counted even if approved!)
-
25.9 - 11.05.2012
+
'''25.9 - 11.05.2012'''
Removed a problem aith approved = yes and translate = no
Removed a problem aith approved = yes and translate = no
-
25.8
+
'''25.8'''
Removed a problem in phrase translation with -, [, ] characters
Removed a problem in phrase translation with -, [, ] characters
-
25.7
+
'''25.7'''
Removed problem when searchin with cocordancy and languages.
Removed problem when searchin with cocordancy and languages.
-
25.6
+
'''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).
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  
+
'''25.4 '''
-
a) Removed Right Click Disapprove / Approve bug
+
# Removed Right Click Disapprove / Approve bug
-
b) Change Title According to Review Status
+
# Change Title According to Review Status
-
c) Added Import all approved translations and delete existin translations
+
# Added Import all approved translations and delete existin translations
-
25.3 (a) - 12.12.2011
+
'''25.3 (a) - 12.12.2011'''
Corrected time and date saving in export and import
Corrected time and date saving in export and import
-
25.3 - 08.12.2011
+
'''25.3 - 08.12.2011'''
remove bug in word counint (tags not counted anymore).
remove bug in word counint (tags not counted anymore).
Line 137: Line 183:
HTML Preview now adds ".context" to the file name to differentiate it from the status analysis html file
HTML Preview now adds ".context" to the file name to differentiate it from the status analysis html file
-
25.2 - 17.11.2011
+
'''25.2 - 17.11.2011'''
Removed a problem when using PT traslate; added regex char quoting for -, []
Removed a problem when using PT traslate; added regex char quoting for -, []
-
25.0 - 14.10.2011
+
'''25.0 - 14.10.2011'''
Changed type of times functions from int to long
Changed type of times functions from int to long
 +
Removes probelm when determining the lats change done to database
Removes probelm when determining the lats change done to database
-
24.9a - 05.10.2011
+
'''24.9a - 05.10.2011'''
added export for term extraction
added export for term extraction
 +
REM 1 term extraction csv file
REM 1 term extraction csv file
 +
REM 2 format (TBX)
REM 2 format (TBX)
 +
REM 3 export approved only (true / false)
REM 3 export approved only (true / false)
 +
REM 4 export > score value
REM 4 export > score value
 +
SET JARS=lib\arayaserver.jar;lib\Win32\swt.jar;lib\external.jar
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
call java -Xmx1024m -cp .;%JARS% com.araya.BiExtractor.Exporter %1 %2 %3 %4
-
24.9 - 22.09.2011
+
 
 +
'''24.9 - 22.09.2011'''
Procect Conversion: Corrected Max match usage.
Procect Conversion: Corrected Max match usage.
-
24.8 - 14.09.2011
+
'''24.8 - 14.09.2011'''
Removing intermediate xlf file produced during xslt transformation
Removing intermediate xlf file produced during xslt transformation
-
24.7 - 31.8.2011
+
'''24.7 - 31.8.2011'''
Direct Search - bug removed for update questions
Direct Search - bug removed for update questions
LogFile read and displayed as UTF-8 now
LogFile read and displayed as UTF-8 now
-
24.6 - 09.8.2011
+
'''24.6 - 09.8.2011'''
improved full text search in SQL Server - adaptave ranking depening on blanks in segment: if no rank = 0 used
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
Ranking can be set now in config file
 +
<directFuzzyKeyRank>50</directFuzzyKeyRank>
<directFuzzyKeyRank>50</directFuzzyKeyRank>
-
24.4 - 12.07.2011
+
'''24.4 - 12.07.2011'''
- Support 32bit and 64bit Java
- Support 32bit and 64bit Java
Line 178: Line 233:
64bit: exes ending with 64.exe; requires 64-bit Java found in c:\Program Files\Java\jre6\bin\javaw
64bit: exes ending with 64.exe; requires 64-bit Java found in c:\Program Files\Java\jre6\bin\javaw
-
biedit64.exe
+
# biedit64.exe
-
bitmx64.exe  
+
# bitmx64.exe  
-
tmxedit64.exe
+
# tmxedit64.exe
-
tmxeditentry64.exe
+
# tmxeditentry64.exe
-
XLFEdit64.exe
+
# XLFEdit64.exe
   
   
If not in c:\Program Files\Java\jre6\bin\javaw changes required in the files
If not in c:\Program Files\Java\jre6\bin\javaw changes required in the files
-
tmxeditentryclasspath64
+
 
-
xliffeditorclasspath64
+
# tmxeditentryclasspath64
-
datasourceeditorpath64
+
# xliffeditorclasspath64
-
bitmxclasspath64
+
# datasourceeditorpath64
-
biextractclasspath64
+
# bitmxclasspath64
 +
# biextractclasspath64
java path can now be configured in the *classpath files
java path can now be configured in the *classpath files
Line 195: Line 251:
Advantage: More memory supported (up to the limit of installed memory)
Advantage: More memory supported (up to the limit of installed memory)
-
- Error correct in tmxeditentry (editing crash removed)
+
# Error correct in tmxeditentry (editing crash removed)
-
 
+
# Improvements and new format in term extraction
-
- Improvements and new format in term extraction
+
# Databases: db-MsSQL2008FT.xml
-
 
+
-
- Databases: db-MsSQL2008FT.xml
+
Loading the whole tmx database in main meory can be now controlled thrue menu item in Database menu
Loading the whole tmx database in main meory can be now controlled thrue menu item in Database menu
Line 205: Line 259:
-
24.3 - 30.03.2011
+
'''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
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
+
'''24.2 - 24.03.2011'''
- removed some bugs and update problems; add on creating translation packages in Menu "File"
- removed some bugs and update problems; add on creating translation packages in Menu "File"
Line 215: Line 269:
-
23.12 - 16.02.2011
+
'''23.12 - 16.02.2011'''
- additional check added for length of segment when writting to database
- additional check added for length of segment when writting to database
-
23.12 - 31.01.2011
+
'''23.12 - 31.01.2011'''
Added to eaglememex.properties
Added to eaglememex.properties
-
# when running accept all ignore term db look up if true
+
 
 +
when running accept all ignore term db look up if true
 +
 
eaglememex.Acceptallnotermlookup=false
eaglememex.Acceptallnotermlookup=false
 +
false - Term search will be done / true - no term search done
false - Term search will be done / true - no term search done
-
23.10 - 20.01.2011
+
'''23.10 - 20.01.2011'''
databases can uses now use alias names.
databases can uses now use alias names.
AN alias is defined in the eaglememex.properties file as  
AN alias is defined in the eaglememex.properties file as  
 +
aliasname=databasename
aliasname=databasename
 +
Example:
Example:
 +
150000=ed2
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.
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
+
'''23.09 - 20.12.2010'''
Directly saving the open tmx file to a choosen TMX Database (Bilingual TMX Editor)
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 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)
Directly saving the open tmx file to a choosen TMX Database (Multilingual TMX Editor)
-
23.07 - 06.12.2010
+
'''23.07 - 06.12.2010'''
- added check for getdeepchild if not exists
- added check for getdeepchild if not exists
-
23.06 - 05.12.2010
+
'''23.06 - 05.12.2010'''
- Full text Support with MS SQL Server
- Full text Support with MS SQL Server
- Spellchekcer corrections
- Spellchekcer corrections
-
23.05 - 03.09.2010
+
'''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
- 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
+
'''23.04 - 01.09.2010'''
plicsmenu - Xml2Xliff - auskommentiert -  
plicsmenu - Xml2Xliff - auskommentiert -  
Line 264: Line 327:
"eaglememex.translate.plicsmenue.default");
"eaglememex.translate.plicsmenue.default");
-
23.03 - 31.08.2010
+
'''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.
- 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.
Line 279: Line 342:
- if an invalid xliff file is opened or dropped an error message is displayed now
- if an invalid xliff file is opened or dropped an error message is displayed now
-
23.02 - 10.08.2010
+
'''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
- 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
Line 285: Line 348:
- corrected detection of type in xml conversion...
- corrected detection of type in xml conversion...
-
23.01 - 10.08.2010
+
'''23.01 - 10.08.2010'''
eaglememex.properties: xmlentitylist feature
eaglememex.properties: xmlentitylist feature
# xml Entity-List Section - this specifies the list wehere the entities which can be inserted are read from
# xml Entity-List Section - this specifies the list wehere the entities which can be inserted are read from
 +
xmlentitylist=%CURRENTDIRECTORY%/ini/edqm-ent.txt
xmlentitylist=%CURRENTDIRECTORY%/ini/edqm-ent.txt
Line 295: Line 359:
Ar
Ar
 +
ASSAY
ASSAY
 +
CHARACTERS
CHARACTERS
 +
DEFINITION
DEFINITION
 +
IDENTIFICATION
IDENTIFICATION
 +
IMPURITIES
IMPURITIES
Line 306: Line 375:
Example:
Example:
 +
eaglememex.Araya.dir=%CURRENTDIRECTORY%/
eaglememex.Araya.dir=%CURRENTDIRECTORY%/
Line 312: Line 382:
Because of this change the path names are not adapted anymore when Araya is installed.
Because of this change the path names are not adapted anymore when Araya is installed.
-
23.00 - 16.07.2010
+
'''23.00 - 16.07.2010'''
- support Windows Authentication for Ms drivers added; requires user Field when creating kept empty
- support Windows Authentication for Ms drivers added; requires user Field when creating kept empty

Current revision as of 11:52, 20 December 2012

Personal tools