Actually, Unicode / ISO 10646 is a 21-bit encoding, with values from 0 to
0x10.
On Wed, Oct 8, 2014 at 10:13 AM, J Decker wrote:
> On Tue, Oct 7, 2014 at 2:20 PM, jose isaias cabrera <
> jic...@cinops.xerox.com
> > wrote:
>
> >
> > "J Decker" wrote...
> >
> >
> > So, I
On Tue, Oct 7, 2014 at 2:20 PM, jose isaias cabrera wrote:
>
> "J Decker" wrote...
>
>
> So, I guess it is technically not allowed to encode 11 bit unicode
>> characters as 16.
>> the greek characters are 0x3XX which is 10 bits... I checked what
>> WideCharToMultiByte
"J Decker" wrote...
So, I guess it is technically not allowed to encode 11 bit unicode
characters as 16.
the greek characters are 0x3XX which is 10 bits... I checked what
WideCharToMultiByte was doing and found it was using 11 bit encodings...
fixed my encoder to use an appropriate size for
So, I guess it is technically not allowed to encode 11 bit unicode
characters as 16.
the greek characters are 0x3XX which is 10 bits... I checked what
WideCharToMultiByte was doing and found it was using 11 bit encodings...
fixed my encoder to use an appropriate size for what's required, added 11
Did find sqlite3_prepare16_v2; this allows the replace to work without
error; but the result from the select to read it back isn't the same as
what I put in...
Still trying to figure out the differences... going to implement
WideCharToMultiByte as conversion too to see what differences are
Hello J,
string_tsTest;
int nLengthNeeded = WideCharToMultiByte(CP_UTF8, 0, pszWide,nLength, 0,
0, 0, 0);
if( !nLengthNeeded )
{
ASSERT(0);
return(E_ABORT);
}
sTest.resize(nLengthNeeded + 16);
On Tue, Oct 7, 2014 at 5:39 AM, Richard Hipp wrote:
> On Tue, Oct 7, 2014 at 12:06 AM, J Decker wrote:
>
> > I saw a few things go by about unicode... and understand that it should
> > just work to store the data as characters...
> >
> > I'm getting a
On Tue, Oct 7, 2014 at 8:50 AM, J Decker wrote:
> On Tue, Oct 7, 2014 at 5:02 AM, Richard Hipp wrote:
>
> > On Tue, Oct 7, 2014 at 12:06 AM, J Decker wrote:
> >
> > > I saw a few things go by about unicode... and understand that it should
>
On Tue, Oct 7, 2014 at 5:02 AM, Richard Hipp wrote:
> On Tue, Oct 7, 2014 at 12:06 AM, J Decker wrote:
>
> > I saw a few things go by about unicode... and understand that it should
> > just work to store the data as characters...
> >
> > I'm getting a
On Tue, Oct 7, 2014 at 12:06 AM, J Decker wrote:
> I saw a few things go by about unicode... and understand that it should
> just work to store the data as characters...
>
> I'm getting a unrecognized token... and think this page isn't right...
> I was playing with greek
"J Decker" wrote...
I saw a few things go by about unicode... and understand that it should
just work to store the data as characters...
I'm getting a unrecognized token... and think this page isn't right...
I was playing with greek translation of 'mary had a little lamb'
On Tue, Oct 7, 2014 at 12:06 AM, J Decker wrote:
> I saw a few things go by about unicode... and understand that it should
> just work to store the data as characters...
>
> I'm getting a unrecognized token... and think this page isn't right...
> I was playing with greek
I saw a few things go by about unicode... and understand that it should
just work to store the data as characters...
I'm getting a unrecognized token... and think this page isn't right...
I was playing with greek translation of 'mary had a little lamb'
http://www.sqlite.org/tokenreq.html
13 matches
Mail list logo