FWIW here a nodelet hack which opens a JS.alert() with the HTML of the post you are trying to reply to.

<script><!--
function show_quote() {
alert(document.querySelector("div.preview").innerHTML.match(/^[^]*?(?=
+<hr> <div class="editnodetext">)/)[0]);
}
--></script>

<a href='javascript:show_quote()'> show_quote</a>
[download]

(you need to be in a "comment on" node to make it work)

it was part of my plans to extend my wiki-syntax with comfortable quoting of a users post...

... of course milking the XML-displaytype would be more reasonable here.

... it's very close but that's not the raw input of the poster.

For instance [links] are expanded and code tags have an extra download link.

huck:

Thanks, but that still has the HTML entities encoding and bracket ([ ]) munging.

...roboticus

When your only tool is a hammer, all problems look like your thumb.

How raw can we get?

lynx -dump http://perlmonks.org > dump.txt

Lynx?

Best regards, Karl

«The Crux of the Biscuit is the Apostrophe»

perl -MCrypt::CBC -E 'say Crypt::CBC->new(-key=>'kgb',-cipher=>"Blowfish")->decrypt_hex($ENV{KARL});'Help

I think you are missing the point, compare the data inside the xml link with the produced html.

For instance you can see find* the original line breaks and indentation in the raw form if a poster forgets surrounding code tags

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!}

*) The xml view inside FF doesn't display the (included) line-breaks, but if one's copy the content to an editor it becomes visible again.