This is a copy from my comment to issue 936. http://code.google.com/p/gmaps-api-issues/issues/detail?id=936
---------- Hi Pamela, thanks for looking into this issue. I still see room for improvement other than adding some clarifying words to the documentation. The programmer can follow the documentation, the viewer can not. He depends on the programmer doing things right. Also, using utf-8 might not be possible in all cases. Isn't it possible to use html entities for the labels and tooltips of the controls? Then the text "Gelände" would display as "Gelände" regardless of what charset the page uses, even if it doesn't use one at all. I think this is rather important to make sure all Google Maps mashups look the same in all places of the world. Reason 1: As I pointed out in the thread given above, charset utf-8 might not be possible in all cases. Reason 2: Using the additional parameter oe (see the thread) is only a workaround that happens to work in my area. It won't work out in countries that display labels with characters not from that charset. Reason 3: Programmers for example in english speaking countries might not be aware of the necessity to use a charset declaration, because they don't see the problem in first place. Even though updates to the documentation are definitely a good idea, they likely don't reach all programmers. Thanks Jürgen On 28 Dez., 09:09, "Neil.Young" <[email protected]> wrote: > From the initiator of this thread: Thank you :) > > Regards > > > > - Zitierten Text ausblenden - > > - Zitierten Text anzeigen - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
