We’re delivering an RSS feed (so XML). Unicode will break it. From: <[email protected]> on behalf of Christopher Hamlin <[email protected]> Reply-To: MarkLogic <[email protected]> Date: Thursday, February 9, 2017 at 11:19 AM To: MarkLogic <[email protected]> Subject: Re: [MarkLogic Dev General] Is xdml:unquote appropriate for handling accent characters?
I still think the goal isn't clear (to me). What are you actually trying to deliver? HTML, XML, XHTML? Why do you want é instead of the Unicode character? I'd go back to basics: break the problem down to steps, define what's needed at each step, and see where it goes wrong. On Thu, Feb 9, 2017 at 2:05 PM, Kari Cowan <[email protected]<mailto:[email protected]>> wrote: I guess I could do a function with a series of replacements >> fn:replace($Str,"é","&eacute;") I was hoping there was a better way. From: <[email protected]<mailto:[email protected]>> on behalf of Kari Cowan <[email protected]<mailto:[email protected]>> Reply-To: MarkLogic <[email protected]<mailto:[email protected]>> Date: Thursday, February 9, 2017 at 10:53 AM To: MarkLogic <[email protected]<mailto:[email protected]>> Subject: Re: [MarkLogic Dev General] Is xdml:unquote appropriate for handling accent characters? We stored in the doc as: Pokémon In xQuery I retrieve with let $theTitle:=$doc//ir:HEADLINE/text() That returns as: Pokémon How can I return it as Pokémon instead of Pokémon? From: <[email protected]<mailto:[email protected]>> on behalf of Christopher Hamlin <[email protected]<mailto:[email protected]>> Reply-To: MarkLogic <[email protected]<mailto:[email protected]>> Date: Thursday, February 9, 2017 at 9:44 AM To: MarkLogic <[email protected]<mailto:[email protected]>> Subject: Re: [MarkLogic Dev General] Is xdml:unquote appropriate for handling accent characters? It's still unclear (to me) what is going on. Here's some stuff I'd try: Is the title in the ML db? If so, it's been parsed and stored as UTF-8. The query console can be complicated since it is goes through layers and is friendly in its output. You can check the data by getting dumping out the xml to disk and inspecting via whatever you might use for that. Just use xdmp:save. Then you know how things are in the db. Then, if you are going through an appserver, just do the request and store the result. Again, check things out on disk. Look at the headers returned and the payload. Is the returned 'stuff' OK in an XML editor? If that's OK, then what is parsing the return and choking, and why is it choking? _______________________________________________ General mailing list [email protected]<mailto:[email protected]> Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
