Awesome, thanks everyone for the answers, I'll go and try all the suggestions mentioned. I must note that this is indeed never been a problem with the text editor itself in farcry cms, that works perfect.
On Aug 6, 9:03 am, modius <[email protected]> wrote: > 2010/8/3 Marco van den Oever <[email protected]> > > > When i search for the error "An invalid XML character (Unicode: 0x1c)" > > i see a lot of posts that suggested to clean the text before it is > > send to the xml parser, so how can we solve this? > > Well this had me intrigued so i did a bit of hunting on the > interwebs. This thread looks like it has a reasonable > solution:http://forums.adobe.com/thread/436859 > > In summary you can use this to hunt for the illegals (probably control > characters): > > <cfset aString= "Something I want to investigate"> > > <cfoutput> > <cfloop from="1" to="#len(aString)#" index="char"> > #mid(aString,char,1)#=#asc(mid(aString,char,1))#<br> > </cfloop> > </cfoutput> > > And use something like this to get rid of them: > <cfset newxml = rereplace(oldxml, "[\x00-\x1f]", " ", "All") /> > or more specifically > <cfset fieldReturn = rereplace(fieldReturn, "\x1c", " ", "All") /> > > Mind you.. i thought Ben Nadel's function mentioned earlier in the > thread should have taken care of everything. > > Hope that helps, > > -- geoffhttp://www.daemon.com.au/ -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
