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
(Created page with 'Araya 15.28 a) TMX File cozunter for tu/tuv b) empty xlf now read from ini diectory c) Selection database names now configurable in properties file: # editor.autoselectdatabase …') |
(Changes in the last versions) |
||
| Line 1: | Line 1: | ||
| + | Araya 16.00 | ||
| + | |||
| + | Araya Xliff Editor | ||
| + | - correcting display and use default database after close / open database. Now after a xliff file is closed (and the database has changed for the closed xliff file) the editor reinstatiates the old (default) database again. The default data base is only stored when xliff editor finishes. | ||
| + | |||
| + | TMX Database: | ||
| + | |||
| + | Improved concurrent access to one sql database by several sources. Now the tmx database always checks before an operation if changes have been doen to the database. Esp. the case of delete entries is now handeled correctly. | ||
| + | |||
| + | Query if entry exists dialog: Now the the tm match window shows the current contents of the tm match correctly (now only the old matches) | ||
| + | |||
| + | A check is now made which type the dates in the database really use. "int" is much more faster when loading as conversion from "String" to "int" not required any more. | ||
| + | <creationmodificationdatetype>true</creationmodificationdatetype> in the database config file | ||
| + | If true "int" is assumed as the basic data type for creation and modification date. | ||
| + | |||
| + | XML Converter: | ||
| + | |||
| + | Added rewritting the xml file before conversion so that default attributes etc. are written into the xml file. | ||
| + | eaglememex.xml.RewriteXmlFile=yes (rewrittes the file), default is no. | ||
| + | |||
| + | Added option to determine the catalogue for the xml document based on dtd name. This is esp. necessary in case of dtds where entieties etc. could be overwriten by the standard catalogue file inidir/catalogue.xml | ||
| + | Example: | ||
| + | eaglememex.xml.catalogue.config_BA.xml=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 | ||
| + | |||
| + | Improved texts for querying for existing translations | ||
| + | |||
| + | Araya 15.33 Araya Xliff Editor | ||
| + | |||
| + | Added checking dialog @ databases if source or target segment exists | ||
| + | |||
| + | Araya 15.32a Araya Xliff Editor | ||
| + | |||
| + | Removed yes/no bug with Cancel button for TM Update Question dialog and changed dialog text | ||
| + | |||
| + | Removed a bug in the xml converter dealing with "single" > | ||
| + | |||
| + | Araya 15.32 Araya Xliff Editor | ||
| + | |||
| + | Added Cancel button for TM Update Question dialog | ||
| + | |||
| + | 15.31c | ||
| + | |||
| + | TagAnalysis: remove id in string when comparing | ||
| + | |||
| + | Araya 15.30 | ||
| + | |||
| + | Error message added for importing tmx and csv file if bulk insert fails | ||
| + | |||
| + | Bulk insert: the csv file is written to the directory sharedfolders.database.path if this property exists; otherwise to the database directory | ||
| + | Example: sharedfolders.database.path=c:/Dokumente und Einstellungen/klemens/Eigene Dateien/ | ||
| + | |||
| + | The directory name can be abstract, e.g. \\SystemX\DiskZ\Sales | ||
| + | It must follow UNC-Namens (Universal Naming Convention). | ||
| + | |||
| + | |||
| + | Araya 15.29 | ||
| + | |||
| + | Reading UTF16-x xliff files added | ||
| + | |||
| + | Added OpenTMS support as special plugin | ||
| + | Support regular expression search in Term Editor | ||
| + | Clicking on Search term Window entry will display the term in the Term editor | ||
| + | Term Editor is kept in memory and reused as long as not closed | ||
| + | |||
Araya 15.28 | Araya 15.28 | ||
