Hi,

I had similar needs (access and parse logs ) so I'm  a small library in cpp. Have a look on https://github.com/flagarde/elogpp maybe it could be usefull for you too.

Stefan,

When will you have 2.3.1 out? I just upgraded to 2.3.0 and would like to see
the links in my summary view. If it is going to be out soon I will wait
instead of compiling from source.

Thanks for great software,
k.

> > Would be nice if you can specify which columns data has links as a flag or 
> > setting of some sorts, as opposed to either the first or all, but given a 
> > choice I would want the first column to be the linkable one 
> 
> Well, I decided to make all entries in a table a link, to be consistent with 
> the threaded display. But I changed the style such that they look like 
> before, but are actually links. This way it cannot hurt (like having too 
> much underlined text). The style can be changed via classes ".list1" 
> and ".list2" in the style sheet.
> 
> The modification will come in 2.3.1, or you can get the source code from CVS 
> under 
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c
> 
> and
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/themes/default/default.css
> 
> > > > Problem 2 - no matter what i try in the config file i cannot get elogd 
> to 
> > > > use stylesheets ive tried specifying and even editing and removing the 
> > > > default.css style sheet i downloaded but it just seems to ignore its 
> > there.
> > 
> > I resolved this problem, many thanks for your help
> 
> What happened. If you tell your initial problems, I can maybe put something 
> into the docs so that others won't have it...
> 
> - Stefan

I would like to dump mylog files into comma/tab seperated files. Is there 
an easy way to do it?

I tried to run elconv, but had no success. Always returns an error. 

Thanks,
k. 

Hi,

"Default encoding" appears to have the default value of 2 (HTML) instead of 0 (ELCode) as documented in http://midas.psi.ch/elog/config.html

ELOG V2.7.0-1954 : elog.c line 8952

Kristján

Do I have to do any extra configuration in elog to enable the FCKeditor.

What I get with V2.7.0-1954 is that the main message entry field looks and behaves identically whether I set the encoding to HTML or plain (except the width and height of the field changes).

ELCode works as expected.  Message files saved with the encoding set to HTML have a line "Encoding: HTML", but no HTML markup.  Those saved with encoding set to plain have the line "Encoding: plain", but are otherwise identical.

I have the scripts directory as set up by "make install" containing the elcode.js file and the fckeditor subdirectory.  All are world readable.

Any hints about what could be the problem?

Thanks

Kristján

Excellent, works as expected now, thanks.

Didn't realise how far behind the SVN version elog-latest.tar.gz is.

I'm running a Debian package of elog with verision number 2.5.4+r1480-1. 
The revision of the elog client in this package is 1.21. 

I'm using the elog client to send entries generated by a script to my
logbook.  I want to format the body text of the entry using HTML, to include
links and images.  When I submit the entry with the elog client it is
submited as text and not HTML.  

The man page for the elog client does not mention any commandline options to
specify the formating of the entry and I have not found any info in this
forum on the issue.

Is it possible to submit an entry with a html body using the elog client?