Yes, I noticed that the samples use utf-8 too. That makes as much (or as little) sense as any other encoding giving that a String is being passed in. I guess unless someone from the Android team can shed light on it, I'll just go with my theory that the encoding parameter is used to encode the String before passing it to the nativeWebKit engine.
Thanks! Pete On Jul 3, 7:36 pm, Mark Murphy <[EMAIL PROTECTED]> wrote: > pcockerell wrote: > > I'm confused about the encoding parameter of loadData(). Since the > > data argument is a Java String, by definition it's in UCS-2 > > representation. > > I can tell you that the one loadData() sample in ApiDemos in the SDK > uses "utf-8" for the encoding parameter, and in some code I've written, > I've used "UTF-8" for the encoding parameter. > > This does not mean UCS-2 is necessarily invalid, or why the sample uses > UTF-8. My string-encoding fu is weak, so I'm just following the sample's > lead (capitalizing it only because I thought that was the official way > to name the encoding). > > Sorry if this doesn't help you much... > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > _The Busy Coder's Guide to Android Development_ -- Available Now! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
