On Thu, Apr 14, 2011 at 10:49 AM, Yonik Seeley <yo...@lucidimagination.com> wrote: > Hmmm, looks like the highlighting code changed. Using the example > doc, with 1.4 I get > > http://localhost:8983/solr/select?q=features:circumflexes&hl=true&hl.fl=features&wt=json&indent=true > > "highlighting":{ > "UTF8TEST":{ > "features":["eaiou with <em>circumflexes</em>: êâîôû"]}}} > > With 3.1, this now looks like > > "highlighting":{ > "UTF8TEST":{ > "features":["eaiou with <em>circumflexes</em>: > êâîôû"]}}} > > So it's started to produce XML entities even when not in XML format. > And even worse, when one is using the XML format, those entities are > treated as literal data and escaped: > <str>eaiou with <em>circumflexes</em>: > &#234;&#226;&#238;&#244;&#251;</str>
Although I guess if the actual value is supposed to be HTML, then this looks like it's working as designed? Perhaps someone more familiar with the highlighter can chime in - I didn't see anything called out when looking at CHANGES.txt -Yonik http://www.lucenerevolution.org -- Lucene/Solr User Conference, May 25-26, San Francisco
