# Koradhil :
Considering all opinions and preferences, I'm convinced we should go for a multi-parser solution. My design would include the following:
- Multi parser, both BBcode and HTML
- BBcode gets smart paragraphs instead of nl2br
- HTML is cleaned using HTMLPurifier (upon submission)
- We use two of the extra rights fields (the hidden ones) to configure which usergroup can use which parser (i.e. both HTML and BBcode for moderators and up) for each site area/plugin. Alternatively we add 2 custom fields.
- We use only one field for the text (BBcode or HTML), but use another to store which parser is applicable. This keeps redundancy to a minimum.
- All editors (Markitup, TinyMCE, CKeditor) are configured as plugins. Which two will be included in the Cotonti package (if any) is yet to be defined.
Good point technically. Though, we won't drop page_html for bbcodes because it really makes the site faster. As for permissions, better use appropriate plugin permissions rather than extras. What I'm worried about is:
- It's hard to add optional fields to BBcodes, so improving SEO in bbcodes is a tricky thing
- For such things like PFS it will require to support multiple parsers too, when inserting thumbs, file links, icons, etc.
- There are more fields with parsing potentially enabled rather than just page_text. For pages it could be also page_desc, page_preview. Forum section descriptions would need markup too. Setting different parsers to each of them would be a waste.
