Chris, just to clarify something: When I look at a dump of the categories, I see these category names:
Sales &amp; Retail Religion &amp; Spirituality and so on. Is this correct, what you intended? I'm wondering what purpose there is to double-escape an ampersand in the output, since it is being processed internally (in PHP or whatever) before rendering on the client's browser. I have to do an extra internal step to un-escape the extra one. -Alex On Mon, Nov 15, 2010 at 14:09, Chris Radcliff <[email protected]> wrote: > Hi Mike, > > It looks like there are a couple of things going on here. I'll check with our > data team and see what should be happening, and I'll get back to you with the > result. Thanks again for pointing these out. > > Cheers, > ~chris > > On Nov 15, 2010, at 12:52 PM, Mike Battista wrote: > >> >> Thanks, Chris. >> >> I've seen this issue surface in a bunch of different ways including the >> following examples. >> >> - Tony V's Garage - "V0-001-002123194-1" >> - BJ\'s Bingo - "V0-001-004458341-8" >> - Danny&39;s Pub - "V0-001-002241355-1" >> - Woody's on the Water - "V0-001-002212041-1" >> - Romeo's Bar & Grill - "V0-001-002032900-9" >> - Engel's Pub - "V0-001-001987156-0" >> - Mari's Place - "V0-001-002062024-5" >> - Slades Bar & Grill - "V0-001-000893868-3" >> - Harvest Café - "V0-001-000636877-4" >> >> Some of these venues look like this on the website, too, but others like >> Harvest Café look correct on the website, but come back in the API like >> Harvest Caf&eacute;. The & entity gets correctly decoded to & and >> then I'm left with "Harvest Café". Slades Bar & Grill has the same >> problem. The & comes back in the API like Slades Bar &amp; Grill. The >> & gets correctly decoded to & and then I'm left with Slades Bar & >> Grill. >> >> It seems like there's some double encoding happening somewhere. >> >> Mike > > >
