[opencms-dev] Accented & Special Characters in WYSIWYG Editor

Alexander Kandzior alex at opencms.org
Thu Jun 24 09:44:01 CEST 2004


Kevin,

the eoncoding issues in the WSIWYG should be gone in OpenCms 5.3.5, the
latest milestone build already avaliable from CVS.

Best Regards,
Alex.

Alexander Kandzior
Alkacon Software - The OpenCms Experts
http://www.alkacon.com 

> -----Original Message-----
> From: opencms-dev-admin at opencms.org 
> [mailto:opencms-dev-admin at opencms.org] On Behalf Of kevin fong
> Sent: Thursday, June 24, 2004 6:23 AM
> To: opencms-dev at opencms.org
> Subject: [opencms-dev] Accented & Special Characters in WYSIWYG Editor
> 
> 
> Hi all,
> 
> Whilst using the WYSIWYG MSHTML editor to edit pages, I 
> realised that accented characters like "ë" become malformed 
> after the page is saved. By changing the following  file 
> /system/workplace/skins/modern/editors/msdhtml/scripts/edithtm
> l.js : 
> ==============================================================
> ==================
> function saveContent() {
> 	var _form = document.EDITOR;
> 	var _editor = _form.EDIT_HTML;
> 	var content_to_save = "";
> 	if (_editor.DOM.documentElement) {		
> 
> // FROM:  _form.content.value = 
> encodeURIComponent(_editor.filterSourceCode(_editor.DocumentHTML));
> 
> 		_form.content.value = 
> _editor.filterSourceCode(_editor.DocumentHTML); 	//CHANGED TO
> 
> 	} else {
> 		// IE4
> 		_form.content.value = 
> encodeURIComponent(_editor.DocumentHTML);
> 	}
> }
> 
> ==============================================================
> ==================
> 
> By excluding encodeURIComponent, it fixes "malformation" 
> problem with accented characters but creates other encoding 
> exceptions when content that needs 
> to be converted by encodeURIComponent does not get encoded 
> properly(because the method is now excluded).  Sort of a 
> catch 22 situation here and would most appreciate any advice 
> on this matter especially from the experts out there who 
> content manage websites that uses languages that have 
> accented characters.
> 
> The workaround solution is to use the source code editor to 
> use the html encodings "&eactute;" but my end users are not 
> familiar with html and this does not serve as an acceptable 
> solution for them. _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, 
> please visit http://mail.opencms.org/mailman/listinfo/opencms-dev
> 
> 
> 




More information about the opencms-dev mailing list