- .NET: Validation caused an error if a string contained { and } and not an number following {.
- .NET: For some forms Sisulizer gave a warning that Localizable property is not set true even it was set true.
- Exporting items from transaltion engine when a project was opened caused an error.
- When editing and you clicked to another cell the sheet left to a cell selecting state
- Print Preview works again (this got broken in the build 1.5.5)
- Edit | Replace... was not working correctly in certain situations
1.5.7
- .NET: If a ListView or component derived from ListView has column headers and the component was not mapped to list view the project got dirty (e.g. needs to be saved) after every scan.
- Visual C++: Sisulizer failed to create multilingual output file.
1.5.6
- VCL: Changing language on runtime caused Sisulizer's function to crash if a form contained DevExpress components.
- SlMake: Exchange did not include the project file to the EXE package.
- If loading of the project file was cancelled the hour glass cursor remained on the screen.
- Updating the scroll bars of the sheet.
1.5.5
- .NET: Adding a file to the Excluded file list of the source did not exclude scanning or building the file.
- .NET: When using binary localization for an assembly that container aresource string that lengthwas more than 63 but less than 129 characters caused Sisulizer to create invalid resource data that .NET runtime could not load.
- .NET: Forms that had different parent information on .resx and source (.cs or .vb) caused Sisulizer to raise an error. Now Sisulizer ignores information from .resx if it conflicks to source.
- VCL: When Sisulizer created a multilingual EXE it left the original neutral resources intack that caused that localized resources we never used.
- VCL: Sisulizer's VCl functions did not compile on Delphi 5.
- VB: If the translation of a Label component was longer that the original text Sisulizer's visual editor showed text on two lines. However there was no error in the localized file created by Sisulizer.
- VB: Sisulizer failed to scan .ctl file having binary data in .ctx files.
- Database: Row localization without combined primary key did not work with Paradox and dBase.
- Vista: Sisulizer raised an exception after pressing OK in the General Settings dialog (Tools | General). Changed settings did not stored.
- SlMake could not compile localized .NET satellite assembly files but reported an error about missing .NET runtime.
- When importing data from existing localized files and those files contained comments Sisulizer imported the comment to the row and not to translation.
- When another language has been selected, the view mode ob the project tree will be refreshed.
1.5.4
- HTML Help: Creating an exchange package made all rows hidden in the package.
- Message Windows binary resources with IDs over 16-bit boundary can be handled.
- Project | Edit Source... menu will be updated correctly.
- Excel export: The header line was sometimes written incorrectly levaing some column name unwritten.
- .NET: Importing an satellite assembly file to a .NET project source (e.g. .csproj added to .slp) did not import anything.
- XML: Sisulizer created invalid localized XML files of the original file contained CDATA and text elemetns mixed in the same tree path.
- .NET: Validation caused an error if a string contained { and } and not an number following {.
- .NET: For some forms Sisulizer gave a warning that Localizable property is not set true even it was set true.
- Exporting items from transaltion engine when a project was opened caused an error.
- When editing and you clicked to another cell the sheet left to a cell selecting state
- Print Preview works again (this got broken in the build 1.5.5)
- Edit | Replace... was not working correctly in certain situations
Originally posted by tsjking at 2007-6-1 22:40:
yoyo大!真的不好意思說,看到新分享才想到跟大大求教過的問題,可是還不能完成是,只會用這個工具來翻中文,要配合其它的工具好像有點困難,還不能理解,剛好工作上有事情不能繼續,沒有程式語言的基礎,對初入門比較難一些,那個cxat的流程可能還要爬文才能了解,今天有看另一篇的說明,但還不是很了解,我會繼續努力,謝謝教學
