Support forums » Products » Cute Editor for ASP » Re: HTML entities in CuteEditor 6.0

HTML entities in CuteEditor 6.0

Last post 10-19-2007, 2:16 PM by MansonServices. 2 replies.
Sort Posts: Previous Next

  •  08-03-2007, 2:44 PM 32157

    HTML entities in CuteEditor 6.0

    Reply Quote
    The upgrade is great -- we're seeing much faster load times.  But now we're having trouble with HTML entities, Unicode, greek letters, etc. 
     
    We enter & # 9 4 6 ;   (no spaces) into the HTML view, then switch back to normal view.  The lowercase beta (β) displays fine.  Click HTML view again, there's the beta but no more & # 9 4 6;.  After the beta gets saved to SQL and served elsewhere in the application, it comes out garbled.
     
    I would like CuteEditor to conserve the & # 9 4 6; and not translate it into a character that SQL can't handle.  Any ideas?
     
    This was never an issue in 5.0, but we love 6.0's speed so much we're not willing to go back.
     
    Thanks,
     
    -Tim

  •  08-07-2007, 9:14 AM 32223 in reply to 32157

    Re: HTML entities in CuteEditor 6.0

    Reply Quote
    Tim,
     
    We are investigating this issue and will get back to you as soon as possible.
     
     
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  10-19-2007, 2:16 PM 34446 in reply to 32223

    Re: HTML entities in CuteEditor 6.0

    Reply Quote
    I have noticed that if our users enter two or more spaces in a row like "  " (space,space) , it save to SQL, and when we display it later we get a small box in place of the two spaces, it looks kinda like [] but is really just one character. Any ideas? It seems like when it goes through SQL is is the issue. Is this some encoding conflict?
View as RSS news feed in XML