Re: [Issue 200] Convert spaces to tabs

Yeah. That's what it does. Any wierd processing of stuff within <noop></noop> is due entirely to the HTML processor (browser) and it's interpretation of your code.

Please can we address the issue's text, which asks for a conversion facility.

Again, I'm glad to make the processing an active part of coWiki parsing, taking tab processing out of the preamble, thus allowing tabs to be regurgitated by reverse parsing, if that's what is intended.

Otherwise, I'll ask again: please can we act on this issue. (close it!)

Regards,

Archie

Daniel T. Gorski wrote:

On 22 Jun 10:25, PAUL HANCHETT wrote:

  

What is <noop> defined to *do*? 
    

<noop> was defined to do what it says: "no operation" while parsing the text...

Each character or any text enclosed in <noop>..</noop> was ment to be
completely ignored by the parser, even if its a part of the coWiki syntax.
Hence the first task for the parser to do, is (was?) to filter anything
between this directives and replace it originally after any other markup has
been processed.