Hi all- Just wanted to let you know I've filed a feature request internally about inserting a paragraph in the documentation about character encoding.
- pamela On Dec 19, 2:31 am, "Neil.Young" <[email protected]> wrote: > Yes, I see your point. HTML entities would probably help. This is > especially important for our english speaking friends, who probably > don't care about content-encoding, and also do not see, how there > "default" buttons look like in other languages. The same issue by the > way with the sizing of the menu buttons top right. If the local > representation of given menu point enlarges the button, than the button > may overlay others... > > Jürgen schrieb: > > > I don't know much about the internals, but to me the text "Gelände" > > seems to be just a simple html-string. Why can't Google write it as > > "Gelände" then it would display ok whatever charset the page is > > using. > > > My point is that there might be legitimate reasons for not using > > charset utf-8. It may break other parts of the page. As of now not all > > editors, databases and so on can deal with utf-8. > > > I don't know if there is a simple solution, but if there is why not > > implement it. > > > On 18 Dez., 07:34, Mike Williams <[email protected]> wrote: > > >> If there is a real issue here, it's an issue with MSIE. There's nothing > >> that Google can do about it other than adding a recommendation to set > >> the charset to utf-8 in the documentation > > >> --http://econym.org.uk/gmap > >> The Blackpool Community Church Javascript Teama --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
