On Tue, 2007-28-08 at 19:30 +0100, Paul Johnston wrote: > Hi, > > >How do you find using Textile as compared to using something like > >TinyMCE? I'm trying to find one optimal solution that will do for most > >of my custom cms cases to make sure users can enter formatted text some > >of the time but absolutely can't break their site with malformed xhtml. > >I would prefer to err on the side of slightly inconvenient and > >unbreakable. > > > > > In my environment it works well, I've only got a small number of people > using Textile - 4-5 techies, who I all work closely with. I wouldn't > want to roll this out to less techie people. > > Textile can produce invalid HTML, I found at least one string that did > this. Fixing it did not look easy, and the author was unresponsive. > > Thinking about your situation, I reckon you're probably best sticking > with TinyMCE, and adding some validation. Use ElementTree (or anything) > to validate what you receive is valid XML. Ok, that's not an easy error > for the user to cope with, but at least it's better than their site > randomly breaking.
I'm tending to agree. I figure if they want to enter html, they should be able to look up the syntax ok. I think I'd rather stop bad input before it gets in at all. What settings do you use for your template serializer when doing it that way? Thanks iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
