Sisulizer versions

v2.1 [Aug 18, 2010]
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.

v1.6 [Mar 14, 2008]
Sisulizer 1.5 comes with nearly 100 new and improved features, like: Windows Vista support, HTML Help support, improved HTML support, version-independent .NET support incl. .NET 3, Delphi 2007 support, direct Multilizer project conversion, GUI in nine languages and much much more.