(anonymous guest) (logged out)

Copyright (C) by the contributors. Some rights reserved, license BY-SA.

Sponsored by the Wiki Symposium and the Nuveon GmbH.

This is version . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Welcome to Creole, we are glad you are with us.

Your comments on quotes are very helpful, I didn't know about that mozilla guidelines. Seems like you have some very good ideas.

I'm impressed with your parser, it can even handle things like //italic **bold italic// bold**// and generate proper html for them!

However, it behaes weird on this input:


-- RadomirDopieralski, 2006-09-24

Thanks a lot for your help, Radomir. I worked on the problem of newlines in links and it should be fixed now.

About the parser: large part of the code is taken from Text_Wiki, so its developers are the people who deserve your compliments. But... thanks! ;)

Seems something has changed for the worse as //italic **bold italic// bold**// produces <p><em>italic <strong>bold italic</em> bold</strong>//</p>.

-- Jared Williams, 2006-09-25

You're right, Jared, the parser is not yet so smart to avoid this kind of crossing elements. This could also involve links. Radomir, I suspect you used "View selection source" in Firefox... Is it possible?

These cases cannot be easily recognised in Text_Wiki using regular expressions. The only solution I can imagine is counting the tags (actually 'tokens' generated by previous rules) inside the body of a new found element, to avoid encapsulating a single opening or closing tag. Any suggestion?

I've added a check on the the inner tags. At least the generated HTML is standard compliant, now, even if in convoluted texts some possible elements could be missed by the parser.

Thanks everybody for helping and finding bugs. Be patient as it's an early release.

Add new attachment

Only authorized users are allowed to upload new attachments.

« This particular version was published on 25-Sep-2006 10:54 by MicheleTomaiuolo.