Consider the following commands, and their results :
$ echo "<br/> <br/>a<br/>b<br/>c<br/><br/> <br/>"|lynx -dump -stdin a b c $ echo "<br/> <br/>a<br/>b<br/>c<br/><br/> <br/>"|elinks -dump a b c
Neither prints the correct number of lines :
elinks skips the first white space, and both skip blank lines and trailing lines with white space only.
Is there a way to force
elinks to interpret all spaces and line breaks ? I didn't see anything obvious in their manpage.
(I mean, beside using a temporary character to be suppressed by
tr or whatever after the display.)