Received: by 10.180.97.162 with SMTP id eb2mr686916wib.0.1352477697846;
        Fri, 09 Nov 2012 08:14:57 -0800 (PST)
X-BeenThere: pylons-discuss@googlegroups.com
Received: by 10.180.90.134 with SMTP id bw6ls1378275wib.1.canary; Fri, 09 Nov
 2012 08:14:34 -0800 (PST)
Received: by 10.180.96.6 with SMTP id do6mr685320wib.1.1352477674609;
        Fri, 09 Nov 2012 08:14:34 -0800 (PST)
Received: by 10.216.199.17 with SMTP id w17mswen;
        Fri, 9 Nov 2012 02:59:11 -0800 (PST)
Received: by 10.181.13.75 with SMTP id ew11mr309136wid.0.1352458751011;
        Fri, 09 Nov 2012 02:59:11 -0800 (PST)
Received: by 10.181.13.75 with SMTP id ew11mr309135wid.0.1352458751001;
        Fri, 09 Nov 2012 02:59:11 -0800 (PST)
Return-Path: <ldave...@gmail.com>
Received: from arnac.cri.ensmp.fr (service.cri.ensmp.fr. [86.65.170.33])
        by gmr-mx.google.com with ESMTP id cn9si100473wib.0.2012.11.09.02.59.10;
        Fri, 09 Nov 2012 02:59:10 -0800 (PST)
Received-SPF: neutral (google.com: 86.65.170.33 is neither permitted nor denied by domain of ldave...@gmail.com) client-ip=86.65.170.33;
Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 86.65.170.33 is neither permitted nor denied by domain of ldave...@gmail.com) smtp.mail=ldave...@gmail.com
Received: from vialfre.cri.ensmp.fr (vialfre.cri.ensmp.fr [10.2.14.11])
	by arnac.cri.ensmp.fr (Postfix) with ESMTP id D20862001EB;
	Fri,  9 Nov 2012 11:59:10 +0100 (CET)
Message-ID: <509CE1FF.2020109@gmail.com>
Date: Fri, 09 Nov 2012 11:59:11 +0100
From: Laurent DAVERIO <ldave...@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: pylons-discuss@googlegroups.com
CC: Jonathan Vanasco <jonat...@findmeon.com>
Subject: Re: recommend a wysiwyg editor for a pyramid project?
References: <509AD019.2010706@simplistix.co.uk> <CAAPh5Fn7r4HbFOGLTLPi3+R9C4bCi+Z7J7QDc99oh7p=f-rtLA@mail.gmail.com> <509B8CD1.1000201@simplistix.co.uk> <d1a659a5-fbd4-4e36-8a92-0daebde619ec@googlegroups.com>
In-Reply-To: <d1a659a5-fbd4-4e36-8a92-0daebde619ec@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

> - As much as you can , don't allow consumer HTML
> - I really suggest forcing everything into Markdown or similar in the
> backend, then generating into HTML as needed.  

I humbly disagree. In many companies, you'll see people elaborate
rich-text content in MS Word, and then copy and paste it into a content
management system (I develop and maintain a couple of Zope/CMF/Plone
corporate intranet websites, and I see this happening all the time).

If you don't allow HTML and impose wiki-style formatting instead, many
non-technical people will complain about the change, and rightly so...

My 2 cents...

Laurent.