yeah, I wouldn't want the h1-based thing. The standard way is to only
denote prose paragraphs with P's.

I'm thinking of something like a large regex accepting all text
without "block" "sectional" "table" or "list-like" markup... well that
and completely empty/whitespace lines. Then define it as an element
'p'.  I see where the complexity comes in though.

When the parser is going through the text, does it search for all
matches of config.formatters[0] and replace text with the html tags,
then search the text (now with some tags) for all matches of
config.formatters[1]? I'm curious about how nesting/greediness are
handled.

On Thu, Oct 7, 2010 at 1:25 PM, PMario <[email protected]> wrote:
> Hi David
> I think it is not that easy.
> If you have a look at a "standard" html page it may look like this for
> a "section"
> <h1>header</h1>
> <p>some more text<br />
> second line
> </p>
>
> and not
>
> <p>
> <h1></h1>
> </p>
>
> But as FND sayd "you can pretty much do whatever you
> please."
>
> -m
> On Oct 7, 5:13 pm, David Young <[email protected]> wrote:
>> I see. old 'bug'.  Would there be a technical breakage if I were to
>> add a few paragraph parsers for my plugin?  Since I'm writing a new
>> parser, I have little concern for backwards compatability.  The
>> example I'm starting with seems to throw <p> tags around when making
>> new !sections (or, in the example formatter's case, new =sections= but
>> they're both h1's).  Maybe I can adapt this a bit.
>>
>> http://www.martinswiki.com/%23ExampleFormatterPlugin&usg=AFQjCNHoSIQg...
>>
>>
>>
>> On Thu, Oct 7, 2010 at 11:03 AM, FND <[email protected]> wrote:
>> >> tiddlers output <br>s where one would expect <p>'s [...]
>> >> Is there a reason for this implementation?
>>
>> > The reasons for this are historic - unfortunately, it doesn't seem like
>> > we can change this now without breaking backwards compatibility:
>> >http://trac.tiddlywiki.org/ticket/34
>>
>> > -- F.
>>
>> > --
>> > You received this message because you are subscribed to the Google Groups 
>> > "TiddlyWikiDev" group.
>> > To post to this group, send email to [email protected].
>> > To unsubscribe from this group, send email to 
>> > [email protected].
>> > For more options, visit this group 
>> > athttp://groups.google.com/group/tiddlywikidev?hl=en.
>>
>> --
>> David Young
>
> --
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWikiDev" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/tiddlywikidev?hl=en.
>
>



-- 
David Young

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/tiddlywikidev?hl=en.

Reply via email to