Lance- You bet cha CRLF's are bad. I see so many people making complicated table structures or any complicated "nesting" of elements and they always wonder why it doesn't format correctly... The answer is simple remove the crlfs(and tabs). Most don't believe this but, 99.9 time out of 100 all that's needed it to rip out ALL crlf and tabs and the browser will format correctly. This is true ANYWHERE in the file NOT just where you might expect it to make a difference but, ANYWHERE IN THE xml/xhtml/html that the browser is processing.
I'm not going to argue that building complicated nested elements is something that should be done by hand (I have an obvious preference for producing xml) but none the less removing ALL crlfs and tabs will usually solve formatting problems provided it's xhtml that passes http://validator.w3.org/ On Apr 25, 5:35 pm, Lance Dyas <[email protected]> wrote: > I took a look back at your earlier post.. yes adding in the unnecessary > carriage returns and line feeds is a bad thing I will agree ... not only > does it soak unnecessary band width it messes with some parsers by > adding additional text nodes in the xml. > ironic > note...http://www.microimages.com/ogc/newtntmap/gmap.htm?kml=http://www.phsa... > > [multipart_alternative_part< 1K ] > > > > No virus found in this outgoing message. > Checked by AVG -www.avg.com > Version: 8.0.238 / Virus Database: 270.12.4/2080 - Release Date: 04/25/09 > 08:29:00 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
