> using:
> Display mode = threaded
> List display = Subject, Type, Author, Date
> 
> in the config file (omitting "ID" then) rise the bug
> 
> ie, an unneeded "," is displayed after the "supposed to be printed" ID

Fixed in CVS revision 1.574

> > I tried to substitute avery occurrence of hard coded "&" with "&" but it does
> > not do the job at all ... infact the first time the HTML code is ok, but
> > following a link let the browser to automatically decode html entities .. and
> > everything turns wrong again ... maybe the encoding should be done in
> > printing-to-the-browser-time ..

That won't help, since the 'Start page = ...' string is used for redirection (outside
of any HTML). The '&' thing should only occur inside the HMTL text.

I changed elogd.c to encode things properly, but I'm not sure if I covered all
occurences. Can you try release 1.576 if it works correctly?

> Is there any solution to obtain an non-clickable column ?
> For example here : http://midas.psi.ch/elogs/Config+Examples/ what should 
> I do to obtain the data of the Category column non clickable?
> I don't have find a solution in the Syntax of elogd.cfg  
> (http://midas.psi.ch/elog/config.html)

What do you mean by "non-clickable column"? The column header for sorting, or
the column contents which brings you to the single entry page? For both of
them, there is no way right now to obtain that. Why do you want it?

> If I want to go to the latest CVS release, what files do I have to compile
> along with the elogd.c file?  Also, do I need to use any special gcc flags
> for the compilation?  Thanks.

You need elogd.c, mxml.c and regex.c, the Makefile you can get from CVS as well 

http://midas.psi.ch/cgi-bin/cvsweb/elog/Makefile

> Is it possible to get around this problem by having more then one main text field 
> per record?

No, not at the moment. You can increase the 1500 characters by recompiling elogd, but
at some point you will hit the stack limit and elogd will crash. I plan a major
redesign with completely dynamic memory allocation, thus permitting any number of
characters on any attribute. But this will take a couple of months or so.

I fixed this problem in revision 1.586. It will be contained in the next release.

> 
> Display subject = <b>$subject</b>
> 
> is printed to the browser encoded, so that it is diplayed as is..

I fixed that in revision 1.587. Note however that you should do the formatting
of attributes better using the CSS functionality, since it gives you more
possibilities. See for example the subject of this forum, which has it's own
CSS class "subjname", which has a larger font size. You select your own class like

Format Subject = 0, subjname, subjvalue

in the configuration file. Then add the classes into the CSS file.

Now elog shows each attribute which contains a "<b>" encoded (as HTML). But if you
want to write a subject line like "For bold use <b> in HTML", then the "<b>"
triggers the HTML display, so it is not written as is, which is not what you want in
that case. Since there is no switch "Submit as HTML text" for the attributes, it is
hard for elog to "guess" if you want HTML encoded or not.

> I talk about the column contents. In fact on ELOG, we store password so its 
> more easyer to click twice on it to select them and after to copy them instead 
> of select from right to left the password and to try to copy them. The HMTL 
> link gave problem, its more hard to copy data from HTML link than an normal TXT.
> A little hard to explain sorry for my mistakes and explication I'm French :o).

I added a new option "Link display = ...", with which you can restrict the number of
attribues which gets a HTML link. If you put

Link display = ID, Author

then only the ID column and the colum with the Author are shown as HTML links, all
other are shown as simple text.

The new version is under CVS. This option will be included in the next release.