Sisulizer 2008.282 Enterprise Edition Rus» New 2008 build 282 (May 11, 2009): «
New features:
• Sisulizer.exe is now fully Unicode enabled application.
• Support for PostgreSQL database added. Sisulizer can import translations from PostgreSQL, localize PostgreSQL databases, and can store translation memory into PostgreSQL database.
• Database samples added for Interbase, Firebird, MySQL, Oracle, PostgreSQL and SQL Server in addition of Access and Paradox that were in the previous versions.
• "Invalid amount of vertical bars"-validation. Validates that there are the same amount of '|'-characters in translations than in originals.
Improved features:
• Server database access (MySQL, SQL Server, Interbase, Firebird and Oracle) improved.
• Sisulizer now saves valid translations to the translations memory even if equals to the original value. You can turn this feature off from Translation Engines dialog.
• Translate duplicates process uses the alternative language (if set) as reference language.
• Slow editing in a translation cell has been improved.
• If you add or remove a new language the editing translation will be committed.
• Can't add the same source into the project twice.
• List views in bottom panes can now display text in multiple lines if it is too wide to fin in a single line.
• parameter added to the output file pattern.
Bug fixes:
• Running Java samples (JAR files included into Sisulizer project) did not work.
• VCL: Some empty translations "" in TStringList objects caused an excaption during rescanning.
• Excluded originals dialog.
• Sisulizer did not use proxy settings with Google Translate. This cause Google Translate not to work when Sisulizer was used behind a firewall.
• WPF: Sisulizer could not compile XAML files that used local user controls. This caused that Sisulizer could not also create localized satellite assembly files for those projects.
• Databases: If you pressed Connect in the database source dialog your items settings were lost.
• WPF: If using binary localization with pages using Resources block caused invalid BAML data written to localized satellite assemblies. This caused parse error when running the application.
• Silverlight: Sisulizer did not scan XAML resources as user interface data but as XML data.
• You can add space characters and use Ctrl+C, Ctrl+X and Ctrl+V combinations (as copy, cut, paste) also with armenian language.
• HTML Help: Sometimes Sisulizer added unnecessary files to localuzed CHM file and this caused that the fiel did not work.
44.57 Mb
42,0 Mb