On 9/7/06, Chris at globet.com <Chris at globet.com> wrote: > > The thought is that it is *not* being treated as if it were > > HTML-encoded. It is being treated as a literal string. So, if > > you type "&", you will get "&" just as if you had > > typed "asdf" and got "asdf". > > To clarify: the input string *is* "ñ" the ouput string *is* > "&#241;". What I require is that the input string *should be* > "ñ" and the output string *should be* "ñ". Hence my belief > that somewhere in the process of assigning the string value to a > DropDownList item via a ListItem object, an HTML encoding method is > being executed on the string. Oh, I see. This is not at all what I thought you were saying. Then, my searches confirm the source of your confusion -- as far as I can tell, the string should not be HTML encoded. There is no mention in the docs I can find that suggests that's the way it should be handled. Wish I could be more helpful. -- Matt Warden Cleveland, OH, USA http://mattwarden.com This email proudly and graciously contributes to entropy.