yes, but we explicitly set the charset on the response header, always Thus the browser does not need to guess.
Juergen On 7/13/05, Johan Compagner <[EMAIL PROTECTED]> wrote: > Juergen (and others) > > We now have an output encoding in the ApplicationSettings that is great > but it defaults to UTF-8. So now all the pages are in utf-8 but the > servlet spec > says that default iso-8859-1 is the default charset. > > Should we stick with UTF-8? It is better anyway and no charset > conversion needs to be done > (at least not as much i think) > > johan > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Wicket-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
