default_output/content_type for RichText in ArchGenXML

Maurits van Rees <m.van.rees-1kr/[email protected]> Wed, 14 Jun 2006 16:57:48 +0000 (UTC)
Newsgroups gmane.comp.web.zope.plone.archetypes.devel
Message-ID <[email protected]>
Hi,

According to
http://plone.org/documentation/tutorial/archgenxml-getting-started/archgenxmlquickref
the default_output_type for a RichText field is 'text/html'.  The
default_content_type is not mentioned there.  That probably means it
is 'text/plain'.

In Archetypes/Field.py the default_content_type and
default_output_type are both 'text/plain'.

Wouldn't it make more sense for ArchGenXML to also have 'text/plain'
as default_output_type or at least to have the *same* default type for
both?

The problem is that currently with my own product (the
eXtremeManagement tool) when I fill in a rich text field the drop down
box shows I am adding text/plain, but after saving I see literal html
codes on the page, like "<br />".  That happens when I just add a few
random characters and some newlines.  When I set the
default_output_type to 'text/plain' in the code everything goes as
expected.

So would it make sense to change ArchGenXML here?  Or should I change
something in my code?

I'm using FCKEditor; might that be the culprit here?  I tried kupu
just now, but that only gives you the 'text/html' option, so it
doesn't give you the chance to mess it up. :)

-- 
Maurits van Rees | http://maurits.vanrees.org/ [NL]
            Work | http://zestsoftware.nl/
       GnuPG key | http://maurits.vanrees.org/var/gpgkey.asc
"Do only what only you can do." --- Edsger Wybe Dijkstra