[TYPO3-RTE] problems understanding configuration of htmlarea rte

Simon Harhues Simon.Harhues at muenster.de
Sat Nov 8 03:46:14 CET 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Stanislas,

thanks for your help!

Stanislas Rolland schrieb:
>> Now i and b tags stay in source code but don't get remapped to em and
>> strong tags on saving.
> I would think that they are. Did you check in the database? How do they
> show in the frontend?
You're right. In the FE and DB they are correct remapped and saved as
strong and em. I just looked in the rte, where they nevertheless are
still shown as b and i. Didn't know, that the appearance in rte won't
change...
> 
> If you did not enable the configuration variable "Enable additional
> inline elements" in the Extension Manager, then you are using an old
> backward compatibility mode. In this mode, IE supports only b and i.
> Therefore, if you are using IE, strong and em are converted to b and i
> for the time they reside in IE..., but converted back on the way to the
> database.
I didn't activate that option, but I have to say I'm not using IE but
Firefox 3.0.3. So maybe also Firefox has some problems with the
compatibility mode?
Well, because in productive use later on we will use IE7 I've activated
the configurations variable "Enable additional inline elements" now
(didn't know about it's use before). And now my Firefox shows strong and
em also correctly in rte. I'll check the whole stuff in IE
tomorrow/later. Does this configuration variable produce any other side
effects?

Regards,
Simon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJFP12zqmr83R5SCwRAlVAAJ0fM1PMbPqpFIu6LDiKeQZAIP/mpwCgi1Ts
bPXPXsuFBtpnwdpFjC0lSew=
=V0gt
-----END PGP SIGNATURE-----


More information about the TYPO3-project-rte mailing list