While not related to the character encoding issue, you should be careful declaring content as application/xml+xhtml in the browser-based web (as opposed to the web service-based web). Internet Explorer (even versions 7 and 8) does not know how to handle content served as application/xml+xhtml. It will prompt you to download the contents of the page rather than rendering it. See <http://blogs.msdn.com/ie/archive/2005/09/15/467901.aspx>.
Justin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James A. Robinson Sent: Monday, August 18, 2008 10:19 AM To: General Mark Logic Developer Discussion Subject: Re: [MarkLogic Dev General] Bad Codepoint error > As Mike said initially, if the link is in a UTF8 web page then it works fine. > The problem I have is when typing in a url directly or editing an existing > url. > Not sure there's any way around it though. In experiments we've run it looked to us as though most browsers will send back information using the encoding specified by the page. So if you ensure that your application sends its output indicating that encoding, e.g., Content-Type: application/xhtml+xml;charset=UTF-8 I think most modern browsers will then encode any characters you type into forms or the URL bar as UTF-8. Jim - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - James A. Robinson [EMAIL PROTECTED] Stanford University HighWire Press http://highwire.stanford.edu/ +1 650 7237294 (Work) +1 650 7259335 (Fax) _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
