Sisulizer Free Edition Changelog

What's new in Sisulizer Free Edition 4.0 Build 374

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

New in Sisulizer Free Edition 4.0 Build 372 (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 Free Edition 4.0 Build 372 (May 23, 2018)

  • Support for .NET 4.7.2 added.
  • If .NET 4.7.2 was installed Sisulizer did not detect .NET 4.5 or later.

New in Sisulizer Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 4.0 Build 365 (Mar 1, 2017)

  • 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 4.0 Build 361 (Jul 21, 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 4.0 Build 357 (Oct 23, 2015)

  • IMPROVED:
  • 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 FIXED:
  • 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 3.0 Build 341 (Nov 8, 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 Free Edition 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 Free Edition 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.

New in Sisulizer Free Edition 3.0 Build 338 (Apr 24, 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.

New in Sisulizer Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 2010 Build 327 (Dec 23, 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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 Free Edition 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.