Minor changes you do externally to the elogd.cfg file are reflected immediately under Windows (under Linux you have to send a HUP signal to the process to re-read the configuration). But if you make major changes like adding a new logbook, you have to restart elogd. 

 Let me report when I see this behaviour.

If I use a text editor on elog.cfg directly, while elog is running, then when I save the file, the new elog.cfg is in place,

but the running elog is still running with the old configuration.  You have to restart elog for it to read the new config file and

use the new settings.

This does not apply if you edit elog.cfg via the "config" option in the menu command, where elog will read the new elog.cfg

just after it has been saved.

The reason I sometimes edit the file directly is if I want to create a new logbook, but with all the configuration of another logbook,

and it's quickest to cut-and-paste,  change the heading, create a new directory and restart elog.

This may be completely off what is being reported.

>- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?

I change the configuration directly on elogd.cfg, (after i save and update my web page, and i not modification immediately)

>- Some write protection of elogd.cfg

no

- Do you have more than one server running at the same time and changing the wrong one's config?

i have one server with elog

Not really, you are the first one reporting this issue. Just some thoughts:

- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?

- Some write protection of elogd.cfg

- Do you have more than one server running at the same time and changing the wrong one's config?

- Stefan 

hello,

At home, when I change the config *. cfg, the modifications are not taken in consideration

Have you got a idea ?

Thanks a lot !

Bob

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

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 installed 2.81 (Elog-latest) but this Version did not work. I got Error 193: %1 is not a valid Win32 Application as I tried to start the service. So i will sent you the complete elogd.cfg via Mail.

Best regards

Michael