Re: [Rlib-devel] RLIB-1.3.2 questions, problems and an ODBC fix

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

> I don't know the PDF internals enough to answer that.
> I think for my purpose it would be enough to accept the strings
> in UTF-8 and output them in ISO-8859-2. That would require only iconv.

Ok.. I'm changing things around a bit from how it worked in RLIB 1.2.0

How does this sound:

1) LIBXML is always utf8 and no work is needed there

2) DataSources could really be in any encoding.  I'll add a new api
rlib_datasource_set_encoder(r, "data_source", "iconv decoding...");

3) Paramaters passed in from rlib_add_parameter don't need to be touched
because the user can do this on their own (it will be assumed they are
in UTF8)

In the actual engine RLIB will use g_utf8 functions to do all the string
stuff (We have wrappers in util.h.. I'll preform an audit to make sure
nothing has fallen out)

Outputs:

We will need to typically encode the output in order to make things
work.  

so rlib_set_output_encoding(r, "iconv encoding");

In PDF for sure we probably need to do this.  In HTML we need to do this
**I think** and in the <HEAD> do something like
content="text/html;charset=iso-8859-2" 

I'm using your name as my test bed to make sure this all works.  :)

- bob