> MSIE still doesn't like the "<>" characters in line 58 of the > mashup.htm code, but it will at least allow for the display of the > info when clicking on "Compatibility View." Good to see you're almost there. And apologies for the bum steer on parsing your JSON data. I should have added to my original disclaimer that I don't know anything about JSON, either.
I'm not seeing any markers in IE either, but I'm sure that Andrew's suggestion for tweaks to your data file will fix that. if the line 58 problem persists, I would try even MORE apostrophes around the html tags and see if that doesn't make a difference. I'd try something like this: var html = '<b>'+name+'</b><br /><a href="'+web+'">'Client website'</ a><br /><a href="'+url+'">'Link to more info at mapformation.com'</ a><p>'+info+'</p>'; Which may work. Or it may break the thing entirely - no harm in trying. But expecting people to view your page in compatibility mode is a bit of an ask in my book. I have one more suggestion for once you get the above sorted - some of those text chunks are very chunky (Florida International University is a decent example). You could consider putting line breaks in your text in the data file to break long passages up, although how JSON will deal with those tags is, as I say, beyond me. You might need to wrap the text in CDATA tags. Or something else entirely. Or nothing at all. Possibly worth noting, too, is that infowindows have a maxWidth optional parameter, which means that you can make them narrower (the payoff being that they become taller). From a readability viewpoint, I think text on screen is best in reasonably short paragraphs with reasonably short line lengths. -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
