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

> 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

> When creating/updating entries in elog, excluding the main text field are 
> there any limits on the size of the other fields?

Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
currently set to 1500 characters. You can try to increase this and recompile,
but at some point you will produce a stack overflow and elogd will crash. So
the current length is a compromise.

- Stefan

For some reason it looses the "m" so line 5 instead of having
"hh:mm" has "hh: m"


Please ideas ;)
Cheers,
GL.

For some reason it looses the "m" so line 5 instead of having
"hh:mm" has "hh: m"


Please ideas ;)
Cheers,
GL.

> > Is there any way to include the text of a log message in the CSV export? 
> > Anyway to include a pointer to the attachment?
> 
> The text of a log message is usually several lines long. To my knowledge, CSV
> only allows single line values, that's why I excluded the text field from the
> CSV export. This is different in the XML export, which supports multi-line
> values. If you teach me however how multi-line values can be represented in
> CSV format, I could easily add that.
> 
> As for the attachment, do you just need a name, or a URL back to the logbook?
> Should the pointer be in the form "http://elog.server/logbook/attachment.jpg"
> or in HTML form like <a href="http:/...">attachment</a> ?

I will attempt to use an active x script in a DTS package on SQL Server to parse
the xml and load it into the database. I can see where CSV has it's limitations.

> Is there any way to include the text of a log message in the CSV export? 
> Anyway to include a pointer to the attachment?

The text of a log message is usually several lines long. To my knowledge, CSV
only allows single line values, that's why I excluded the text field from the
CSV export. This is different in the XML export, which supports multi-line
values. If you teach me however how multi-line values can be represented in
CSV format, I could easily add that.

As for the attachment, do you just need a name, or a URL back to the logbook?
Should the pointer be in the form "http://elog.server/logbook/attachment.jpg"
or in HTML form like <a href="http:/...">attachment</a> ?

Is there any way to include the text of a log message in the CSV export? 
Anyway to include a pointer to the attachment?