Sorry, again I18n. Each operting system (user logged on to the system) has a default character set, which is used as default by the JVM. It is the default character set used to translate the characters read from file (InputStream) into unicode, which Java uses internally. Yesterday I committed a few changes which allow to modify the character set used to create the HTML output sent to the client. This time it is about the character set of the markup files. As described above and as Wicket does not provide any character set while reading the markup file, Java applies the default character set which might be different for each user and OS. And because it is about the markup files, you can not set a default character set for a Page or Component. It has to be per markup file. Markup files are HTML files. I'm not sure about HTML, but XML solves the problem by means of <?xml version="1.0" encoding="ISO-8859-1> which has to be the very first "tag" if at all available. Using this aproach for Wicket markup files could solve our problem as well. But I'm not sure it is HTML 3.x and 4.x compliant. And not sure HTML editors are able to handle it properly. XHTML by the way, because it is fully XML compliant supports this statement.
What do you think? Does it makes sense? Juergen P.S.: This could be the reason if the encoding example does not show the German special characters (Umlaute: ���). ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Wicket-develop mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wicket-develop
