Re: [cowiki-dev] Extension to coWiki text formatting

PAUL HANCHETT wrote:

>> Re bug #195, WikiParser accepting <u>, <i>, <b>... I could fix a 
>> scheme for user-defined attributes in the output HTML, such that <u 
>> origin="wiki"> back-parses to "__" and <u origin="html"> back-parses 
>> to "<u>". Any takers? Comments on expanding this? Put downs?
>
> I can't think of a probem with it...  I haven't looked at the code 
> handling this, my off-the-top-of-my-head fear was that a new tag was 
> needed to represent every formatting source.  I see now that is not 
> necessary.  The light bounces back and forth inside my management-type 
> head!  :-)

I'll put in origin code for emphasis, that's bold, italic, underline, 
strikeout and fixed. It's a natty little fix, and might please some people.

>> What is the consensus on <p>-aragraphs? The parsers, together, seem 
>> [sic] to like putting everything on one line unless broken by <br/>. 
>> This is true-to-html behaviour. Thing is, I could be slotting 
>> <p>...</p> around these lines without much effort. I'm thinking of 
>> somebody's future javascript, where the <p></p> is the only 
>> containing element we have, except for a <div> within which 
>> justification takes place. Comment?
>
> Are you talking about internal representation, what we display back to 
> the user when they edit, or the html output?
>
> In Wiki-text, the end of line, in a non-blank line, is a paragraph 
> break.  Multiple empty lines produce no output and silently disappear 
> from the page text.

I'm talking about internal xml. If the end-of-line to paragraph-break is 
your understanding of wiki-text, O fearless leader, then I'll put 
<p></p> around those virtual lines. No worries.

>> If you like, I'll commit to cvs, but I don't want to break the HEAD 
>> again.
>
Haven't the guts to do this, yet. Cometh thursday and the looked-for 
feedback...:-)

My HEAD-tree is probably bogged down in stickiness, but for now tigris 
is timing out...:-(

Regards,

Archie