On Jun 30, 2:38 am, karen <[email protected]> wrote: > And while the other browsers had no problems with > the dash character there, IE that lovely prima > donna of a browser, did.
I guess we should investigate further to find out why IE is having problems with the dashes. Regarding 8 bit encoding, the dashes aren't in ISO-8859-1, but the old windows encoding Windows-1252 has got them as character 0x96 and 0x97 (en-dash and em-dash). The Macintosh Roman encoding has got them as 0xD0 and 0xD1. http://unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP1252.TXT http://unicode.org/Public/MAPPINGS/VENDORS/APPLE/ROMAN.TXT so for the en-dash, the character might have been first encoded as 0x96 or 0xD0, and then translated to unicode 0x2013 in the database. Or maybe they are stored in the database as the original Windows or Macintosh encodings?? the Store Locator article is a bit vague about character encoding: http://code.google.com/apis/maps/articles/phpsqlsearch.html#outputxml it says "you can use utf8_encode on the outputted data", but constructs the DOMDocument without an encoding, hence the XML header is output without an encoding, and the browser must use a default when parsing the XML. so maybe you could try changing the PHP to specify the encoding, and see whether IE will accept the dashes. $dom = new DOMDocument('1.0', 'UTF-8'); -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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.
