UPDATE:

After days of head banging and trying different syntax combinations, I finally stumbled on my own answer. It involved some syntax adjustments, and then splitting the task into these two consecutive operations:

      1. wget --no-check-certificate --cookies=on --save-cookies cookies.txt --keep-session-cookies -O e:\export1.csv "http://localhost:8080/demo/?uname=agrant&upassword=skipper"

      2. wget --no-check-certificate --cookies=on --load-cookies cookies.txt --keep-session-cookies -O e:\export2.csv http://localhost:8080/demo/?mode=CSV1

All is working fine now.

> We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> entries made during the shift and files the printouts. If one entry in the shift was plain text without
> appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> very tiny scale, which makes it unreadable.
> 
> Is there a way to enforce line breaks in plain text entries?

Obviously there is: this logbook does add line breaks?!?

Maybe it is only a problem with entries made by the "elog" command?
I'll find it out and re-post.

Cheers
Andreas

> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> > width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> > very tiny scale, which makes it unreadable.
> > 
> > Is there a way to enforce line breaks in plain text entries?
> 
> Obviously there is: this logbook does add line breaks?!?
> 
> Maybe it is only a problem with entries made by the "elog" command?
> I'll find it out and re-post.
> 
> Cheers
> Andreas

Okay, I found two ways to add very long lines:
- if the very long line does not contain a space then this will screw the printout.
- if the line has been added as plain text using the elog command, there will be no line breaks added.

It would be nice if the elog command would have an option to break lines to a maximum line length.
But for the moment I'll just modify the applications that make use of the elog command.

> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> > width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> > very tiny scale, which makes it unreadable.
> > 
> > Is there a way to enforce line breaks in plain text entries?
> 
> Obviously there is: this logbook does add line breaks?!?
> 
> Maybe it is only a problem with entries made by the "elog" command?
> I'll find it out and re-post.
> 
> Cheers
> Andreas

Yepp, this is a (missing) feature of the elog command. Can you pre-process your messages outside of it, or do I have to add code to elog to do that?

Stefan

This may be due to how I have my config file setup

Example:

Attributes = A, B
Options B = Please Select A
Options A = One{1}, Two{2}
{1} Options B = 1, 2,
{2} Options B = 3, 4,
 

Deleting a logbook in the config page (via "Delete this logbook") only removes the logbook defiition from the config file. To really erase all information you have to go to the file system and delete the whole directory belonging to that logbook. You have one subdirectory per year, containing all logobok entries and also attachments, so make sure you do a recursiver directory removal.

Stefan

Stefan,

Thank you that is exactly what I needed to know.

Steve

Uppon closer inspection, removing the option to preset the secondary attribute as a Option list dosn't do anything for the find page.

This:

Attributes = A, B
Options A = One{1}, Two{2}
{1} Options B = 1, 2
{2} Options B = 3, 4

Still fails to set attribute B to a option list on  the find page.