corrected file is attached

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

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

Dear ELOG users,

this is to announce an important security update. As proposed by Lukasz Olejnik (CERN/PSNC), ELOG has now switched to strong encryption of password. So everybody concerned in security is advised to update to the new version 2.8.0. Existing password files for Windows users and Linux users not using HAVE_CRYPT are automatically converted. Those installations which used HAVE_CRYPT in the past under Linux have to ask their users to re-enter their password (via the link "Forgot password") after the upgrade to version 2.8.0.

Best regards,

  Stefan Ritt

Hi, I rsync an elog database from CERN to TRIUMF every few months and I notice that rsync keeps copying preview files (xxx.png.png, xxx.gif.png, etc) from very old entries. I guess that elogd creates these files from scratch each time they are needed, overwriting any previously existing preview files. This creates extra rsync network traffic and rsync takes longer to complete. Is there any way to avoid this? K.O.

I just realized that the command line elog utility did not yet use the new encryption. So automatic elog submissions using passwords are broken in version 2.8.0. I made an intermediate version 2.8.0-2 which fixes that. However you only need to update it if you use the elog utility and have problems with the 2.8.0 version.