The problems came from the French accents and the German umlauts. I changed the XML
charset, so this should be fine now. New version is under CVS.

> I included the HTML result so you can "visualize" what's going on (this may 
> also be on the avant browser side !).

I believe it is on the avant browser side. Below is the same shown in the
SharpReader browser, where everything is displayed correctly.

> i am trying to implement ssl features on our logbooks. however, it seems
> that stunnel has drastically changed their program and the usual startup
> procedures listed on the elog page don't work.
> so, what is the new method for getting elog set up with stunnel?

stunnel is kind of a deprecated feature. Better use the SSL proxy of Apache,
as written in the elog admin guide. If someone else figures out how to use the
more revent stunnel, I'm willing to update the documentation.

> i

> is there a way to set up a logbook so that a password is required to get
> into it, but no username?

Have a look under "Access control" in the manual. What you need is "Read
Password".

> thanks. that seems to get me the functionality i needed. is there any way to
> get rid of the username line when using the "Read Password" feature?

No, this is an HTTP standard. The dialog box is generated by your browser, and I
do not know any way to prevent it.

> When compiling elogd on AMD64 (in 64 bit mode) there are many 
> warnings like these:
> 
> src/regex.c:3769: warning: cast from pointer to integer of different size
> src/regex.c:3769: warning: cast from pointer to integer of different size
> src/regex.c:3775: warning: cast to pointer from integer of different size
> 
> The reason is the (int) cast, which (I think) is not necessary.

Unfortunately I don't have a 64-bit compiler to try. Can you please check if
elogd.c has similar warnings or only regex.c? The ones in elogd.c I can fix,
but regex.c is straight from the GNU C library, so we would have to wait intil
they fix it. Or can you get it from the 64-bit C library? The point is that I
need the source code, so that I can compile it under Windows as well. Can you
try to compile elogd without regex.c, like 

gcc -g -O -W -Wall -o elogd src/elogd.c

If that works fine, we don't have to compile regex.c under linux. But I guess
it's still needed fot Solaris and other non-GNU Unix brands.

> I needed the export feature and could not find documentation on it in the latest 
> version. I finally read the code and added Find Menu Text = <filename>
> where filename had the tags XML, CSV1, and CSV2
> This always exports all records. Shouldn't it just export the records appearing in 
> the window?

Exporting workes as follows: Click on "Find", and switch the radio button to XML or CSV.
If you click on "Search", you will be prompted where to save the resulting "export.xml"
or "export.csv". I did this through the search page because you can then specify som
filters, in order not to export all records.

> (BTW, the XML export is not valid. Internet Explorer complains about the first line)

The XML charset in the first line was missing. I fixed that, new version under CVS. Or
you can manually change the first line to

<?xml version="1.0" encoding="ISO-8859-1"?>