- If you right click the form editor you find a new menu "Browse Components...". It shows all components and their properties in a single dialog.
- Visual report localization support added for Ace Reporter and ReportBuilder.
--- Bug fixes ---
- Even if you unchecked install language or dictionary the setup installed the file any way.
- Sometimes Sisulizer detected string to a message string pattern and the validation process reported an unnecessary inconsistent message string validation error.
- You could not drag and drop localized database table undernearth the original database table.
【 V1.6.7 】
--- Bug fixes ---
- When the sheet had been resized, some texts wrapped incorrectry
- C++: POPUP menus sometimes were not ended correctly.
【 V1.6.6 】
--- New features ---
- Combined string support added to database localization.
- You can now choose the updation method of Windows resources. Possoble value are: Auto, Windows, Custom. Auto works like it has been. If the generated EXE of DLL are invalid, you can try Windows or Custom.
--- Bug fixes ---
- If you have sepecified an alternative original language it is used instead of original in filtering.
- "Exclude the whole component and its properties" options in component mappings works property.
- Japanese resource file (Sisulizer.JP) was invalid in 1.6.5. Sisulizer crashed if started in Japanese.
- If TMX file cotained context data and it was imported by value (e.g. not by context) nothing got imported.
- If there was a SQL Server translation memory added to Sisulizer it raised an error when starting.
【V1.6.5】
--- New features ---
•Support for Firebird database added. Sisulizer can import data from Firebird, localize Firebird tables and store translation memory on a Firebird database.
•You can select an alternative original language (=any language in the project). The selected language will be used instead of the original on the sheet and WYSIWYG editors. That will help to translate from any other than original language. Choose Project | Options... and select an alternative original.
--- Bug fixes ---
•Importing data from large Excel files caused an error.
•.NET: If .NET runtiem directory (e.g. C:\Windows\Microsoft.NET\Framework) contained two directories for the same .NET version (e.g. beta and release) Sisulizer used the first one (beta) and that caused creating the localized satellite assembly files failing.
•.NET binary localization: If you excluded a node in the project Sisulizer could not create localized satellite assembly file
【V1.6.4】
--- Bug fixes ---
•HTML: This kind of code <THEAD>Some text here</THEAD> doesn't raise an excaption.
•Visual Basic: List index out of bound error happened sometimes hen scanning VB forms.
•.NET: Run original was enabled event if the drive did not contain Visual Studio project file.
- If you right click the form editor you find a new menu "Browse Components...". It shows all components and their properties in a single dialog.
- Visual report localization support added for Ace Reporter and ReportBuilder.
--- Bug fixes ---
- Even if you unchecked install language or dictionary the setup installed the file any way.
- Sometimes Sisulizer detected string to a message string pattern and the validation process reported an unnecessary inconsistent message string validation error.
- You could not drag and drop localized database table undernearth the original database table.
【 V1.6.7 】
--- Bug fixes ---
- When the sheet had been resized, some texts wrapped incorrectry
- C++: POPUP menus sometimes were not ended correctly.
【 V1.6.6 】
--- New features ---
- Combined string support added to database localization.
- You can now choose the updation method of Windows resources. Possoble value are: Auto, Windows, Custom. Auto works like it has been. If the generated EXE of DLL are invalid, you can try Windows or Custom.
--- Bug fixes ---
- If you have sepecified an alternative original language it is used instead of original in filtering.
- "Exclude the whole component and its properties" options in component mappings works property.
- Japanese resource file (Sisulizer.JP) was invalid in 1.6.5. Sisulizer crashed if started in Japanese.
- If TMX file cotained context data and it was imported by value (e.g. not by context) nothing got imported.
- If there was a SQL Server translation memory added to Sisulizer it raised an error when starting.
Originally posted by tsjking at 2007-9-24 21:22:
終於更新到1.6.8了,忍了很久了想說應該近期中會再度升級
今天上來就看到了,要不然一直下也不是辦法,如同osk大說的
一樣,下來備用,一時忘了就放著也沒有刪,最近要找時間清理
一下了,謝謝yoyo大持續更新分享這個 ...
