Hi! I’m testing ScriptCase 8 and it seems great for our bussiness. But we do have one problem that we have to solve before we can buy the product. I started testing Scriptcase 3 days ago, started with a simple grid, added some forms and all looked well. I’m connecting to our company mssql database that uses Windows 1250 charset. I think you now know what my problem is. I solved my elementary problem with ini_set(‘mssql.charset’, ‘cp1250’) but because all the controls use AJAX only the postback (or browser refresh F5) had normal type of characters. When i went from page 1 to page 2 on the grid, the encoding changes since it has to be encoded into UTF-8 for JSON and then decode it back to the “original” charset. The problem is that wont ever work for Windows 1250 charset. It’s because ScriptCase 8 code generator uses mb_convert_encoding function which doesn’t support Windows 1250. Also I see that in the nmutf8.php generated file you only check if the given string is a UTF-8 string or not. If its not UTF-8, it assumes it’s in the default charset (from session) and converts from that to UTF-8 in mb_convert_encoding.
Do you have any advice how to use your application and then replace all the mb_convert_encoding calls with ICONV calls. Iconv php converter supports windows-1250 (cp1250). Grid works semi-well if I set Language charset (sl.lang.php file) to Windows-1250 and convert all the calls from mb_convert to iconv. The caching with AJAX then works, but I loose the text on the export button and alot of other buttons (only one button is visible and thats for sorting) so I’m guessing that button text isn’t going trough the same converters as other data is. Any advice for a trial user that really wants to use your app but I just cant buy before I find a solution for this.