#495440 ELinks removes newlines when editing a DokuWiki page

Package:
elinks
Source:
elinks
Description:
advanced text-mode WWW browser
Submitter:
Norbert Tretkowski
Date:
2023-04-19 23:18:03 UTC
Severity:
normal
Tags:
#495440#5
Date:
2003-09-18 19:55:06 UTC
From:
To:
I guess there are <pre></pre> tags missing around those.

(Let the web interface show the log file to see the problem)

#495440#10
Date:
2003-09-18 21:34:01 UTC
From:
To:
Jürgen A. Erhard wrote:

When you click on 'LOG file' to see /var/lib/backuppc/log/LOG ?

All my log files are properly shown on my backuppc...(and with pre
tags...)
(URL used: http://localhost/backuppc/index.cgi?action=view&type=LOG )

Cheers,

  Ludo

#495440#15
Date:
2004-06-03 19:22:39 UTC
From:
To:
-------- Original Message --------
Subject: Re: Bug#211588: backuppc: all the ASCII files being displayed are one
*long* line
Date: Sat, 20 Sep 2003 01:45:17 +0200
From: "Jürgen A. Erhard" <jae+debian@jerhard.org>
To: Ludovic Drolez <ldrolez@debian.org>
References: <20030918195506.GA6453@sanctum.jerhard.org>
<3F6A24C9.6000206@debian.org>
over to elinks.

Bye, J

PS: elinks doesn't know what to do with the 
 it sees in the
<pre>-tagged part.  Since <pre> contains PCDATA, it should be parsed and,
presumably, acted upon.

Actually, backuppc could easily fix this by not escaping newlines; it
currently escapes *any* nonprintable char in EscHTML.

#495440#22
Date:
2005-05-23 09:26:01 UTC
From:
To:
I have a similar problem with dokuwiki. When editing and saving a
site, all newlines getting removed.

The result is completely unusable.

Regards, Norbert

#495440#27
Date:
2006-12-20 22:15:42 UTC
From:
To:
Ludovic Drolez <ldrolez@debian.org> writes:

This seems to be ELinks bug 52, which was fixed on 2004-06-24.
Because ELinks 0.10.0 was released on 2004-12-24, I assume it
includes the fix.  However, that fix recognizes only 
 and

 (case insensitive).  I do not know whether this suffices
for backuppc.

A separate bug 387 was later entered about supporting also other
syntaxes like the 
 used by Bugzilla.  That bug has been
fixed in ELinks 0.12.GIT.

Norbert Tretkowski <tretkowski@inittab.de> writes:

ELinks bugs 52 and 387 are specifically about <pre>...</pre>.
If you have similar problems with a textarea, that may be bug 876.


Bug 52 - Problems w/ handling of 
 in <pre>
Bug 387 - Character sequence 
 should cause newline.
Bug 876 - 
 in textarea should display a line break

#495440#34
Date:
2008-01-13 21:40:01 UTC
From:
To:
Version: 0.10.2-1

Closing as such. Please reopen if the bug if you run into this again.

Cheers,
        Moritz

#495440#45
Date:
2008-08-17 13:05:09 UTC
From:
To:
Norbert Tretkowski <tretkowski@inittab.de> writes:

Our upstream ELinks 0.12.GIT still seems to have this bug, even
though http://bugzilla.elinks.cz/show_bug.cgi?id=876 was already
fixed and mostly tested.  I have now split your bug report from
the original one, which was about 
 in PRE elements and was
fixed earlier.

#495440#50
Date:
2023-04-19 23:08:04 UTC
From:
To:
Could you ttest if this problem still persists in elinks 0.13.1 ?