Thanks Andrew and Larry, but I still can't get this to work.

The XML file is created by a php file (www.globespots.com/
markersXML.php) based on the Google map tutorial (http://www.map-
server.com/googlemaps/tutorial_api2.html) which use the DOM object.
This DOM and XML is a bit grey area for me, but the actually text in
the XML file is generated by the server, so how can any spaces or
declaration be missing/wrong in the XML?

Based on Andrew suggestion I tried to replace the "/>" with both " />"
and " /marker>" which just made it not work at all.

I have tried to keep everything in utf-8, but I have overlooked
something?

Again any suggestions will be appreciated.

Thanks

On Nov 26, 3:08 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> On Nov 26, 5:48 am, Schall <[EMAIL PROTECTED]> wrote:> Hi,
>
> > Small problem, big headache withhttp://www.globespots.com/test.php
>
> > I'm generating markers from database trough an XML file - similar to
> > the Google Map tutorial. They show up fine in IE, but nothing in FF.
>
> > I have put alert boxes, which shows that the XML is generated fine in
> > both cases, but in FF the markers array is not created (markers.length
> > = 0).
>
> > Any ideas any one?
>
> Firefox has this thing called the "Error Console".  It reports:
> Error: XML or text declaration not at start of entity
> Source File:http://www.globespots.com/test.php
> Line: 2, Column: 1
> Source Code:
> <?xml version="1.0"?>
>
> Notice the "Line: 2".  There is white space before the <?xml ...
> which is invalid.  Firefox rejects invalid xml, apparently IE doesn't
> care in this case.
>
>   -- Larry
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to