From: Everton L. B. <ev...@fa...> - 2004-03-25 20:49:14
|
Chet Heilman wrote: > Hi Everton, Hi, > > I can't tell what is happening from that stack trace. It was not in > RLIB at the time it crashed. I think that maybe RLIB does not remove its > exception handler when it exits, or maybe it got stuck in a loop and got > killed - can't tell. > > Anyway, was your database created with a specific encoding? The > latest RLIB requires the DB to be in UTF8. That is probably why the > characters are not coming out correctly. I suspected this might be a > problem in this version, but making everything work out correctly could > get very confusing. If this is the case, we need an input encoding for > the datasource. > > I suspect that your DB is encoded as iso-8859-1. Yes, you are right. > > 1.1.8 versions of RLIB use UTF8 internally. libxml always produces UTF8. > > Does anyone know if there is a way to 'ask' the db what encoding it > is using? That would eliminate the need for the app level to set it. At Postgres you can execute: SELECT getdatabaseencoding(); Returns for me 'LATIN1', it's the same of 'ISO-8859-1' > > Anyway, I'll make some changes so that you can set a datasource > encoding. This would be the encoding used by the datasource. > > We could have a similar problem with passed parameters, if they are > not UTF8 encoded. > > Chet > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Rlib-devel mailing list > Rli...@li... > https://lists.sourceforge.net/lists/listinfo/rlib-devel > -- Everton Luis Berz Nucleo de Sistemas :: FACCAT - Faculdades de Taquara +55 51 541 6600 - R.647 ICQ 7807919 |