Menu
▾
▴
Re: [Exist-open] handling html entities
|
From: Misztur, C. <CMi...@ma...> - 2013-12-02 22:22:42
|
Couldn't you PUT through a restXQ endpoint? On Dec 2, 2013, at 1:05 PM, "Palmer, Eric" <ep...@ri...<mailto:ep...@ri...>> wrote: Wolfgang thanks It would require a major shift in how documents are stored in exist-db if I migrate from http put to passing them through xquery. I will look into using the Neko parser from the file transfer program and maybe I can just do it there. thanks -- Eric Palmer Web Services U of Richmond To report technical issues, obtain technical support or make requests for enhancements please visit http://web.richmond.edu/contact/technical-support.html From: "wol...@ex...<mailto:wol...@ex...>" <wol...@ex...<mailto:wol...@ex...>> Date: Monday, December 2, 2013 1:58 PM To: Eric Palmer <ep...@ri...<mailto:ep...@ri...>> Cc: "exi...@li...<mailto:exi...@li...>" <exi...@li...<mailto:exi...@li...>> Subject: Re: [Exist-open] handling html entities I have a file that contains entities such as ‘ when I upload the file to exist-db I get this sort of error (2.1) One approach would be to use an XQuery which sends the content through util:parse-html before storing it. It will expand all standard html entities. xquery version "3.0"; let $html := "<html> <body> <p>Hello &lsquo; world</p> </body> </html>" return util:parse-html($html) Wolfgang ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ Exist-open mailing list Exi...@li...<mailto:Exi...@li...> https://lists.sourceforge.net/lists/listinfo/exist-open ________________________________ The contents of this message may be privileged and confidential. Therefore, if this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. Please consider the environment before printing this e-mail |