I have a difficult problem and I'm sorry to post such a general question to the dev list but I dont expect to find an answer elsewhere, and I'm hoping a javascript master may have some creative solution.
The library of congress is unifying it's search process, it's a 'heavy' javascript solution, and jquery is being used. Originally objtree.js was used to transform the xml messages (getting json is unfortunately not an option currently). Profiling showed I was getting a heavy hit in objtree so I made some minor modifications to jquery.xslt.js to setup a simple client-side xslt pipeline. the good news it works in ff2/3 - ie5/6/7 - opera9/10 but chrome1/2 and safari9/10 fail for content delivered from 3 of 6 targets. the 3 failure targets use consistent utf-8 encoding surprisingly. I found the following: In the webkit engine there was, or is, apparently a problem parsing javascript with some utf-8 characters: http://code.google.com/p/chromium/issues/detail?id=2015 http://code.google.com/p/chromium/issues/detail?id=176 This is apparently fixed though I still experience the problem. The important point is the javascript is generated from xml on the client with xslt, no errors, clean utf-8, but parsing it fails with an unhelpful 'unexpected_token ILLEGAL'. I'm sort of tearing out my hair out but have plenty of other things to keep me busy. Has anyone else run into issues with a clever solution? Again, apologies for a post not specific to the dev of jquery, just hoping someone with more experience has an idea. Thanks Thatcher -- Christopher Thatcher --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
