Re: Charset conversion error

Previous version converted such characters all right. And there wasn't any
bogus ASCII spaces. But I looked at the KOI8 charset table and found out
that there is not equivalent symbol (0xb9) in this table.

2006/5/30, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>:
>
> > I think you are right. But everything was alright before I updated my
> > database.
>
> Previous version converted such characters to ASCII spaces. So
> probably you have lots of bogus spaces anyway. If you think it's ok,
> then you could your own CONVERSION which behaves similar to previous
> version.
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
>
> > So there are a lot of "incorrect" values in tables. And errors appear
> when I
> > execute "SELECT * FROM table".
> >
> > 2006/5/30, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>:
> > >
> > > > Hi, I have an error after updating my database up to 8.1.4 version.
> > > > "SQL Error: ERROR: character 0xb9 of encoding "WIN1251" has no
> > > equivalent
> > > > in "MULE_INTERNAL"'. "
> > > > My client program encoding is windows-1251 and database encoding is
> > > koi8.
> > > > What can I do to rectify the situation?
> > >
> > > It suggests that Windows-1251's 0xb9 cannot be converted to KOI8. You
> > > should check your Windows-1251 data.
> > > --
> > > Tatsuo Ishii
> > > SRA OSS, Inc. Japan
> > >
> >
> >
> >
> > --
> > Verba volent, scripta manent
> > Dan Black
>

--
Verba volent, scripta manent
Dan Black