Comments on: Why you should develop with UNICODE? http://codereflect.com/2009/08/14/why-you-should-develop-with-unicode/ On Windows Programming, Technical Tips etc... Sat, 20 Mar 2010 03:19:33 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Sarath http://codereflect.com/2009/08/14/why-you-should-develop-with-unicode/comment-page-/#comment-2292 Sarath Tue, 18 Aug 2009 07:14:21 +0000 http://sarathc.wordpress.com/2009/08/14/why-you-should-develop-with-unicode/#comment-2292 That's truly inputs. Of course the usage of UNICODE strings must be standardized. That’s truly inputs. Of course the usage of UNICODE strings must be standardized.

]]> By: kneaver http://codereflect.com/2009/08/14/why-you-should-develop-with-unicode/comment-page-1/#comment-2293 kneaver Tue, 18 Aug 2009 07:07:14 +0000 http://sarathc.wordpress.com/2009/08/14/why-you-should-develop-with-unicode/#comment-2293 Yes great question. Well, after using UNICODE for a while, there are quite a lot of drawback as well. - A lot of the data we manipulate are still perfectly stored on 8 bit. Either because it's the standard (URL, web pages) or because it uses UTF8 instead of UTF16 and you don't want to decode it. - UTF16 is equal to wchar_t and BSTR on Windows but on linux wchar_t is UTF32. There is no standard there. - The idea that one character is one string element is not true for UTF16 as well. Several old or uncommon languages still require UTF32. So you will still have to carry the complexity of multichar encoding with UTF16. - Nothing assure that future MS compilers will keep the equation BSTR = wchar_t = UNICODE. - Eventually we started recoding to UTF8. Yes the conversion will take place at some places if the string is just passed around it will stay UTF16. May be it just take to abandon the idea are simple objects based on arrays. - Suddenly when you start manipulating queries with resultsets of 500 megs memory is again an issue. in UTF16 it becomes 1 gig. Yes great question.

Well, after using UNICODE for a while, there are quite a lot of drawback as well.
- A lot of the data we manipulate are still perfectly stored on 8 bit. Either because it’s the standard (URL, web pages) or because it uses UTF8 instead of UTF16 and you don’t want to decode it.
- UTF16 is equal to wchar_t and BSTR on Windows but on linux wchar_t is UTF32. There is no standard there.
- The idea that one character is one string element is not true for UTF16 as well. Several old or uncommon languages still require UTF32. So you will still have to carry the complexity of multichar encoding with UTF16.
- Nothing assure that future MS compilers will keep the equation BSTR = wchar_t = UNICODE.
- Eventually we started recoding to UTF8. Yes the conversion will take place at some places if the string is just passed around it will stay UTF16. May be it just take to abandon the idea are simple objects based on arrays.
- Suddenly when you start manipulating queries with resultsets of 500 megs memory is again an issue. in UTF16 it becomes 1 gig.

]]>