> 
> 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.

> There is a read password ("Read Password=..." entry in elogd.cfg) on
> the logbook which I cannot bypass from the client.

This is correct. The elog utility works with write passwords and user level access
(specifying a password file), but not with read passwords, that's not implemented. Use a
password file and you should be fine.

> There is a required attribute called "Publiek", and it's defined as
> MOptions. Whenever I try to upload, I keep getting the message that 
> it misses this attribute.

Your problem is that you try to combine a MOptions with a "-r <n>" (reply-to) option. I
have never tried that and found there is a problem. I changed the way MOptions are
submitted. Instead of using <name>_0, <name>_1 etc, you can now do a 

-a "<attrib>=<value1> | <value2>"

This also solves the problem with the "-r" option. You have to upgrade elogd.c from CVS.

> On a side note, one would expect that when "Fixed Attributes Edit" or "Fixed Attributes
> Reply" is set, the attributes in this list shouldn't be supplied with the command line client.

Well, don't shoot yourself in the foot! The communication between elog and elogd is limited. elog
more or less submits "blindly" whatever you give it on the command line. If "Fixed Attributes
Edit/Reply" is set in the configuration, this only affects the web page with the entry form, so
these attributes are not shown as edit boxes. They are not checked during submission by elogd. Now
to get the same functionality with elog, elog whould have to retrieve the full entry form, analyze
the HTML code, find out which attributes have edit boxes and which ones not. So that's a lot of
work. Since most people use elog in scripts, they set it up once and forever correctly. There are
actually a few people which even want the functionality that elog can change attributes which are
normally fixed.

- Stefan

> Okidokie. May I then humbly suggest to mention this in the documentation of the elog command client?

I did modify it already, see http://midas.psi.ch/elog/userguide.html at the bottom.

> Was just wondering about the status of the multi-line attributes in Elog, are 
> they implemented in elog yet? If not is that something you are planning to do 
> in the future?

In order to have multi-line attributes, the whole format of the logbooks has to be
changed. I plan to use XML for the logbook format in the future. We would not have
any more one file per day, but one big file per logbook. I have already some XML
functionality in elog, but this one requires a major rewrite of the whole code. On
the other hand, searching etc. will become much faster afterwards. I plan to start
this development soon, but it might take quite some time, so don't expect it
before summer or fall.

Best regards,

  Stefan

> I'm looking for an option to attach a user to a log?
> 
> For example:
> 
> Rob is making the log, and whant's to dedicate the log to a stagaire,
> the stagiare recieves an E-mail so that he can do the job?
> 
> Bud we all want recieve the mail bud the stagiare see's that the job is for 
> him.

Maybe use an attribute for that?

Like

Attributes = Author, ..., stagaire
Options stagaire = Jim, Joe, ...

So Rob can select a stagaire from the list, and the email contains this name.

- Stefan

> I would like to increase the spacing between 'MOptions' choices. I have
> created a new theme and have been playing with the CSS stylesheet. But can't
> find how to increase this spacing. Having lots of fun otherwise!

Intersting question (meaning: I don't have an answer... (;-) )

The class which applies there is "attribvalue". You can increase the padding for
that class, but that only increases the space between all options and the cell
border, but not between them. I could put each MOption in a separate cell of a
subtable. Then one could increase the padding between them, but the layout would
be fixed, meaning that they are always left-to-right. As you can see in this
forum, the MOptions nicely place below each other if the screen is too narrow.
This functionality would be lost.

Maybe someone else has a clever solution?