Actually I think you are closer to the wiki-creole standard than BoltWire on this point, which requires // to generate a line break. Which I take it is what you are saying. But I made a deliberate decision to go a more intuitive, blog-like direction and have line breaks in source produce line breaks in html. I want as close to a cut and paste kind of ability from a text document to html. And I do not want to lose that capability. I should note even at wiki-creole this issue was hotly contested, and the community there was split close to 50/50. It was also not part of the original wiki-creole standard--which was more aligned with BoltWire's present position.
You are of course welcome to develop an alternate approach. You would only have to rewrite the last two markup rules to something more suited to you. You should find it much easier code wise to eliminate intuitive line spacing than getting it to work--which has been quite difficult all along. And is still not perfected. It has however, not only been a perennial challenge, but a perennial goal in BoltWire. As for your comment about including some page, you are correct. This does not work perfectly because the included content is escaped and not injected into the page as multiple lines. It can be corrected in one of two ways: 1) add a ` after the function to escape the next line break. This generates proper html. or 2) some how rewrite the page generation routine so that everything is unescaped before the line spacing is added. ideally by moving it into the domarkup function rather than a separate markup rule. Actually, this last suggestion might be the best solution. But it would take some tinkering, and I'm not sure when I'll have the time to dig into this. As mentioned above, getting intuitive line spacing to work is not easy. But I plan to continue pursuing it. Cheers, Dan On Mon, Oct 5, 2009 at 10:16 AM, blues <[email protected]> wrote: > > On Oct 5, 4:58 pm, The Editor <[email protected]> wrote: >> I'm glad the rules explain things. But I disagree that it is >> "obviously" incorrect. The example above does not at all look like two >> paragraphs to me. > > either they are two paragraphs, either they are five (following your > way of thinking). i don't understand why only "third line" should be > enclosed in <p>. > i agree that it follows the markup rules you set, but the rules > themselves may just be wrong. > > >> As paragraphs do not have line breaks in them. > > as i said in the previous post, in html, <br/> does NOT break the > paragraph. and since we are trying to render html here, i find this > behavior wrong. > there is a specification to follow, and the current way does not do > it. > > blues > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" 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/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
