Softpedia >Windows >Programming >Other Programming Files >Sisulizer Standard >  Changelog

Sisulizer Standard Changelog

What's new in Sisulizer Standard 4.0 Build 374

Dec 1, 2018
  • Support for Delphi 10.3 Rio and C++Builder 10.3 Rio added.

New in Sisulizer Standard 4.0 Build 373 (Sep 10, 2018)

  • If project was exchanged the exchange hidden falgs were removed when the project was first saved.
  • WPF: Some binding value caused Sisulizer to write invalid XAML.
  • RC: If any control contained "L" text the generated localized RC file was invalid.

New in Sisulizer Standard 4.0 Build 372 (May 23, 2018)

  • Android: Sisulizer reads the translatable attribute.
  • .NET: When excluding certain properties by using the Excluded properties in the source's properties the properties vere excluded but the localized .resx file contained the orginal properties. Now they are removed.
  • Source that contained a wild card such as *.resx sometimes took very long tome to open if the path pointed to a directory that has huge amount of files (e.g. Windows system directory)
  • XAML compilation did not work on 32-bit Windows and .NET 4.6x or later.

New in Sisulizer Standard 4.0 Build 371 (May 12, 2018)

  • Improved features:
  • Android:
  • Sisulizer reads the translatable attribute.
  • .NET:
  • When excluding certain properties by using the Excluded properties in the source's properties the properties vere excluded but the localized .resx file contained the orginal properties. Now they are removed.
  • Bug fixes:
  • Source that contained a wild card such as *.resx sometimes took very long tome to open if the path pointed to a directory that has huge amount of files (e.g. Windows system directory)
  • XAML compilation did not work on 32-bit Windows and .NET 4.6x or later.

New in Sisulizer Standard 4.0 Build 370 (Jan 5, 2018)

  • New features:
  • Support for .NET 4.7.1 added.
  • Support for Windows Embedded Compact .NET 3.9
  • Improved features:
  • Microsoft Translator. Sisulizer now automatically renews the access token. Previously the token expired after 10 minutes so if you translated a long project the translation failed after 10 minutes.
  • Android: Sisulizer correctly decodes new line (n).
  • Bug fixes:
  • Import. When importing from a file and then deleting the file and imprting again Sisulizer hanged.
  • .NET: Scanning a form containing DevExpress.XtraEditors.Controls.LookUpColumnInfo sometimes caused EXE parsing to fail with "Could not scan the code of ScanError.XtraForm1 item. Form may show incorrectly on visual editor."
  • WPF: SlMake did not export rows that had TXamlRow class.

New in Sisulizer Standard 4.0 Build 369 (Oct 7, 2017)

  • New features:
  • Support for .NET Core and .NET Standard.
  • Improved features:
  • SlMake. When building Sisulizer project having .NET assembly source and Sisulizer's .NET extension were not properly installed Sisulizer always used either .NET 2.0 or 4.0 tool but not any other.
  • CHM: Index files using Keyword parameter instead of Name parameter are now scanned too,
  • Delphi: Sisulizer warn if DRC file does not exist or user tries to change the resource string context method.
  • Bug fixes:
  • Import. If "Import import status" was set to "Set to status" and the import file actually contained status data (e.g. some XLIFF files) the status data of the import file was used instead of the value of "Set to status".
  • Import. Importing from other but .slp or localized files did not always import strings lists.
  • LaTranslator.pas caused an warning on DX 10.2: "W1000 Symbol 'GetUnicodeStrProp' is deprecated: 'use GetStrProp'"
  • Text source: use byte order mark did not have any affect if the original file did not have a BOM.
  • .NET: Sisulizer did not locate the right MsBuild.exe for projects made in Visual Studio 2017.
  • Text source: If you added defect id/status/comment field an exception occured.
  • ReportBuilder: An exception occured when opening a project containing ReportBuider source.

New in Sisulizer Standard 4.0 Build 368 (Apr 29, 2017)

  • New features:
  • Support for Delphi 10.2 Tokyo and C++Builder 10.2 Tokyo added.
  • Support for .NET 4.7 added.
  • Support for Visual Studio's Shared projects added.
  • Improved features:
  • Support for the new Microsoft Translator added.
  • SlMake: setstatus option added to import task.
  • Bug fixes:
  • Java: Unicode escape encoding output was turned off in builds 364-366. Now it is on.

New in Sisulizer Standard 4.0 Build 366 (Mar 1, 2017)

  • NEW FEATURES:
  • Support for Visual Studio 2017 added.
  • IMPROVED FEATURES:
  • Sisulizer no longer imports exchange hidden rows.
  • BUG FIXES:
  • WPF: Binding was not parsed correctly it there was a sub item without parameters.
  • .mpr import removed leading and trailing spaces from translations.
  • Source code localization scanning was broken in build 365.
  • Now fixed and works in the same way as before 365.

New in Sisulizer Standard 4.0 Build 365 (Dec 23, 2016)

  • Improved features:
  • Windows RC: Sisulizer can now localize AFX_TARG definition.
  • When creating a new project Sisulizer can find existing localized files from multiple localization and not only the from Sisulizer's default output directory.
  • When importing translation from Multilizer project Sisulizer can better import duplicate strings.
  • XML: localize attribute now works with elements that are not selected.
  • You can set multiple rows as HTML in the same time.
  • .NET: Sisulizer can now use both standalone MsBuild (installed by Visual Studio) and MsBuild of .NET framework. Standalone is used if it exists. If not then .NET MsBuild.
  • Support for Burmese added.
  • Bug fixes:
  • Export filter ignored translation marked flag.

New in Sisulizer Standard 4.0 Build 364 (Oct 11, 2016)

  • New features:
  • You can now drag a file from Explorer to Sisulizer to open the file.
  • Improved features:
  • .NET: Sisulizer starts using MsBuild of the tool version instead of .NET framework. This makes sure that same MsBuild is used as with Visual Studio.
  • .NET: When localizing .NET assemblies using the binary localization Sisulizer now read the correct .NET framework from the original assembly.
  • Sisulizer checks if the size of application file to be localized is 0 and gives a property error message instead of exception.
  • You can now enter 3 character ISO language codes into the system language dialog when you add a custom language.
  • Android: Trying to run an Android application on a machine that did not have any Android devices installed caused Sisulizer to crash. Now Sisulizer shows a correct error message.
  • Firebird: Support for UTF-8 encoding added.
  • Database: When creating a new project you can specify the original encoding in the project wizard.
  • XLIFF: Sisulizer now support mrk element and segmented translations.
  • You can now turn off usage of the checked language ids when building localized files.
  • Delphi: When Vietnamese support is turned on Sisulizer writes Unicode property values as Ansi using Vietnamese code page.
  • Bug fixes:
  • .NET: If sorting of string items was turned off they were still sorted if the project was saved without scanning. For example translator never scans and .slp file edited by them contained always sorted strings data.
  • HTML Help: When scanning some .chm file Sisulizer hanged.
  • JavaScript: If a string was immediately followed by a single line comment Sisulizer scanned JavaScript file incorrectly and created invalid output JavaScript file.
  • WPF: If binding expression contained and empty parameter ({}) the binding value in the localized XAML was incorrect.
  • When project was exchanged the exchangehidden flags were cleared after translator saved the project for first time.

New in Sisulizer Standard 4.0 Build 363 (Jul 27, 2016)

  • IMPROVED:
  • .NET: Sisulzier can now handle better projects that contains both WPF and Windows Forms.
  • Delphi: When scanning 64-bit EXE Sisulizer sometimes wrote "Unused inherited forms..." Hint even there was no such case.
  • BUG FIXES:
  • .NET: The default output directory was wrong if .slp was saved in a different directory than .csproj

New in Sisulizer Standard 4.0 Build 362 (Jul 21, 2016)

  • BUG FIXES:
  • Sisulizer did not uses the correct assembly directory when finding required assemblies. This caused XAML compilation to fail when a XAML using a custom control was compiled.
  • Namaspace of some custom .resx resources was not read correctly.

New in Sisulizer Standard 4.0 Build 361 (Jul 1, 2016)

  • NEW:
  • Support for .NET 4.6.2 added.
  • IMPROVED:
  • .NET: File version is now updated in satellites if customized in the project.
  • Importing can now handle multiline strings that use different new line combinations.
  • BUG FIXES:
  • Merging did not work correctly unless the source and target project had the same amount of languages in the same order.
  • .NET 4.6.1: Sisulizer did not use SDK tools from BinNETFX 4.6.1 but BinNETFX 4.6.
  • Project reports incorrectly counted exchange hidden rows.

New in Sisulizer Standard 4.0 Build 360 (Apr 20, 2016)

  • New features:
  • Support for Delphi 10.1 Berlin and C++Builder 10.1 Berlin added.
  • Support for Android values files (.e.g strings.xml) added.
  • File | Merge feature added. Merges another Sisulizer project into the current project.
  • Improved features:
  • Excel and text import: Importing of translation comments implemented.
  • Pseudo translation: Max translation method added. Gets the longest value among the original and the translations.
  • Pseudo translation: Add an unique id feature added.
  • PO: When compiling to MO files the empty translation are skipped. There is an option that you can use to make Sisulizer to include empty translations.
  • PO: Support for msgctxt (context) added.
  • Delphi: Vientamese support added for Ansi applications (pre 2009).
  • Spell checking: Sisulizer can now import OXT files that uses the new format.
  • Defect id, defect status and defect comment fields added to translation.
  • Export: Hidden rows (e.g. Version number) are no longer exported.
  • Translation Memory now works better to use the same character case as the value in the translation memory. Also special characters such as commas are handled better.
  • Sisulizer's editor renders Thai correctly.
  • .NET: Sisulizer reads assembly references also from import files that VS projects file imports.
  • Project Wizard and Import Wizard improved to have a file edit and to accept drops from Windows Explorer.
  • Show file in explorer menu added to source's popup menu in thef project tree to quickly view the original file.
  • .NET: Languages sheet added to .NET resource source dialog.
  • Microsoft Translator and Google Translate: string length check added.
  • Delphi: When creating multilingual Delphi file Sisulizer can now set the language of the original language neutral resource to match the original language.
  • Bug fixes:
  • Translation memory: Sisulizer removed traling and leading brackets even if they were not matching. For example in [...} [ and } were removed.
  • SlMake: Crashed of "Clipped text" validation was checked in the named validation list.
  • .NET: If Version number check box in Version type of Resource sheet was not checked and Sisulizer could not read the version from AssemblyInfo.cs the default version (1.0.0.0) was used.
  • .NET: Building of WPF project that uses .NET 3.5 and ToolsVersion 14.0 failed.
  • PO: Default language was ignored.
  • MySQL: Sisulizer alreay used the default port 3306 even if you specified a custom port.
  • HTML: If segmetation was on and you selected a node in the project tree Sisulizer sometimes intoduced a changed row.
  • Sisulizer did not detect the installed .NET 4.6 framework version correctly on Windows 8.1 or earlier. This caused XAML compiliation to fail if .NET 4.5.* or 4.6 was used.

New in Sisulizer Standard 4.0 Build 359 (Dec 30, 2015)

  • NEW:
  • Support for .NET 4.6.1 added.
  • IMPROVED:
  • Delphi: Support for TRzCheckTree, TRzTreeView and TRzListView added.
  • Sisulizer can now correctly convert a Multilizer 6.x project file.
  • .NET: Visual Basic project without namespace can be localized.
  • HTML Help: Index and content files can now be in UTF-8.
  • XML: Option added to force encoding of predefined characters (, &, " and ').
  • BUG FIXES:
  • Sisulizer setup did not update the sample files if you installed a new version using "Update the existing installation" option.
  • .NET: If a resource files was in a sub folder containing spaces in the folder name (e.g. "My files") the resource name in the satellite assemblies was incorrect and those localized resources were not used.
  • Find dialog's Accept regular expressions did not work.
  • Windows: If the EXE or DLL contained the same icon with several different resolution the order of these were different in the localize files making the file to use different icon when viewed in Explorer.
  • .NET: If .resx project had a default language set to other than original and Items that localized files contain had set to all the output localized fiels contained sometimes wrong translations.
  • SlMake.exe: When using add command and relative path to a source different to SLP files SlMake did not correctly add the source.

New in Sisulizer Standard 4.0 Build 358 (Oct 23, 2015)

  • NEW FEATURES:
  • Support for Delphi 10 Seattle and C++Builder 10 Seattle added.
  • Build automation server setup option added to Sisulizer's setup.
  • Tested with final version of Visual Studio 2015 and .NET 4.6.
  • IMPROVEMENTS:
  • SlMake finds license data even if it is run one different Windows account as was used to install Sisulizer. This is usually the situation for example on build server.
  • Write log and Use smart options added for translate duplicates feature.
  • Source code: support for JavaScript's RegExp modifiers added.
  • Delphi: Support for TGridPanel and TFlowPanel.
  • Windows Forms: ToolTipText properties of DataGridView's column are now scanned.
  • PO: Language attribute in PO-header is updated in the localized PO files.
  • BUG FIXES:
  • Sisulizer did not store the custom text definitions added when importing.
  • .NET. Select language dialog incorrectly included language into the language list if there exissted an empty satellite directory.
  • XML: When adding a multilingual XML into Sisulizer the original language was always set to the first language of XML file.
  • VCL: Loop error in EnumResourceNamesProc fixed.
  • JSON: Building failed if *.json file name was added.

New in Sisulizer Standard 4.0 Build 357 (Jul 2, 2015)

  • Improved features:
  • Source code: Comment tags can now be before the string and not only after the string as in the previous versions.
  • .NET and Silverlight: Digital signature and delay signing options added.
  • Validation: Some false alarms removed from hotkey validation.
  • Windows: When creating resource DLL and Copy all files are unchecked Sisulizer now always include the resource item if the resource type is checked and resource item is not excluded.
  • Bug fixes:
  • Silverlight: If a resource dictionary node was excluded but contained some translations the Strings elements were missing in the localized files.
  • Delphi: The output encoding of defined text was alsways Ansi even the original resource used UTF-8.
  • Importing. If a row was hidden Sisulizer incorrectly imported a value into that.

New in Sisulizer Standard 4.0 Build 356 (Apr 28, 2015)

  • New Features:
  • Support for Windows 10 added.
  • Support for Delphi XE8 and C++Builder XE8 added.
  • Sisulizer can export row and translartions from Sisulizer project to .resx files and import them back.
  • Improved features:
  • Android: Support running application on devices added. Previousely Sisulizer supported only the emulator.
  • Android: Sisulizer now find zipalign.exe from its new location in the SDK directory.
  • .NET: Version property added to .resx options sheet.
  • .NET: Localized resx files no longer contain original comment but a translation comment if existed.
  • .NET: If Version number check box was not checked in Resources sheet Sisulizer read the version number from AssemblyInfo.cs and not from original assembly file. Now Sisulizer reads always from original assembly file and only if not found from AssemblyInfo.cs.
  • Machine translation: Sisulizer no longer translates hidden row when using machine translator.
  • XAML: Run, Span and text elements inside TextBlock can now be scanned either individually (default) or grouped.
  • Pseudo translation is not done for strings that contain XML data.
  • Bug fixes:
  • .NET: DevExpress.XtraEditors.Controls.LookUpColumnInfo parser hanged on some cases.
  • XLIFF: Filterng did not work with projects that contained XLIFF files.
  • XAML: If original binding value did not contain single quote but the translated value contained then localized XAML created by Sisulizer was invalid.
  • Android: Sisulizer sometimes wrote invalid string data into localized .apk file.
  • WPF: Sometimes Sisulizer raised out of index exception when creating localized XAML files.

New in Sisulizer Standard 4.0 Build 355 (Mar 11, 2015)

  • New features:
  • File dialog filter validation added.
  • Improved features:
  • .NET: Now you can turn of the feature that disables those projects of solutions that do not contain any resources to be localized.
  • Project | Import Translations from Localized Files | Import by value, do not change existing translations added. This lets you to import translations from old existing files where context is not necassary same any more because of code and UI changes.
  • Version resource localization improved (it is possible to ignore file names and version numbers).
  • .resx parsing improved.
  • .NET: Improved parsing for DevExpress.XtraEditors.Controls.LookUpColumnInfo implemented.
  • If output directory is specified to a none default and the source has platform files then localized platform files are also written to the output directory.
  • Bug Fixes:
  • Default language did not have any effect with database source.
  • XAML: If TextBlock contained Run element that had a Text attribute and empty element value Sisulizer created invalid localized file.
  • .NET: Sisulizee failed to compile .resx file that containd localized DevExpress SuperTip data.

New in Sisulizer Standard 4.0 Build 354 (Jan 13, 2015)

  • New features:
  • Support for Visual Studio 2015 added.
  • Support for .NET 4.6 added.
  • Improved features:
  • Improved XAML parsing.
  • WPF: DevEx's Label and Caption properties added into the default scan properties.
  • When applying Machine translation status of translation is now set to best guess instead of auto translated.
  • .NET: Sisulizer can read the SatelliteContractVersionAttribute (if any) from the original assembly and matches the satellite assembly version with that version.
  • Sisulizer can now remove machine translations from the project (if they were added using this version or later).
  • Bug fixes:
  • iOS: If .strings file contained an empty string value it broke the scanning of the rest of the .strings file.
  • Windows Forms: DevExpress SuperToolTips data is now scanned correctly.
  • Microsoft changed protocol of Microsoft Translator and that broke Sisulizer's Microsoft Translator feature. This has now been fixed to apply the new protocol.
  • Android: Sisulizer could not read some .apk files but caused an error when reading the file.

New in Sisulizer Standard 4.0 Build 353 (Jan 13, 2015)

  • Improved features:
  • iOS: Sisulizer now finds all existing translations.
  • Bug fixes:
  • Delphi: LaTranslator.pas did not compile with Delphi XE7.

New in Sisulizer Standard 4.0 Build 352 (Jan 13, 2015)

  • New features:
  • Support for Delphi XE7 and C++Builder XE7
  • Improved features:
  • JSON: Sisulizer can now read JSON files where the root object is an array.
  • Java: Localized properties file no longer escape single and double quotes in the values.
  • Bug fixes:
  • If a project contained custom country depend variant (e.g. sv-SE-My) column and country neutral (e.g. sv) column Sisulizer did not use translations of country neutral column if there were no translation in the custom country depend variant column.

New in Sisulizer Standard 4.0 Build 351 (Jan 13, 2015)

  • Improved features:
  • PO: Sisulizer now keeps the original order of the strings.
  • TMX: Sisulizer reads the existing languages from the original TMX file.
  • TMX: Sisulizer can handle language id with underline (_) as separator instead of hyphen (-).
  • Windows RC: Localized files can now be written as Unicode (UTF-16).
  • iOS: Sisulizer can now handle language id with script part such ad zh-Hans and zh-Hant.
  • Bug fixes:
  • Translation memory dialog: The Search function in the Search sheet did not always work if the language did not use Western code page and the search word contained diacritical characters.
  • XLIFF: When using SlMake to exchange projects containing XLIFF all the rows were marked exchange hidden so they did not show visible on the grid.
  • .NET: If the sign key file if the project file (.csproj or .vbproj) contained variable (e.g. $(SharedDir) Sisulizer did not find the key file and could not sign the localized assemblies

New in Sisulizer Standard 4.0 Build 350 (Jan 13, 2015)

  • New features:
  • Support for Delphi XE6 and C++Builder XE6 added.
  • Support for TypeScript added.
  • Support for iOS and OS X strings files added.
  • Support for Visual Studio 2013 Update 2 added.
  • Support for .NET 4.5.2 added.
  • Improved features:
  • SlMake: uilangs option added to exchange task.
  • Server translation memory: The Delete button of Multiple Translations Found dialog was not updated to a database server until connection was closed.
  • Bug fixes:
  • Java: If .properties file contained an empty resource and Items that localized files should contain was set to All, Sisulizer did not write the empty item.

New in Sisulizer Standard 3.0 Build 344 (Apr 15, 2014)

  • Improved Features:
  • PO: Rows are not sorted any more but kept in the original order.
  • Excluded source will not be scanned.
  • Windows resource compiler: Less than original font sized will be changed.
  • .NET: Sisulizer can use the new Chinese resource names (zh-Hans and zh-Hant) with .NET 2.0 and .NET 3.x.
  • Sisulizer can now use memory up to 4 Gbytes when run on 64-bit Windows.
  • Bug fixes:
  • WPF: If TextBlock contained styles or resources then localized XAML files did not contain those elements.

New in Sisulizer Standard 3.0 Build 343 (Apr 15, 2014)

  • New Features:
  • FireMonkey: Support for multires bitmaps added.
  • Sisulizer supports WPF applications created in Visual Basic
  • Improved Features:
  • Silverlight: Sisulizer can now localize Silverlight libraries.
  • XAML: Sisulizer now parses Paragraph element correctly.
  • VCL: Sisulizer localizes TImageList even if the localized image has different mask than the original image.
  • VCL: Support for DevExpress's TcxTreeList.Data added.
  • Sisulizer supports Visual Studio project file that uses environmental variables.
  • WPF: XAML compilation improved such way that all assembly dependencies are now found.
  • Interbase/Firebird: Other encodings but UTF-8 can be used on localized fields and rows.
  • JSON: Unicode escape output encoding added.
  • Bug fixes:
  • WPF: If the HintPath attributes of assembly references in the Visual Studio project file contained an environment variable such as $(MyDir) Sisulizer failed to compile localized XAML files.
  • WPF: If your Visual Studio project contained linked XAML files (Add as link) and the files were outside the project directory Sisulizer failed to find compiled XAML files.
  • Exchange Wizard ignored the Invalidated status if specified in the exchange filter.
  • Access: Sisulizer sometimes raised an exception when scanning an Access table using row localization.
  • Delphi: Some MAD resources was incorrectly detected as HTML data.
  • Sisulizer could not import data if alternative original language was set in the project.
  • Delphi: If TAction.ShortCut translation was disabled in component rules and the shortcut had an existing translation Sisulizer used it.

New in Sisulizer Standard 3.0 Build 342 (Jan 6, 2014)

  • New features:
  • Support for Windows 8.1 added.
  • Support for Visual Studio 2013 added.
  • Support for .NET 4.5.1 added.
  • Improved features:
  • Windows Forms: Support for DevExpress InformationTips format added.
  • XAML: Bidning values that are inside Setter are scanned.
  • Bug fixes:
  • Delphi: LaResource.LoadNewResourceFile return type changed to HMODULE. It used to be Interger that caused sometimes a crash because of a data overflow.
  • .NET: Sisulizer sometimes failed to compile XAML files when target .NET framework 4.5 or 4.5.1 was used.
  • Segmentation: Sisulizer did not save segmentation rules that were imported using segmentation sheets's Import button.

New in Sisulizer Standard 3.0 Build 341 (Nov 9, 2013)

  • Bug fixes:
  • LaResource.pas did not compile with Delphi XE5.
  • NET: If the solution file was not in the parent directory of a project file the compilation localized assembly file sometimes failed.
  • Delphi: Language switch did not work correctly if runtime packages were used.

New in Sisulizer Standard 3.0 Build 340 (Sep 10, 2013)

  • New features:
  • Support for Delphi XE5 and C++Builder XE5 added.
  • HTML: "xml:lang"-attribute in body tag can be localized. Byt default it is off. You have to turn it on. Right click html-source in the tree. Choose Properties... menu. From Attributes sheet check "BODY xml:lang" check box. Rescan youd project and new row will be found.
  • Improved features:
  • VCL: If Font.Size was negative (typically it is positive) Sisulizer changed the value to positive in the localized form.
  • Importing. Sisulizer can now correctly imported segmented text after you have changed sources segmentation method.
  • XML: Segmention works also in the case when the selected element has sub elements.
  • .NET: You can exclude any indivicual resource item.
  • .NET: Sisulizer scan comments from localized .resx file into the translation comment column.
  • If desktop file is invalid a warning message is given.
  • Bug fixes:
  • XLIFF: If you created a project and selected "Localized all similar files in a directory" option in Project Wizard Sisulizer crashed
  • Export: Sisulizer did not exports items of list view, tree view, status bar, grid header and header control components.
  • XAML: If a resource dictionary contained string value and an item was not translated or translation was same as original the item was not included into the localized XAML file.
  • .NET: If a file in a Visual Studio project contained brackets Sisulizer could not scan the file but reported an error.
  • SlMake: -escape parameter did not have any affect when importing data from Excel file.
  • When importing from XLIFF Sisulizer incorrectly imported status even XLIFF file did not contain any status value.
  • Delphi: if TImageList has 32-bit bitmaps with transparency (8-bit Alpha channel) in some cases transparensies were lost.

New in Sisulizer Standard 3.0 Build 339 (Apr 24, 2013)

  • New features:
  • Support for Delphi XE4 and C++Builder XE4 added.
  • Support for FireMonkey 2 added.
  • Improved features:
  • Windows Forms: If Language property of a form was set to other than Default and Options sheet was configured to write all items to localized files the localized files contained the original Language property. This made it impossible to edit the localized resx in Visual Studio.
  • Windows Forms: Support for DevExpress SuperToolTips format added.
  • Windows Forms: System.Windows.Forms.DataGridViewTextBoxColumn.Width property is automatically scanned without a need to add a custom component rule.
  • WPF: Title.StringFormat added into default scan property rules.
  • Bug fixes:
  • PO: If you set Items that localized file contains value in Project Wizard it was not set but kept as default.
  • Delphi: If a font name or size row had a value and then the row or data typed was excluded Sisulizer still used the entered value when building.
  • Delphi: TListView data scanning when "" strings exists.

New in Sisulizer Standard 3.0 Build 338 (Apr 1, 2013)

  • New features:
  • Support for Windows Runtime's .resw files added.
  • Support for TMS Control Pack (VCL) added.
  • Improved features:
  • Sisulizer can now properly import data from an import source when orignal language is not specified.
  • Database: Can handle GUID types as resource ids.
  • Database: Possibility to analyze and localize only one table from the database.
  • Database: Progress bar and possibility to cancel database analyzing.
  • NET: Sisulizer sometimes could not read a correct .NET version from Visual Studio project file.
  • Sisulizer setup automatically adds Sisulizer's VCL directory to Delphi XE2 and XE3's library search paths.
  • Android: When building multilingual AKP files and the default language is specified then Sisulizer uses it if there is no translation given.
  • XML: Visual editor sometimes did not show the last character if that was very narrow such as a standalone diacritic character.
  • Bug fixes:
  • .NET: If you opened source dialog of a source that contained exclude properties they were cleared once OK was clicked if you did not select Excluded Properties sheet.

New in Sisulizer Standard 3.0 Build 337 (Jan 14, 2013)

  • Improved:
  • Windows RC: New options (Use caption in menu context). By default Sisulizer uses an index for menuobjects without ID (Popup menus for example). This causes on problem when inserting a new popup menu between olds. Using this options the caption on popup meni is used instead of index.
  • If a Sisulizer project contained several Delphi sources opening of the project file took very long.
  • PO: Now it is possible to scan PO files such way that the msgstr specifies the original value instead of msgid.
  • Sisulizer's editor can now correctly handle Hindi script.
  • Windows RC: New options (Use caption in menu context). By default Sisulizer uses an index for menuobjects without ID (Popup menus for example). This causes on problem when inserting a new popup menu between olds. Using this options the caption on popup meni is used instead of index.

New in Sisulizer Standard 3.0 Build 336 (Nov 13, 2012)

  • Improved:
  • Sisulizer can import translation from localized DFM files.
  • User can choose the scope of pseudo translation.
  • Bug fixes:
  • .NET: If you had .NET solution source and you had checked Delete localized .resx files after the build process Sisulizer did not remove the localized .resx files.
  • Sisulizer setup: If you entered a custom personal directory Sisulizer did not install samples there but to the default personal directory.
  • WPF: When using binary localization Sisulizer could not correctly read some XAML resources.
  • WPF: Sisulizer did not parse correctly some extension items "{..}". This caused localized XAML files to contain invalid extension data.
  • SlMake: Using -output option with Sisulizer project containing Visual Studion solution sources caused an exception.
  • .NET: Sometimes Sisulizer wrote invalid localized resources resource and Items that localized resource files contain was set to All.

New in Sisulizer Standard 3.0 Build 333 (Jul 3, 2012)

  • Improved:
  • XAML: Sisulizer incorrectly scanned x:Code elements.
  • Android: Sisulizer uses the same compression methods as in the original file.
  • Fixes:
  • Android: Sisulizer did not correctly sign localized apk files if JSDK 1.7 was used.
  • .NET: Sisulizer could not correctly read .NET 4.5 assemblies that had been compiled with Any CPU and Prefer 32-bit options.
  • SlMake: New output option of add task replaced the previous output option of create task. The new option was renamed to outitem.
  • Java: Sisulizer did not write a translations to a resource bundle if the translation value was same as original and Items that localized resource files contains was Translated.
  • Visual C++: Sisulizer did not import text of popup menu items from localized files.

New in Sisulizer Standard 3.0 Build 332 (Jun 13, 2012)

  • New:
  • Two new validations added: Length in characters and Length in pixels.
  • Support for Salesforce translation files added.
  • Support for Visual Studio 2012 RC. Windows 8 specific stuff does not yet work.
  • Support for .NET 4.5
  • Improved:
  • Setup: Sisulizer setup does not create a new personal directory every time you update the project but keeps the exiting one.
  • SlMake: When importing SlMake can now map language smarter if there is not exact match. A sub language maps to main language (pt-PT -> pt) and vice versa.
  • SlMake: When you add a new source the initial properties will be same as when using Sisulizer.exe.
  • SlMake: origlang and output options added to add task.
  • HTML Help: If the original CHM contain binary index then Sisulizer by default does not create binary index into localized CHM file if the code page of the CHM does not match the current system code page of your OS.
  • WPF: Sisulizer can now localize icon resources.
  • Fixed:
  • If XML file (XML, XAML, etc) contained empty lines before the XML header or root element (in the case there is no header) Sisulizer raised an error.
  • Tools | General -> Output Messages -> Unknown components did not have any affect.
  • WPF: If a binding item did not contain any parameter Sisulizer created invalid localized XAML file.
  • XML: On some XML files scanning interrupts without any error leaving project in incomplete state.
  • WPF: If WPF project contained images and image localization was turned on and Visual Studio solution file (.sln) was added into Sisulizer project instead of project file (.csproj or .vbproj) Sisulizer could not compile satellite assembly files.
  • When importing translations from Sisulizer project fiel that contained HTML file Sisulizer did not prompt for overwrite even if Confirm overwrite check box was checked in Import Wizard.
  • When importing translations from Sisulizer project fiel that contained HTML file Sisulizer did not import some popup text if the popup exister both in header and body sections.
  • XAML: Sisulizer incorrectly change FlowDirection property from RightToLeft to LeftToRight even when the target language was not right to left.
  • HTML: Rows made inside tag shall have "head" as start of their context.
  • Delphi: If added 64-bit platform file Sisulizer did not use the DRC of the 64-bit file but the original DRC. This sometimes caused strings to be messed up.

New in Sisulizer Standard 3.0 Build 331 (Apr 24, 2012)

  • New:
  • Support for TBX added. You can import translations from a TBX file into translation memory or project.
  • Each rows have now two new properties: Created and changed times. Created time shows the date/time when row has been created. Changed date show the date when its original valuan has been changed. You can filter rows also by there new parameters.
  • Improved:
  • Delphi: Sisulizer automatically detects the Unicode mode of XE2 application.
  • .NET: Sisulizer can now import exisiting localized file into source that is a Visual Studio solution file.
  • .NET: Import wizard tries to import .resx data by default to the node that is selected in the project tree. If can not then the node is searched using the normal method.
  • TMX localization. Context method added. Now context can either be string value or tuid value.
  • Fixed:
  • Importing to translation memory sometimes caused and exception.
  • Sisulizer could not install all OpenOffice dictionaries but raised an exeption.
  • If you had a menu node selected and then you selected another node in the Project Tree Sisulizer sometimes raised an error.
  • Unchecking Tools | General | Translations -> Translate new rows automatically after scanning did not have any affect.
  • Visual C++ and Delphi: If source contained platform files building of a localized platform file failed sometimes.
  • If TextBlock XAML element contained commens Sisulizer incorrectly included them into strings value.
  • .NET Windows Forms: When using binary localization Sisulizer sometimes failed to read serializer data correctly and raised an exception.
  • Sisulizer could not import MLD file but raised an invalid file format exception.

New in Sisulizer Standard 3.0 Build 330 (Mar 12, 2012)

  • New features:
  • Support for NexusDB added.
  • Improved features:
  • PO: Sisulizer can handle multiple equal msgids.
  • PO: You can now contol if msgstr of localized PO file contain empty or original value in the case when there is no translation.
  • XML: Sisulizer keeps existing translations better if you change your original XML.
  • XML: You can turn off visual editor.
  • XML: 2000 characters restriction turned off by default.
  • Java: Sisulizer now parses correctly .properties file where keys use escape character (\) or : is used as separator instead of =.
  • HTML: title attribute of span tag will be scanned eg. ...
  • Bug fixes:
  • XAML: Sub items of ListBoxItem were not scanned.
  • .NET: If a Visual Studio solution file (.sln) contained a Visual C++ project, Sisulizer incorrectly handled it as C# project.
  • Pasting multiple lines of text where single line length was one character didn't work.
  • HTML: In some situations got an application error.
  • Project | Import Translations from Localized Files did not work on every file.
  • HTML: Temporary files of browser were not deleted in some situations.
  • XML: Sisulizer did not write localized attributes to into multilingual assemblies if the element that contained attributes was a single tag selement (e.g. ).
  • .NET: If directory part of a .resx file contained dots (.) Sisulizer did not scan the .resx file.
  • If you set the spell checker of original language other than default Sisulizer did not remember the settings.

New in Sisulizer Standard 3.0 Build 329 (Feb 6, 2012)

  • Improved features:
  • .NET: The properties of a component property containing XML data can be edited.
  • Delphi: TLaTranslator can now translate nested frames.
  • Bug fixes:
  • Windows: If Manifest resource was selected to be localized then Sisulizer created invalid manifest resource that prevented localized application to start.
  • .NET: Settings of Languages sheet of Visual Studio Solution file or .NET assembly filesource dialog did not have any affect: Sisulizer created assemblies using default language names.
  • Delphi: Localized resources were sometimes invalid.

New in Sisulizer Standard 3.0 Build 328 (Jan 16, 2012)

  • Improved features:
  • Support for Screen saver file (.scr) added.
  • WinForms: Sisulizer scans comment from form resource file (.resx).
  • XML: Sisulizer can correctly localized unvalid XML fiels that use unknown entities not defined in DTD.
  • When importing an old project that contain node that no longer exist in the current project Sisulizer now show the full context of the unknown node.
  • Bug fixes:
  • If WinForms had a component that Visible property was set to False Sisulizer' visual editor did not show the component.
  • XAML: Extension parsing improved to accept nested extensions.
  • Machine translators did not correctly translate strings that contained HTML tags.

New in Sisulizer Standard 3.0 Build 327 (Dec 7, 2011)

  • New features:
  • Old HTML Editor view added. By default it is not visible. To turn it on choose Tools | Editor | HTML Editor... and check Use check box.
  • Improved features:
  • Windows RC: linked translated images will be written with right path.
  • XAML: Sisulizer now scans the Binding data of a Setter property.
  • Bug fixes:
  • VB.NET: Sisulizer did not import existing resource strings.
  • SlMake did not use segmentation (if enabled) when building.
  • Java: Sisulizer incorrectly scanner keys or .properties files in case insensitive way.
  • .NET: Sisulizer did not read the assembly file of referenced projetc correctly if other configuration than default was selected.
  • XAML: If StringFormat item in Bindings started with { Sisulizer created invalid localized data.
  • XLIFF files that had menu items caused an exception during scannning.
  • If original language and a target languages were the same and a custom spell checker word was added to either of column then the other column did not used the new word.
  • If original string contained a colon and space (e.g. "Sample: ") translate duplicates or translate using translation engine did not add the colon into the translated string.
  • If label Caption property is null string, the width of the label will not set to 0.

New in Sisulizer Standard 3.0 Build 326 (Nov 10, 2011)

  • Initial 3.0 release
  • HTML source code view
  • Support for Google Translate 2.0 added
  • HTML preview
  • Delphi: Scannng Single data type properties failed

New in Sisulizer Standard 3.0 Build 325 (Nov 10, 2011)

  • Tested with Android 4.0
  • Run feature added to Android support
  • Android support ready
  • Delphi: Sisulizer did not correctly scan all items of collection list.

New in Sisulizer Standard 3.0 Build 324 (Nov 10, 2011)

  • Support for OSX resource files (.dylib) added.
  • Support for Delphi Prism added.
  • XLIFF export: resname and datetype attributes implemented.
  • .NET: Sisulizer now supports delaysigning and PFX keys in addition of SNK keys.
  • SlMake: subdirs option added to add command.
  • Delphi: Sisulizer raised an exception if a platform file did not exist.

New in Sisulizer Standard 3.0 Build 323 (Nov 10, 2011)

  • Can import localized database files.
  • Support for FireMonkey OSX files added.
  • Support for Delphi XE2 and C++Builder XE2 added.
  • Support for 64-bit Delphi and C++Builder applications added.
  • Support for FireMonkey (Delphi XE2) added.
  • Support for Android added.
  • File | Open Sample added.
  • Open Sample button added to recent list control on the main page.
  • HTML preview implemented.
  • Delphi: Sisulizer supports ISO based resource DLL extension of VCL/FMX (e.g. DEU vs. de-DE).
  • VCL: Support for Virtual Treeview's runtime switch.
  • Recent news did not show text until the first link.

New in Sisulizer Standard 2010 Build 322 (Sep 26, 2011)

  • Bug fixes:
  • SlMake could not import files if the language codes in the import file used different format as in Sisulizer project files (e.g. zh vs. zh-CN and zh.tra vs. zh-TW).
  • .NET: If the .csproj contained assembly references that has SpecificVersion set Sisulizer could not always compile the localized XAML files.
  • .NET: Building a .NET 1.x project to Arabic or Hebrew failed.
  • .NET: Sisulizer could not compile some .resx file that had reference to 3rd party assemblies.
  • WPF: Sometimes Sisulizer created invalid string into the StringFormat part of Binding. This caused XAML compilation to fail.
  • XAML: Sisulizer did not scan a style in the resource dictionary if the style did not have a name or key.
  • If a HTML resource contained incorrectly encoded HTML file Sisulizer scanning was interrupted leaving project in uncompleted state.
  • Silverlight: If the original XAP file contained satellite assembly files they were not copied on the localized XAP file.
  • Visual C++: If PE file contained very short RCDATA resources having text data Sisulizer sometimes raised an error.

New in Sisulizer Standard 2010 Build 321 (Sep 26, 2011)

  • Bug fixes:
  • If SlMake's parameters were incorrect or SlMake was run without any parameters SlMake corrupted the Command Prompt where it was run.

New in Sisulizer Standard 2010 Build 320 (Sep 26, 2011)

  • Improved features:
  • Sisulizer can automatically detect encoding of Java resource files.
  • Sisulizer can import existing Java source files also in the case when a source is a directory and not a single .properties files.
  • Bug fixes:
  • If a project contained both Simplified and Traditional Chinese only the first Chinese was shown on Export Wizard's XLIFF sheet's Target language list.
  • When exporting data to XLIFF Chinese language code were always "zh" when it should have been either "zh-CN" or "zh-TW".

New in Sisulizer Standard 2010 Build 319 (Aug 10, 2011)

  • Bug fixes:
  • .NET: If you had added .NET 4.0 assembly into Sisulizer project and target language was Chinese, Sisulizer created satellite assembly with wrong name (zh-CHS/zh-CHT instead zh-Hans/zh-Hant).
  • XML: Sisulizer sometimes raised an error when scanning XML file that has a context attribute.
  • Exchange Wizard. If you exchanged more that one packages in the same run and you had duplicates set to first only the packages all but first were invalid.
  • Silverlight: If the original XAP file contained assemblies that were excluded in Sisulizer project, then Sisulizer created invalid output XAP files.
  • HTML and HTML Help: If a HTML file contained two content type meta tags Sisulizer used the later one when the first one should have been used.

New in Sisulizer Standard 2010 Build 318 (Aug 1, 2011)

  • New features:
  • Persian translations added.
  • Improved features:
  • SlMake's output is now UTF-8 with BOM in the beginning.
  • HTML: Keep text format option now keeps the spaces after text.
  • Bug fixes:
  • WPF: If you used pseudo ranslation the default enclose characters were { and }. This caused an invalid XAML files to be created.
  • SlMake did not return an error code if a language specified in the parameter did not exist in the project.
  • .NET: Sometimes Sisulizer used wrong version of .NET tools causing the localized filed using different .NET runtime as the original assembly.
  • Text definition: The user interface contained a definition wide escape setting. This was not used anywhere but the rule depend escape settings are used. The deprecated UI removed.
  • Tex rule tester did not show the result corretly.
  • XML: If element contains context attribute and element was changed Sisulizer sometimes removed the old row and created a new one.
  • HTML: You can choose a custom browser displaying translated HTML-files. Choose Tools | Platforms | HTML... and enter used browser name.

New in Sisulizer Standard 2010 Build 317 (Jun 27, 2011)

  • Improved features:
  • Windows Forms: Sisulizer.WindowsForms.Translator improved to translate ListView and ToolTip text.
  • Bug fixes:
  • XML: If you have marked an XML element to be localized with inline (e.g. nested) XML elements and those elements contained attributes the localized files created by Sisulizer did not contain them.
  • Sisulizer hide some some row when translate only mode was turned on.
  • XML: Changing context type caused Sisulizer to crash sometimes during the first scan after the context change.
  • Firebird support was dropped out in build 316.
  • HTML, XML: The trailing slash '/' for example in will be added in a template when text including that kind of tag will start translating.
  • XAML: Sisulizer sometimes created invalid localized {Binding ...} data.
  • XML: Removeing unused items caused sometimes Sisulizer to crash.
  • XML: If XML file uses original-translation element pairs and translation did not have any initial value Sisulizer did not scan any values.

New in Sisulizer Standard 2010 Build 316 (Jun 23, 2011)

  • New features:
  • Support for SQLite and SQL Server Compact added. Sisulizer can now localize those databases and import data from them.
  • Support for Guiliani files added.
  • Improved features:
  • When exporting into TMX or XLIFF the user can now spacify if and how the translation values are written.
  • Database: If Sisulizer can not open a database table it will show the error message on the database item tree.
  • .NET: Support for Krypton components improved. Sisulizer's form editor shows the Text property.
  • SlMake import task enchanged such way that also all localized files can be imported.
  • XAML: Sisulizer can now localize all attributes of Binding element.
  • "Set to Empty" actions affects now for all selected rows. It has been moved underneath the "Translation"-context sub menu.
  • Bug fixes:
  • Access: Sisulizer could not open Access tables whose name was as a reserved word in Access.
  • .NET: If "Items that localized file contains" was set to All and resx file contained refered image files Sisulizer created invalud resx file that could not be compiled.
  • When importing SLP that cotains embedded XML resources Sisulizer did not import XML items.
  • XAML: Sisulizer scanned InputGestureText property as menu shot cut and not as plain text.

New in Sisulizer Standard 2010 Build 315 (May 7, 2011)

  • New features:
  • New optional buttons to set row status on the top of sheet. To show right click tool bar and choose "Customize...".
  • Improved features:
  • Sisulizer can import existing localized XAP into a Silverlight source.
  • HTML-files with extent different than HTM and HTML can also be scanned.
  • New options "Update by primary language only" in Windows RC. If you have different sublangauges in resources, you can check this option in order to force to update all languages fields of different sublanguages in the localized file. Otherwise only the main sublanguages field are updated.
  • Bug fixes:
  • If you typed the serial number instead of pasting it in the welcome window Sisulizer raised an error.
  • XAML: If the ToolTip contained strutured data instead of plain string Sisulizer did not scan it.
  • Sisulizer crashed when trying to open a custom spell dictionary that did not exits.
  • HTML: if you had selected "Localize all similar files" Sisulizer did not scan custom HTML files even if they were correctly mapped.
  • .NET: If you had added a Visual Studio solution file (.sln) and turned on the WIN32 resource localization Sisulizer could not create localized file but reported an invalid typecast error.

New in Sisulizer Standard 2010 Build 314 (Apr 13, 2011)

  • Improved features:
  • VCL: Sisulizer's VCL units are now better Delphi XE compatible.
  • VCL: LaDefaultLocale.pas added. It makes it possible to easily load the resource DLLs matching the default locale.
  • Bug fixes:
  • WPF: If compilation of XAML file failed Sisulizer could not create a correct support package.
  • XML: Sisulizer incorrectly read and build processing instructions () that were inside an element.
  • If there was existing .NET resource files for same culture but using different case in culture part then the Project Wizard added the culture twice that caused an error.
  • SlMake caused sometimes an error when performing validate task.
  • Delphi XE: Sisulizer could not correctly scan TListView.ItemData but caused an error.

New in Sisulizer Standard 2010 Build 313 (Apr 13, 2011)

  • New Features:
  • Support for JSON files added.
  • Improved features:
  • XAML: Sisulizer now localizes App.xaml file too.
  • XAML: Sisulizer now localizes StringFormat part from a Binding.
  • Silverlight: Sisulizer deleted the intermediate files after build process.
  • You can choose whatever validate only visible row filtered byt filter or all. See Tools | General... | Settings ans "Use filter on validation" check box.
  • Bug fixes:
  • XML: Sisulizer did not populate all elements into XML tree in the project wizard if the XML container several elements with same name but different sub elements.
  • When importing SLP with context method "By context first then by value" Sisulizer always used Never as overwrite method.
  • Resx: Items using CDATA were not localized.
  • When there is a HTML-attribute without "-characters SL couldn't draw the tag rightly. Eg. name=Test vs name="Test". Now both are OK.
  • Changing a row by clicking a new item on WYSIWYG-form, open editing will be commited.
  • VB: Sisulizer caused an error if a FRM file contained comments between properties.
  • .resx: If item used metadata instread of data Sisulizer did not write the localized item into localized .resx file.

New in Sisulizer Standard 2010 Build 312 (Jan 26, 2011)

  • New features:
  • Translation and rows status filter buttons are now also found on the sheet toolbar. By default they are hidden. You can show then clicking Properties button and checking "Show translation status filter buttons" or "Show row status filter buttons".
  • New case sensitive popup menu "Stretch Controls with Text" for forms. If the text of a control is too wide to fit the control will be strected.
  • Improved features:
  • You can include or exclude all items of selected node in Project Wizard.
  • Free Edition lets you change the properties of the visual editors.
  • Context sensitive menus and sheet toolbar buttons are enabled is the same phase.
  • When Project Wizard imports existing translations it can now import also those strings that equal to the original strings.
  • Bug fixes:
  • If .NET assembly contained XML data and XML folder was excluded Sisulizer could not save the project file after scanning.
  • Opening a project file sometimes failed if the project contains XML resource and one or more XML elements were removed.
  • HTML: Script inside attrubues can be shown correctly on the editing grid. Eg. Click here.
  • XAML: Sisulizer did not scan DataTemplate parts of resource dictionaries.
  • XAML: If a Run block containend Text attribute Sisulizer created invalid localized XAML file(s).
  • WPF: Compilation of localized XAML files sometimes failed if the project contained references into 3rd party design assemblies.
  • If output directory was set to a custom one and SLP was opened in a computer that did not contain the source file the output directory in the SLP changed.
  • resx: If data item contained CDATA element it was not scanned.
  • XAML: If a resource dictionary contained some other element name but String or system:String Sisulizer did not scan the item.

New in Sisulizer Standard 2010 Build 311 (Dec 18, 2010)

  • Improved features :
  • XML: When localizaing XML files containing language pairs Sisulizer imports the translated value.
  • .NET: Sisulizer scans resource items that contain only white spaces.
  • Bug fixes:
  • Tools | Platforms | XML dialog mixed localize and language attributes.
  • XML: CDATA element was not localized even if it was celected to be localized
  • .NET: If a Label contained LinkArea but no Text property building caused an error.
  • .NET 4.0: Sisulizer uses correct language codes for Chinese, Serbian, Azeri and Uzbek.
  • .NET: If assembly infor contained line feed character or other special characters Sisulizer could not compile the satellite assembly file.

New in Sisulizer Standard 2010 Build 310 (Nov 18, 2010)

  • Improved features:
  • XAML: Sisulizer reads data from Localization.Attributes and Localization.Comments attributes.
  • XML: Sisulizer can now optinally localize only those elements that have localize attribute set to true, yes or 1.
  • XML element can contain original and translation element pair where original contains the original value and translation contains the translated value.
  • input and rootoutput options added into SlMake.exe.
  • Importing: if the import file and current file have different node names Sisulizer prompts user to choose the right destination node.
  • .NET: Build process of localized .NET files is now faster.
  • .NET: Version and icons files are scanned when using project or solution file localization.
  • .NET: Assembly version info gets updated in localized satelite assembly files.
  • Bug fixes:
  • Silverlight: Manifest file of multilingual XAP file did not contains all satellite assemblies.
  • Sisulizer detected some Python strings that contained % but were not actually message patterns incorrectly as message strings.
  • Text: If you seleced a text file to be a plain text file in Project Wizard Sisulizer did not remember the choice.
  • Hunspell spell checker: Sisulizer read incorrectly some dictionaries that did not use UTF-8 or ISO 8859-1 encoding.
  • HTML: · and ¸ are written as coded.
  • Delphi: TEdit.PasswordChar = #0 caused an error
  • When you have editing a cell in the sheet and you click a new row on the validation pane, the cell editor got to a wrong cell.
  • Visual C++ binary: Inserting new popup menus keeps the old contexts valid.

New in Sisulizer Standard 2010 Build 309 (Sep 9, 2010)

  • Improved features:
  • Databases: Sisulizer can localize field that contains the primary key.
  • Access: You can pass optional connection string parameters.
  • When exporting into XLIFF Sisulizer adds custom namespace if sl:xxx tags are used.
  • HTML Help: Sisulizer scan localized standalone script files (e.g. .js) that are inside .chm files.
  • Bug fixes:
  • Databases: Sisulizer sometimes caused an error if the string in database started with

New in Sisulizer Standard 2010 Build 308 (Sep 9, 2010)

  • Improved features:
  • An option added to HTML segmentation that forces Sisulizer to use segmentation even on cases when there is formatting tags.
  • Sisulizer support UTF-8 encoded Hunspell dictionaries.
  • VB: Sisulizer skips strings in the header of class files.
  • Neutral Norwegian language code (no) added in addition of nn and nb.
  • Bug fixes:
  • PO: Sisulizer compiled invalid MO files when the PO file contained plural_id items and in some other rare cases.
  • WPF: Sisulizer failed to compile some XAML file that used .NET 4.0.
  • Databases: Sisulizer sometimes read primary key incorrectly. This causes some of the rows be ignored during scanning.
  • WPF: If you used project localization and the active configuration of the project was not Any CPU Sisulizer failed to compile localized XAML files.
  • Sisulizer exported row even if it was excluded.
  • VCL.NET: Sisulizer could not scan assembly files created with Delphi 2007.
  • SlMake: Sisulizer ignored escape option when importing data.

New in Sisulizer Standard 2010 Build 307 (Aug 30, 2010)

  • Improved features:
  • Source code and VB: Sisulizer does not add evaluation stamp on source code string that do not contain translation.
  • Windows RC: The localized Vietnamese RC-file will always be written in UFT-16LE (Unicode little endian).
  • HTML: comments inside tag attributes do not break the code.
  • Sisulizer can localize Visual Studio project files that contains a Silverlight application.
  • Sisulizer can localized plural forms of PO files.
  • SlMake. -name option added to validate task.
  • Bug fixes:
  • Database: If localized field were not consecutive in the table Sisulizer could not always detect the localized fields.
  • Exporting to TMX or XLIFF using SlMake caused exported file contains string in C/C++ encoded form and in as unencoded form. This prevented successful importing of those strings that contained multiple lines.
  • NET 4.0: When Sisulizer created localized satellite assembly files is incorrectly set the target runtime to .NET 2.0.
  • Sisulizer did not recognize Microsoft SDK 7.1 as .NET 4.0 SDK but .NET 2.0 SDK.
  • Pressing F3 (Search again) while editing a cell left the editor open.
  • PO: Sisulizer did not scan correctly PO source that had wild cards (e.g. *.po).
  • PO: Depending on the data in the PO file Sisulizer did not always create localized PO files.
  • When importing data into project Sisulizer sometimes overwrote the existing row comments.
  • Delphi: Wide string useage will not be set on if it has been excplicity set off.

New in Sisulizer Standard 2010 Build 306 (Jun 16, 2010)

  • Improved features:
  • SlMake: invalid and marked options added to export and exchange tasks.
  • Bug fixes:
  • CHM: When reading CHM Sisulizer sometimes raised a List out of index error and aborted scanning.
  • Export and exchange: Setting duplicates value in the filter did not have any effect.
  • PO: If the PO file header contained an emtry name and email Sisulizer scanned the empty values and when entering a value in translation sheet an error occured.
  • VCL: The language dialog of Sisulizer's VCL component did not show the initial language correctly on application compiled with Delphi 2010.

New in Sisulizer Standard 2010 Build 305 (Jun 16, 2010)

  • Improved features:
  • WinForms: Sisulizer can scan the Group data of ListView component.
  • Setup can automatically upgade existing Sisulizer 2008 installation into 2010 installation.
  • Bug fixes:
  • Text: Sisulizer's UIlet the user add string length and string count fields that are not used in text definitions.

New in Sisulizer Standard 2010 Build 304 (Jun 16, 2010)

  • New Features:
  • There is a new context label on edit translation dialogs. You can copy that value to the cipbaord.
  • Improved features:
  • If DRC is not used Sisulizer can scan strings using value as context.
  • There is a timestamp if report file names. Statistics.html => Statistics_YYYYMMDD_hhmmss.html. This is optional.
  • Bug fixes:
  • Entering Hebrew translations some original values were rendered incorrectly. Like F (%) as F )%(.
  • Tools | General | Translations "Translate new rows" check box had no effect.
  • WPF: Sisulizer did not scan Style -elements that were embedded inside a form.
  • Text: Sisulizer scanned context values as case insensitive way. This prevented to have two items that differed only by case of the context value.

New in Sisulizer Standard 2008 Build 303 (Apr 27, 2010)

  • Improved features:
  • You can now control if translation memory accept country variants or neutral languages during the translation process.
  • .NET: Sisulizer can now import existing translations from localization .resources files.
  • There is a timestamp if report file names. Statistics.html => Statistics_YYYYMMDD_hhmmss.html. This is optional.
  • SlMake: More checking added in the case of invalid parameters.
  • Bug fixes:
  • XML: Sometimes Sisulizer crashed after editing XML tags in the XML properties dialog.
  • Several small bugs in file mappings and segmentation fixed.
  • Entering Arabic or Hebrew translations some original values were rendered incorrectly. Like F (%) as F )%(.
  • Expot: When using current view settings Sisulizer did not use the current filter but filter specified in the Export Wizard.
  • WinForms: If TableLayoutPanel contained conflicting values in ColumnCount and LayoutSettings Sisulizer sometimes could not scan the form.

New in Sisulizer Standard 2008 Build 302 (Apr 27, 2010)

  • Improved features:
  • Ini: Sisulizer can also scan comments from original Ini file.
  • Microsoft Translator: Sisulizer now keeps exisitng format tag of string to be translated.
  • Importing from TMX, text and Excel files improved.
  • Binary .NET localization: Sisulizer noew create satellite assembly files even if there was not translation given.
  • Bug fixes:
  • Ini and XML: The treeview of the selected keys did not show the checked mark on the selected sections or keys.

New in Sisulizer Standard 2008 Build 301 (Apr 27, 2010)

  • Improved features:
  • Database: Sisulizer detects the field names that have lanugage or locale code appened to the field name (Sample9 is English Sample field).
  • WPF: Sisulizer scan resource dictionary items that contains complex properties.
  • WPF: Sisulizer can localize resource files that are not stored as EmbeddeResource but Resource.
  • After inserting a new source it's duplicates rows will be translated automatically is translate duplicates is on.
  • .NET: You can now localized satellite assembly files too.
  • PO: Sisulizer can also scan comments from original PO/POT file.
  • Bug fixes:
  • Database. The database item view could not drag and drop items if you had scrolled the view.
  • .NET: When using binary localization (EXE/DLL) Sisulizer did not correctly read hierarchy of ToolStripContriner.
  • SlMake: Sisulizer did not read validation settings from .sds file.
  • Imporing translated HTML-files works correctly.
  • SlMake: Sisulizer ignored xlfitems option.
  • Sisulizer somtimes added some extra characters when translating with Google or Bing strings that contain message patterns.
  • .NET: When using project localization Sisulizer sometimes read the name of the resource file incorrectly. This caused localized satellite assembly file to contain incorrect resource name.

New in Sisulizer Standard 2008 Build 296 (Jan 20, 2010)

  • Improved features
  • Sisulizer can import text, TXM or Excel file using different relative context.
  • Default text file encoding for both exprt ad import is C/C++ encoding.
  • SlMake: include and exclude options added to scan task.
  • Bug fixes
  • SlMake. If import method was set to both (-method:2) when importing from SLP file Sisulizer used only context sensitive method and did not use value method.
  • When importing text or Excel file that were encoded using Sisulizer or C/C++ encoding Sisulizer droped a character after encoded character.
  • When exporting to Excel Sisulizer raised an error if a string was longer than 0x7FFF characters.

New in Sisulizer Standard 2008 Build 295 (Dec 22, 2009)

  • Database localization supports extended fields.
  • Exchange Wizard can include all files used by source file. Not only the source fiel itself.
  • .NET: Output directory was not visible in the File sheet of source dialog.
  • .NET: Sisulizer sometimes wrote wrong binary or image data into localized .resx file.
  • Sometimes when rescanning Sisulizer shows Select Translation dialog that contains same translation several times.

New in Sisulizer Standard 2008 Build 294 (Dec 10, 2009)

  • HTML: An error happened when trying to open the properties dialog of an HTML source.
  • One radio button in Exchange Wizard was partly hidden.
  • When clicking OK in the .NET project source dialog and the output directory did not exist Sisulizer showed an error message.
  • Text source dialog: When clicking OK when Format sheet was never selected the following error message was shown: "You have to add a context item and at least one text item."

New in Sisulizer Standard 2008 Build 293 (Dec 10, 2009)

  • .NET: Sisulizer could not import combo box and list box items from translated .resx files.
  • .NET: Sisulizer created invalidf .resx file of the .resx file contained a referenced file.
  • Selecting languages properties of a alternative original caused an error.
  • Excluded VCL forms will allways be written into localized resource files.
  • HTML: If attribute is without "-characters the localized will also be without.
  • Text: If definition was turned on there was no way to turn them off.
  • Source code: If file size was 0 bytes Sisulizer raised an error.

New in Sisulizer Standard 2008 Build 292 (Nov 24, 2009)

  • How to Translate dialog is shown after creating a new project. This shows all possible ways to translate (manual, import, exchange, machine translators) and possible spell checkers.
  • Localization of plain text files added.
  • Localization of binary files added.
  • Databases: Data can now be scanned as XML, HTML, regular expression, or using binary/text definition in addition of plain string.
  • Memory management has been improved.
  • Panel buttons on startad toolbar are visible again.
  • Visual C++: meta-tags were not written into Manifest resources.
  • Project Wizard can add different file types in a single run.
  • Project Wizard can add all known files of a directory in a single run.
  • Source code: When context type was item index Sisulizer did not always kept the existing row attributes (e.g. locked) right when rescan was done after modifying source codes.
  • Databases: When writing localized data into Unicode fields Sisulizer wrote incorrect data on Access and possibly on some other databases.
  • .NET: Scanning a project that contained Visual Studio solution file failed with an error.
  • CHM: If scaning of contents, index or browser sequence was disabled Sisulizer failed to compile localized CHM files.
  • SlMake: Using -lang option with Import task caused and error.
  • CHM: Sisulizer failed to scan the binary index data of some CHM files.
  • ndo Typing when multilizer languages are visible works correctry.
  • Windows RC: Translated control styles are written correctly.
  • Windows RC and C++: Update version code page option has an effect.

New in Sisulizer Standard 2008 Build 291 (Oct 3, 2009)

  • New features
  • New separate Replace function for items in the Find Results-pane.
  • CHM: Support for RoboHelp browse sequences added.
  • Support for EDICT dictionary files added.
  • Improved features
  • Databases: If database or table no longer exist Sisulizer does not report an exception error but writes log that items does not exists any more and removed tables from localizable list.
  • When you select a component on the editor view that has been linked with an action the action row will be selected on the sheet and if you select an action row on the sheet the component assigned to that action will be selected on the editor.
  • Windows binary: You can set a padding for tails of resource segments
  • Sisulizer detects RGS file as source code file.
  • Source code localization: The user can choose the context method between string value or item index.
  • VCL units: Sisulizer can now performs runtime language switch of a VCL package (.bpl).
  • Windows binary: You can now add any number of platform files to a windows binary source. Platform files are identical to the source and are build at the same time as source. Platform file can be for example 64-bit version of the EXE.
  • Translate using translation engines menu in Cell's popup now contains list of available engines just like Column's and Project's popup menus.
  • VCL: Width properties of Label mapped components will not been able to update automatically.
  • Sisulizer handle strings in Excel, TMX and XLIFF files as plain, C-encoded (
  • ), or Sisulizer encoded (#l) when exporting or importing those files. Previously this was only in text import/export.
  • Google Translate and Microsoft Translator support improved. They can now translate text that contains HTML tags and message patterns.
  • Bug fixes
  • WPF: When localizing assembly files Sisulizer ignored Items that localized items contain settings and wrote all items to the satellite assembly files.
  • WPF: Sisulizer could not compile localized resource dictionary if an assembly files was included into Sisulizer project and resource dictionary referred into a custom assembly.
  • HTML: Scripts like "" are written correctly.
  • CHM: Sometimes Sisulizer did not add some images into localized CHM file. Especially when images were used as background image.
  • PHP: Sisulizer scanned of some encoded characters () of a string incorrectly.
  • Windows RC: The language id of VarFileInfo structure is correct.
  • Sisulizer could not open some Sisulizer 1.x file that contained Visual Basic source.

New in Sisulizer Standard 2008 Build 290 (Sep 21, 2009)

  • New features:
  • Import and export implemented to embedded customer spell dictionaries.
  • Separate preview for C++ binary and HTML-files.
  • Support for OpenOffice spell dictinary packages (.oxt) added. You can now import OXT files directly.
  • Improved features:
  • Visual C++: The widths of comboboxes can be changed.
  • Symbolic fonts (line Webdings and Wingdings) are rendered correctly.
  • Importing translated project file (.slp) Sisulizer can now import data even if the path names of the sources in imported file differ from the main project.
  • When selecting a word from spell checker suggestion list Sisulizer now can change the spelling of all other same words in teh project.
  • Tab validation finds diffrent amounts of tabs
  • New option that forces Sisulizer to prompt translating duplicate rows for the first time
  • Clicking Back and Forward buttons also select the last edited row of that node
  • Translation engine translation and duplicate translation can also be performedr for curretnly selected view.
  • Visual C++: The original encoding of embedded HTML documents can be set on a node level.
  • When importing data from Sisulizer project file Sisulizer now can import translation status even if the current translation value equals to the imported one.
  • Bug fixes:
  • Importing data from SLP and using import method Context first value then Sisulizer tried to import same values using context and value method. This caused unnesessary Overwrite prompt shown.
  • If embedded HTML resource in .NET assembly had a referfence to enbedded image resource Sisulizer caused a error.
  • If you added custom word to spell checker and did not save the project choosing Column | Edit Custom Dictionary did not show the new words.
  • If context values in the current SLP and imported SLP were differed by case Sisulizer could not import them.
  • If you have more than one language colums visible the undo of editong a cell works now fine
  • Undo after changing the sheet filters don't give an error anymore
  • Windows RC: Japanese (and other multi byte language) stringtables are written correctly
  • If more than one column used same spell checker the embedded custom dictionary did not work.
  • When using Hunspell spell checker and embedded custom dictionaries Sisulizer sometimes chrashed.
  • HTML: inside a HTML-attribute made Sisulizer to hang on.
  • MFC: Sisulizer uses wrong MFC language extension with Serbian language.
  • When Sisulizer exported data to XLIFF some items did not have unique id.
  • .NET: Assembly file compilation failed sometimes if the resource files contained Asian characters.

New in Sisulizer Standard 2008 Build 289 (Aug 23, 2009)

  • Improved features
  • VCL: TLaTranslator can now translate images.
  • .NET: If XAML or assembly compilation fails Sisulizer creates a support package (zip file) to be sent to Sisulizer support team.
  • Visual Basic: When using source code localization Sisulizer writes encoded characters (Chr(x)) also in encoded format in the localized files.
  • Databases: schema support added.
  • HTML: dir="rtl" attribute is set during building on Arabic and Hebrew languages (optional).
  • Bug fixes
  • Source code: If you had Do not translate marked rows and you modified your source code it was likely that the next scan for changed removed Do not translate marks.
  • VCL: Items in a TRadioGroup are in the right order.
  • HTML: updating has been fixed.
  • Sisulizer prompts before reopning a new project if current is modified.

New in Sisulizer Standard 2008 Build 287 (Jul 28, 2009)

  • New features:
  • Sisulizer can now sort localized table of contents data in HTML Help files.
  • Bug fixes:
  • WPF: When using assembly localication Sisulizer could not always create satellite assembly files.

New in Sisulizer Standard 2008 Build 286 (Jul 22, 2009)

  • Support for Visual Studio 2010 and .NET 4.0 added.
  • Support for Delphi and C++Builder 2010 added.
  • New build command has been added both to the main menu and the case sensitive menus.
  • SlMake: validate task with -w option returns 1 if there is at lest one validation error.
  • When creating resource DLLs Sisulizer does no longer add entry party to the resource DLL but creates pure resource only DLLs.
  • .NET assembly scanning improved. Sisulizer can now change the structure of the XAML tree in the localized resource assemblies.
  • .NET settings splitted to three parts: .NET, Windows Formars and WPF. New .NET settings are common for both Windows Forms and WPF.
  • .NET: If you entered new line for translation it was not added to the localized data if you used .NET binary localization.
  • .NET: Is a .Resx fiel that is not a form resource contained resource named with $this.xxx Sisulizer incorrectly hanled it as form resource.
  • Delphi: Sisulizer did not scan resource string comments from source code event if yuo turned scanning on.
  • In output pane gou got sotimes an error when you clicked a row after importing.
  • Windows binary: Version resource language is right for simplified chinese.
  • The edit cell activates also for special slovakian keybord inputs.
  • If you changed the language while editing a cell you got on excaption.
  • Text file: If file contains same context twice of more Sisulizser warns about it and ignores all but first.

New in Sisulizer Standard 2008 Build 285 (May 28, 2009)

  • Improved features
  • .NET: Sisulizer can now localize obfuscated assemblies.
  • Bug fixes
  • Google Translate did not translate Java's message patterns correctly.
  • SlMake.exe was invalid in the 284 setup package.

New in Sisulizer Standard 2008 Build 284 (May 28, 2009)

  • New features
  • Sisulizer Enterprise supports Microsoft Translator machine translator service.
  • Improved features
  • VCL: Sisulizer now detects Unicode VCL even if you have used runtime packages.
  • Sisulizer's Google translation feature can now translate long strings as well.
  • When importing from TMX file that contains Sisulizer's context attributes also non string values can be imported.
  • When using Google Translate Sisulizer fixes translated message patterns and filenames.
  • VCL: GetWindowsLocaleName can now return language names in currently active language in addition of English and native name.
  • Bug fixes
  • After fresh setup all translation engines were disabled. You had to enabled them manually using Tools | Translation Engines menu.
  • VCL: TLaTranslator did not translate collection item that contains period (.) in the middle of the property name in the DFM file.

New in Sisulizer Standard 2008 Build 283 (May 12, 2009)

  • HTML Help: If and old project contained CHM index having same key as different case variants (e.g. Ope vs. one) Sisulizer could not open the SLP.
  • Sisulizer setup did not change the user interface language even if you changed it.

New in Sisulizer Standard 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.

New in Sisulizer Standard 2008 Build 281 (Mar 17, 2009)

  • New features:
  • VCL: You can save DFM-files separately. Both original and localized.
  • Directly menu short cuts for translation statuses [BestGuess = Ctrl+F9, Translated = Ctrl+F10, ForReview = Ctrl+F11, Complete=Ctrl+F12]
  • Arabic samples added for Delphi, WinForms and WPF.
  • Improved features:
  • Google Translate can smarted translate strings containing hotkey characters (&).
  • .NET and VCL: Sisulizer components has better support for BiDi languages.
  • .NET and VCL: Sisulizer correctly set reading order properties (RightToLeft* and BiDiMode) when creating bi-directional (Arabic, Hebrew or Persian) WinForms, WPF and VCL files.
  • It is possible to choose what translation engine to use if there are more than one engines installed.
  • SlMake: -engine option added to translate task.
  • Empty translations can now give only by a context menu (right click the cell and choose "Set to empty").
  • Bug fixes:
  • VCL: Sisulizer's TLaTreeViewModule crashed sometimes when translating tree view data.
  • XML: Sisulizer could not import translations from localized XML files.
  • .NET: Sisulizer could not open project files made with Sisulizer 1.6 and containing .NET source and font data.
  • SlMake could not add new sources if the project already contained source with same name but on the main directory.
  • WPF: Sisulizer could not localize forms if the form resource (*.g.resources) contained icon data.
  • Java: Sometimes Sisulizer did not encode line feeds and other special characters when writing localized .properties files.
  • Windows RC: ICON controls filenames will be builded rightly.
  • The line heights of editing mode cells were higher than non-editing mode cells.
  • if you removed all spell checkers Sisulizer added the deault checkers next time you started Sisulizer.

New in Sisulizer Standard 2008 Build 280 (Feb 25, 2009)

  • New features:
  • Hungarian translations added.
  • Sisulizer Enterprise support Google Translate machine translator service. This makes it possible to automatically translate any text to more than 30 languages.
  • Empty Translation validation. Report if a translation is an empty string.
  • All Spaces Translation validation. Report if a translation includes only spaces.
  • Empty Original validation. Report if an original is an empty string.
  • All Spaces Translation validation. Report if an original includes only spaces.
  • You can filter rows by empty originals also.
  • Improved features:
  • XML: Sisulizer detects ISM format as XML file and will automatically check the XML elements that contains string data.
  • When you select a pane on the bottom SL the selected row on the pane will be also selected on the main sheet.
  • XAML: Sisulizer can now localize FlowDirection and when localizing to bidirectional language Sisulizer can add FlowDirection attribute to top level element if it does not contain it.
  • WPF: Sisulizer supports XBAP applications.
  • Java: Sisulizer can localized .properties files using any encoding (UTF-8, UTF-16, Ansi, ISO, etc).
  • Bug fixes:
  • VCL: When performing a runtime language switch from Asian language to other language in the case where menu contained automatic hot key Sisulizer could not translate that item.
  • VCL: Sisulizer units worked on different way in XP and Vista when handling .CH resource DLL. XP handled it as Chinese Trad. but Vista handled it as Chinese Simp. Now both handle it as Chinese Simp.
  • .NET: If form contained Syncfusion.Windows.Forms.Tools.ToolStripTabItem controls Sisulizer could not scan the form but crashed.
  • Importing from text file that uses escapes (e.g
  • ). If the files contained non standard escapes Sisulizer reported an error and could not import the file.
  • When exporting data from Windows binary source to Ansi text file the original column was encdoded incorrectly.
  • Excluding original values works also for XML and HTML data types.
  • Windows C++ Binary: Strings that include control characters (x00, x01, ...) can be scanned well. No extra '0' characters will be added after each scanning process.

New in Sisulizer Standard 2008 Build 279 (Jan 19, 2009)

  • Sisulizer can now better import Multilizer project files.
  • Windows RC: Unicode resource files can also be scanned
  • Windows RC: Scanning large resource files including huge stringtables have been speeded up.
  • SlMake: Importing country depend language (e.g. en-US) failed if imported from Excel or Text file.
  • .NET: When using binary localization and if string resource contained XML or binary data Sisulizer could not scan string data as string but as binary data.
  • .NET: If C# or VB source code contained a color value as RGB and the color value was splitted in two or more lines Sisulizer could not correctly read it. In addition Sisulizer could not save such a project but reported "Name can not be null" error.
  • WIN32: When localizatin an XML resource and creating localized resource DLLs instead of localized EXEs Sisulizer created incorrect localized XML data.

New in Sisulizer Standard 2008 Build 278 (Dec 20, 2008)

  • Visual Qt localization. In addition of .ts files Sisulizer can localizee .ui and .pro files visually.
  • Support for .baml files added.
  • Duplicate menu short cut validation added
  • Psudo translations are highlighted by a green color. It can be turned off on sheet dialog options. Right click sheet and choose "Properties..."
  • Qt localization improved. Sisulizer can not automatically import translations existing file. Also you can select one of the localized .ts file (e.g. sample_de.ts) instead of neutral (e.g. sample.ts).
  • XML: When Sisulizer write localized XML file it uses teh same encoding (e.g. > or >) than in the original items in the original file.
  • If alternative original is given for a project Sisulizer can use it instead of actual original when exporting data.
  • Windows: Custom resource localization improved. Supports now text, binary, image, XML and HTML data.
  • MaxPixels effects to the visual target font, not the sheet font.
  • PO: Sisulizer scans also plural forms.
  • PO: Sisulizer maintains the original formatting (e.g. white spaces)
  • SlMake: If you used -status option with export task SlMake crashed.
  • Importing from .mpr (5.x) or .mld file did not work if the were TMemo items or languages witha country (e.g. pt-PT).
  • Importing from TMX fiel did not work if items contained trailing or leading white spaces.
  • Missing char validation reports character only once even if multiple hits found.
  • WPF: Sisulizer could not scan some BAML data but caused an error.

New in Sisulizer Standard 2008 Build 277 (Dec 1, 2008)

  • XLIFF import and export implemented.
  • Support for TMX 2.0 added.
  • String resources in .resx can now be treated also as structured string, XML or HTML instead of plain string.
  • VCL: Sisulizer scans TListView and TTreeView data of Delphi 2009.
  • If your project used more than one custom assembly files (e.g. 3rd party library) Sisulizer could not compile .resx to .resources but reported the following error: Caught a PathTooLongException saying "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.".
  • VB: if a list box contained no list items Sisulizer created incorrect loalized FRX data that caused localized project sometimes not to compile.
  • Qt: If context element of .ts file contained sub elements Sisulizer could not scan the file.
  • Clipped text validation works also for check boxes and radiobutton.
  • CTRL + Z (Undo) works for resized controls in Visual Editor even when the translation sheet is inactive.
  • If you selected the last visible line on the validation list, the right line was not selected but line after that.

New in Sisulizer Standard 2008 Build 276 (Nov 26, 2008)

  • Sisulizer encodes control characters (0-#x1F, not 9, 10, 13) before writing them to SLP files. For example 0x8 becomes to #08. When writing other XML files such as TMX Sisulizer does not write the above control characters. This makes sure that SLP and other XML based files are always valid XML.
  • String resources in .NET and Windows can now be treated also as structured string, XML or HTML instead of plain string.
  • .NET: When using binary localization Sisulizer did not write localized enum data to satellite assembly files.
  • When Sisulizer created the exchanged project file (.slp). The translation status filtering was always done based on the current language and not the language that was actually being written.
  • Spell checking: If Hunspell spell checker was used Sisulizer could not check correctly those word that contained non-ASCII characters (e.g. ä).
  • Overlapped controls validations were fired for no reason.
  • Windows C++ binary: Japanese custom format ansi string were written incorrectly.

New in Sisulizer Standard 2008 Build 275 (Nov 21, 2008)

  • Silverlight support added. Sisulizer can localize Silverlight applications on Visual Studio project level, on assembly level and on XAP file level.
  • .NET: Sisulizer can now localize Width and Height of the columns and rows in grid and table panels.
  • .NET: Support for Enum properties added.
  • WPF: Sisulizer failed to scan Width or Height attributes that contained parameters (e.g. {...})
  • Opening Excluded rows dialog (Project | Excluded Rows...) made Sisulizer sometimes to hang.
  • CHM: If the HHC file name contained spaces (e.g. This a sample.hhc) Sisulizer did not add TOC to the localized CHM files.
  • Hiding a seconrary language while editing another cauded an error.
  • Replacing texts while editing a cell caused an error.
  • XML: Sometimes Project Wizard raised an error when you tried to add an XML file.

New in Sisulizer Standard 2008 Build 274 (Oct 31, 2008)

  • Windows binary: FileVersion and ProductVersion fields in a version resource header will be updated

New in Sisulizer Standard 2008 Build 273 (Oct 20, 2008)

  • Improved features
  • Janus Tab control mapped.
  • Windows binary: XML resources can be edited.
  • .NET: Support for ComponentOne's C1.Win.C1FlexGrid.C1FlexGrid added.
  • Sisulizer can now read and write UTF-8 files that contains extended Unicode characters (e.g. those above basic Multilingual Plane).
  • WPF: Sisulizer scans Text attribute of TextBlock.
  • On component mappings you can choose whatever scan sting lists as as single sting or each lines separately
  • Spansh (Spain) splitted to two different locales: Spanish (Spain, Traditional Sort) and Spanish (Spain, International Sort).
  • Bug fixes
  • CHM: By default Sisulizer assumed that original encoding is UTF-8. You have to set the original encodung manually to match you encoding (right click the CHM file and choose Encodings and set Original encoding).
  • VCL: If Tabs property in a TTabControl compoment has been changed SL gave in some cases an AV during saving project.

New in Sisulizer Standard 2008 Build 272 (Oct 3, 2008)

  • Support for .NET 3.0 and .NET 3.5, WPF/XAML, Visual Studio 2008 added, New live spell check feature, Improved support for po / pot / mo files, More 3rd Party components, Numerous improvements in usability, New Standard edition for mISVs, New Translator edition for translation and building

New in Sisulizer Standard 2008.271 (Sep 11, 2008)

  • VCL: Some ribbon components of Delphi 2009 have been added and mapped (Ribbon, Ribbon page and Ribbon group).
  • Sisulizer can now import Excel sheets that contains empty lines between data lines.
  • Windows 2000: GdiPlus.dll is not required any more.
  • Windows binary: Translation memory can localize better resource string that contain hotkeys and other special characters.
  • WPF: Sisulizer localizes UserControl items as well.
  • Nodes on the project tree are also sorted by natural order (1, 2, 11, 200) not (1, 11, 2, 200).
  • VCL: TLaTranslator can translate properties that have parent object and parent's parent.
  • For example BottomAxis.Title.Caption
  • .NET: Some assembly files contained data that Sisulizer could not read. This caused an AV during scaning.
  • Text: If original text file contained non-ASCII sometimes some of the items were scanned as null string.

New in Sisulizer Standard 2008.270 (Sep 5, 2008)

  • VCL: Delphi 2009 and C++Builder 2009 supported.
  • Support for 64 bits Windows EXE and DLL files.
  • Qt: Comments are also scanned.
  • HTML Help: Building of localized index (.hhk) or content (.hhc) files that were large was very very slow. Now it is fast.
  • Column are soted by natural order (str1, str2, str11, str200) not (str1, str11, str2, str200).
  • XLIFF: Sisulizer can now localize XLIFF file that does not have original attribute in the file element even this attribute is required by XLIFF specification.
  • Qt: Duplicate strings caused only one scanned.
  • In the Short cuts dialog if you clicked Edit without first selecting a line you got an AV.
  • Windows binary: Some version resources were scanned wrongly.
  • VCL.NET: Sisulizer could not disable scanning of binary and picture data. Also exisiting binary or picture rows could not be removed.
  • Windows: Sisulizer could not export embedded HTML data.
  • HTML: If < td > ... < / td > was introduced without < tr > ... < / tr > Sisulizer gave an AV.

New in Sisulizer Standard 2008.270 (Sep 5, 2008)

  • VCL: Delphi 2009 and C++Builder 2009 supported.
  • Support for 64 bits Windows EXE and DLL files.
  • Qt: Comments are also scanned.
  • HTML Help: Building of localized index (.hhk) or content (.hhc) files that were large was very very slow. Now it is fast.
  • Column are soted by natural order (str1, str2, str11, str200) not (str1, str11, str2, str200).
  • XLIFF: Sisulizer can now localize XLIFF file that does not have original attribute in the file element even this attribute is required by XLIFF specification.
  • Qt: Duplicate strings caused only one scanned.
  • In the Short cuts dialog if you clicked Edit without first selecting a line you got an AV.
  • Windows binary: Some version resources were scanned wrongly.
  • VCL.NET: Sisulizer could not disable scanning of binary and picture data. Also exisiting binary or picture rows could not be removed.
  • Windows: Sisulizer could not export embedded HTML data.
  • HTML: If ... was introduced without ... Sisulizer gave an AV.

New in Sisulizer Standard 2008.269 (Aug 8, 2008)

  • Sheet and range options added to SlMake's import command to make it possible Excel files select sheet and range where to import from.
  • Support for Spanish inverted punctuation marks (� and �) in TM and duplicate translation added.
  • Sisulizer now supports merged CHM files.
  • Shortcuts can be customized. Choose Tools | Shortcuts... menu.
  • .NET: Sisulizer now support .NET 1.x text rendering. This old text rendering can also be used in .NET 2.0 and later if UseCompatibleTextRendering was set to true.
  • TAdvOfficePager componet has been premapped.
  • XML: If an element contained both comment and value Sisulizer created localized XML files incorrectly.
  • Installing: When upgrading Sisulizer the setup created a new desktop icon.
  • SlMake could not import data from Excel files.
  • If you sorted the validation pane by its columns, selecting a row row didn't mact to the right one on the sheet.
  • Priorites of nodes take effect on sheet filter.
  • If far east sopport hasn't been installe on windows

New in Sisulizer Standard 2008.268 (Jul 11, 2008)

  • If you have specified custom properties, you gont "Class TStringLink for found" error when opening Silsulizer 1.6 project file.

New in Sisulizer Standard 2008.267 (Jul 9, 2008)

  • Help | Check for Update caused an error.
  • WPF: Sometimes .xaml compilation into .baml failed.
  • Java: When localization .jar file a rescan marked all string as unused.
  • VCL.NET: After rescan resource strings were marked as unused.

New in Sisulizer Standard 2008.266 (Jul 8, 2008)

  • Excluded data types will be gayed on filter panel.
  • Translation memory: Sisulizer could not use translation of Sisulizr 1.6 translation memory if they contained ! or - characters.
  • If you choosed View | Prev or Next Untranslated Row menu command and sheet was not visible you got an error.

New in Sisulizer Standard 1.6.28 (May 16, 2008)

  • VCL: FastReport 4.0 components have been mapped
  • Support for proxy server added.
  • HTML: You can edit the attributes of embedded tags. There is a ' ' mark inside of a box. Click it to open a dialog.
  • Windows RC: #include directives can be scanned.
  • Excluded string properties are visible on form editor.
  • .NET: Support for System.Windows.Forms.ToolStripContainer control added.
  • VCL: LaMenu.pas unit added that makes short cuts multilingual.
  • Import: Sisulizer did not import localized Serbian resource DLLs correctly.
  • Java: When creating a new Java project Sisulizer could not import country depend resource files (e.g. sample_de_DE.properties) but required country neutral files (e.g. sample_de.properties).
  • .NET: If System.Windows.Forms.TableLayoutPanel contained Columns or Rows that had percent containing decimal part Sisulizer did not scan the height or width of the cells correctly.
  • HTML: Statistics are calculated rightly.

New in Sisulizer Standard 1.6.27 (May 3, 2008)

  • Reading Sisulizer project file has been speeded up.
  • Output history lines have been organized into groups.
  • Text: If the end of the file contained some data that did not match 100% the rules (e.g. comment or partial match) Sisulizer wrote an error.
  • Import: Sisulizer did not import the language item from a .csv file.
  • Ini: If a section contained two or more keys with the same id Sisulizer raised an error

New in Sisulizer Standard 1.6.25 (Apr 25, 2008)

  • Rows can be filtered with comments.
  • Rows can be marked.
  • If Filter panel was hidded you got on exception during start up

New in Sisulizer Standard 1.6.24 (Apr 15, 2008)

  • SlAddRes.exe command line tool added to Sisulizer installations. Tool can be used to add embedded resources to applications.
  • Export wizard can now export select languages of the currently selected node.
  • VCL: Sisulizer detects wide string usage automatically when creating a new project or adding a new source.
  • Windows RC: Scanning has been opimized.
  • Windows RC: All STRINGTABLE rows are located on a single foder.
  • Some user interface components have been polished.
  • When creating embedded resource DLLs Sisulizer embedded the original file instead of the resource DLL.
  • XML: When importing translations from .slp file in the situation where the original XML fiel was modified after sending .slp file to translator made importing to fail or sometimes imported wrong values.
  • Vista: Sisulizer did not remember the previously used directory.

New in Sisulizer Standard 1.6.23 (Apr 3, 2008)

  • When adding .resx file or files to Sisulizer project the form or strings are now in the file node instead of inside a folder.
  • You can sen a minimum string width that will restrict the string to to autotranslated. For example value 3 means that all string length of 2 or less will not be autotranlated.
  • IBO Delphi components have been mapped.
  • .NET: Importing existing translations has been improved. Now you can import from existing localized resource files (.resx) and satellite assembly files (.resources.dll) to a .NET project, solution or assembly source.
  • Windows C binary: Text of OCX controls in DLGINIT will not be modified.
  • Sometimes during closing Sisulizer it gave an access error.
  • VB.NET: If a form had a custom namespace Sisulizer used wrong formname in the satellite assembly and .NET runtime could not find it.
  • VB: If translator enterer new line (CR LF) in the translation it was incorrectly written to .frm file.
  • VB: If VB source code contained combined strings:
  • "One" Chr(10) Chr(13) "Two"
  • they were not extracted as one string.
  • Importing .mld file containing Traditional Chinese encoded as Ansi failed because data was imported as Simplified Chinese.
  • HTML Help: Localized CHM files always contained binary index even if the original CHM did not.
  • HTML Help: Sisulizer did not read the second Name attribute in the index data.

New in Sisulizer Standard 1.6.22 (Mar 18, 2008)

  • Norwegian translations added.
  • HTML: title attribute of area scan will be scanned.
  • You can backup old lines of Output pane and browse those afterwards.
  • VCL: You can choose to scan inherited forms also hierarchically as tree.
  • Windows key of keyboard will launch a popup menu (on sheet, tree...).
  • Windows binary: If RT_HTML contains an XML data Sisulizer scans it as XML.
  • If Excel sheet to imported contained some empty cells in the begining of the first column after header row importing caused an error.
  • .NET: Items inside group box were shown tool low in visual editor.
  • .NET: If assembly file name was not AssemblyFile.?? Sisulizer failed to read the correct assembly file version.
  • .NET: If Visual Studio project file contains localized Chinese resource files (e.g Form.zh-CHS.resx) Sisulizer did not ignore them but handled them as separate resource and scanned them.
  • Add component mapping generated a "an not focus hidden component".
  • Scanning and iporting from a multilingual PE-file (e.g. .exe or .dll) did not work correctly. The first language resource was always scanned or imported.
  • HTML Help: Some content files (.hhc) used /> in the end of param tag. Sisulizer failed to scan these.
  • HTML Help: Alias and map information was not correctly written to localized .chm files.
  • .NET: Sisulizer failed to scan assemblies compiled by C .

New in Sisulizer Standard 1.6.21 (Feb 16, 2008)

  • .NET: Project Wiard did not let to localize .resx file that name eneded *.??[?].resx. For example One.Two.vv.resx or One.Two.v3.resx were not shown.
  • Ini: If a file contains two or more section with the same name Sisulizer handled them as a single section.
  • .NET: Map component dialog crashed when opened in 1.6.20.
  • Text: If one record contained more than one string Sisulizer extracted only the last one.
  • Text: Regular expressions did not always worked if they were used in before item.
  • Importing text data that contained null characters failed.
  • Case os JSP functions will not be changed.
  • VCL: Building auto sized and right justified TLabel controls.
  • VCL: Opening menu of TForm chrashed if it contains images and image type was excluded.

New in Sisulizer Standard 1.6.20 (Feb 2, 2008)

  • Importing data from Excel in context sensitive way did not import anything.
  • HTMLHelp: Importing from Help Help file (.chm) did not work.
  • HTMLHelp: Sisulizer did not scan the index data of CHM file that has been compiled for 1.0 compability.
  • HTML: if you had for example "Hello world good day." as original and you copied it to translation using "Copy Original to Translation" command, Sisulizer copied "Hello world good day.". Notice the extra ending tag. Now no extra tags will be added.
  • Relative paths keep as they were if you edit the project file on some other path or computer. For exmple on a translators machine.
  • VCL: A Label with AutoSize = True and Alignment = taRightJustify can be resized and moved correctly.

New in Sisulizer Standard 1.6.19 (Jan 23, 2008)

  • Multiselect rows in "Excluded Rows" dialog.
  • .NET: Is .NET project contained other resource file but .resx (e.g. .xafml) and a solution file (.sln) was added to Sisulizer project the building failed.
  • .NET: 1.6.18 could not build localized assembly files if you did not have either .NET SDK 3.x or Visual Studio 2008 installed.
  • JSP: white spaces will not be touched.

New in Sisulizer Standard 1.6.18 (Jan 22, 2008)

  • SlMake: validate command added.
  • In Project Wizard you can select a directory to be localized even the root directory does not contain any file type (only sub directories contain) that you want to localize.
  • SlMake: build command added as synonym to create.
  • PO: .po files can also be used as original file instead of .pot files.
  • If one language of the project already contains pseudo translation these settings will be used as a default value of pseudo translation for other languages in the project.
  • HTML: Scanning the style attribute of the IMG tag added.
  • Execluded Originals dialog has now multi select properties.
  • Building more that one output items (e.g. localized and resource files) used the same file name for all items.
  • JSP: If JSP file contained JSP comments () or a JSP tag as an attribute value Sisulizer failed to build a valid JSP file.
  • All kind of Short cuts are visible in the menu editor (including Page Up and Page Down).
  • If you hided a column from the popup menu, columns were not allways rejustified.
  • JSP: can be inside values of attributes
  • (Null) translations will be ignored as a candinate of automatic translation.

New in Sisulizer Standard 1.6.17 (Jan 3, 2008)

  • You can customize the auto translation to work with identical context only. For example you like to auto translate only the same dialogs elements somewhere else in the project. Choose "General Settings" dialogs and "Translations" tab. On the bottom exits a new radio group element to make the choose.
  • .NET: Sisulizer show correctly System.Windows.Forms.TableLayoutPanel control and its child controls.

New in Sisulizer Standard 1.6.16 (Dec 19, 2007)

  • Block exclude tags added to source code localization.
  • .NET: Items in the .resx can be shown sorted (default) or unsorted on the project.
  • "Whole words only" in Find, Replace and Filter dialogs.
  • SlMake: fillpseudo and removepseudo tasks added.
  • DB: Row id localization method no longer require the resource id field having foreign key.
  • HTML: title and accesskey attributes of input element will be scanned. For example: .
  • VCL.NET: Writing localized .resx file did not use language cascading properly (fi-FI-Savo -> fi-FI -> fi -> en).
  • Windows RC: FILEDATA items can be excluded just like all other resource types.
  • VCL: If original property (Left for example) was under 128 and the translation over 128 the was a overflow in a integer nubers. In those cases the new translated value will be written as 16-bits signend value or even as 32-bits if neccessary.
  • VB: Building VB project on language using different code page as the computer's system code page caused invalid strings to the localized forms.
  • Windows binary: Icon and cursor images scanned only after the second scanning.

New in Sisulizer Standard 1.6.15 (Nov 28, 2007)

  • Windows RC: FILEDATA items will be scanned and you can translate those. You can also exclude them from the builded RC-file.
  • Block exclude tags added to source code localization.
  • If row will be set to "Do not translate" all it's translations will have "Complete" statuses.
  • Building of localized source code file has been optimized. Building is now a lot faster.
  • The items of .NET's resource files (not forms) can be show also in the original order instead of sorting them.
  • Ini: Each section of the ini file can be added to the project tree for faster browsing.
  • Clipped text validation works rightly in Windows dialogs.
  • HTML: space after tags are removed.
  • VCL: If the DRC file was in use and some resourcestring were located in a unit that started with '_' letter the scanning failed.
  • VB: New line _ character was sometime missing in the localized file causing an invalid file to written.
  • .NET: Writing localized .resx file did not use language cascading properly (fi-FI-Savo -> fi-FI -> fi -> en).

New in Sisulizer Standard 1.6.14 (Nov 12, 2007)

  • You can remove duplicates translations from translation memory using the select translation dialog box.
  • Include and exclude tags editing added to Visual Basic source.
  • .NET: Embedded XML, HTML, images and binary resources are localized. An embedded resource is a file that is stored as raw data instead of embedding into .resources file.

New in Sisulizer Standard 1.1.23 (Feb 26, 2007)

  • Improved support for localizing .NET, Databases, VB, IntraWeb, XML and HTML. New XSL support. New regular expressions for various tasks. Support for new MS glossaries. Dozends of little improvemnts on customer request plus bug fixes.

New in Sisulizer Standard 1.1.13 (Dec 20, 2006)

  • Improved support for localizing .NET, Databases, VB, IntraWeb, XML and HTML. New XSL support. New regular expressions for various tasks. Support for new MS glossaries. Dozends of little improvemnts on customer request plus bug fixes.