• Have a default switch for the Encoding. So if "default encoding = plain", the "plain" radio button is on by default, so people tend to write plain text rather than ELCoded text.
  
• Have either a switch for the email notification, to revert back to the old text format, or have a multipart email message. I saw that outlook sometime does that. One email can contain a "plain" part and an "HTML" part. So you can select in your email reader which one to display. At least thunderbird supports that. But I don't know what your bash scripts say to that, please let me know.
  

> Hi, 
> 
> I am playing with the elog automatic subscription script, but somehow I am failing in submitting an entry. 
> I am using a syntax as this:
> 
> echo test | elog -h 127.0.0.1 -p 8085 -d /usr/local/elogbooks/Elog -l "Sub Elog" -a "Type=MyType" -x -u user passwd
> 
> and I get a message which says: 
> "cannot get host name: Success"
> 
> which seems contradictory and also there is no entry submitted. 
> 
> The command is executed on the host where the elog is running, the port and directory are taken from the cfg File. 
> 
> What is my mistake, where is my misunderstanding of the documentation?
> 
> Any hints appreciated. 
> 
> Erik

The "-d" option is certainly wrong. This is only used when running elog under Apache. But otherwise it should work. I 
tried it myself and it went fine. Try to add a "-v" flag to see verbose output.

> If I create an entry via the web-interface, the defined encoding of the browser is used.
> If I create an entry via "elog", it is always stored in UTF-8 encoding.
> For the text I can overcome that with HTML encoding, but for attribute values the encoding does not show properly.
> The only solution I found was to convert the whole logbook to UTF-8 encoding:
> 
>  define "charset=UTF-8" in elogd.cfg
>  iconv --from-code=ISO-8859-1 --to-code=UTF-8 elogd.cfg >tmp;mv tmp elogd.cfg
>  iconv --from-code=ISO-8859-1 --to-code=UTF-8 resources/eloglang.german >tmp;mv tmp resources/eloglang.german
> 
> Has anyone any idea why ISO8859-1 does not work for me?
> 
> Or can anyone advice me of an editor similar to NEdit that is capable to display UTF-8? :-)

I just tried it submitting to the Demo logbook:

https://midas.psi.ch/elogs/Linux+Demo/15

using some German Umlauts, and saw that it works fine. "elog" does not do any conversion, just submits the text as is. 
If your text is ISO-8859-1 encoded, it will be submitted as such, and your browser will correctly display it. Have you 
tried removing the "charset=UTF-8" from your elogd.cfg?

The "elog" client does unfortunately not support proxies. You could however achieve the same with the "curl" tool. Have a look at elog:68597

Stefan

Hey,

I think this is a "problem" of the elog client, since it simply replaces the data. In most cases this is what you want, but since I wanted to have the option to append to the acutal message I built a function to first read-back the entry and add to the message instead of replacing it.

I just played around a bit and found that the attachments will be even disconnected, if you do not specify the -f parameter but just edit a different part of this entry.

A work-around for this is tricky. I tried to write to the "Attachment" attribute directly (-a "Attachment=Filename'), since then you coud read back the data first and manually add the filenames again. But this does not work.

Since the attachments are not actually removed, the only option I see is to modify the logbook file entry on the server by manually re-adding the filenames to the "Attachment: " line. But 

Hey,

I think this is a "problem" of the elog client, since it simply replaces the data. In most cases this is what you want, but since I wanted to have the option to append to the acutal message I built a function to first read-back the entry and add to the message instead of replacing it.

I just played around a bit and found that the attachments will be even disconnected, if you do not specify the -f parameter but just edit a different part of this entry.

A work-around for this is tricky. I tried to write to the "Attachment" attribute directly (-a "Attachment=Filename'), since then you coud read back the data first and manually add the filenames again. But this does not work.

Since the attachments are not actually removed, the only option I see is to modify the logbook file entry on the server by manually re-adding the filenames to the "Attachment: " line.