Tobie, > A correct character encoding should be all you really need to handle > such entities.
That's rather flip, don't you think? How does character encoding choice solve " or ? These entities are valid HTML, regardless of character encoding. There are sometimes very good reasons for using them. It's fine to say String#unescapeHTML won't handle these because it's too big a problem and document that, but let's not just dismiss it like the person asking the question is being dumb, which is how the above comes across. -- T.J. On Nov 21, 1:10 am, Tobie Langel <tobie.lan...@gmail.com> wrote: > Thanks for your input. > > A correct character encoding should be all you really need to handle > such entities. > > Best, > > Tobie -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to email@example.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en