Hi *,
I have two ideas witih web providers.
1. There's used on some places NONE charset. It's not good and IMO it
should be converted to unicode.
2. There's used UNICODE_FSS in other column's charsets. But this is
outdated. In FB 1.5 the UNICODE_FSS is the same as UTF8 (with all bugs
etc.; UTF8 is alias to UNICODE_FSS), but in FB 2.0+ the UTF8 is new
charset (without bugs :)). So using UTF8 will not be problem (from 1.5
POV) and for 2.0 users gives a great advantage. We can also use
different versions of scripts (but it's no neccessary) just maybe for
readability.
Changes in C# code will be minimal.
What do you think?
--
Jiri {x2} Cincura (Microsoft Student Partner)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
