Exactly! Quoting from the page you provided: "Java uses the standard
character set ISO 8859-11 to encode text files like properties files.
..." (Note that this is a typo above---the author meant to say "ISO
8859-1", not "ISO 8859-11". The link to
http://en.wikipedia.org/wiki/ISO/IEC_8859-1 in the text is correct,
however.)
So according to that description, my FooterPanel.properties file is
expected to be encoded in ISO-8859-1. And indeed it is, as I have
repeatedly explained.
So I ask again: what is wrong with my current configuration?
Garret
On 8/28/2014 10:25 AM, Francois Meillet wrote:
http://wicket.apache.org/guide/guide/
François Meillet
Formation Wicket - Développement Wicket
Le 28 août 2014 à 19:24, Garret Wilson <gar...@globalmentor.com> a écrit :
So are you saying that Wicket does not support ISO-8859-1 properties files that adhere do
the Java standard? Or are you saying, "I don't know what the problem is, I'm just
giving you a workaround?" If so, I appreciate the workaround tip, but that still
doesn't explain what the problem is.
I'm the sort of person who doesn't like to "wave my hands" as we say. I like to find the source of
the problem. My configuration, as far as I can tell, is correct. Moreover, it is technically "more
correct" than the "*.utf8.properties" approach, as my approach follows the standard. In fact
my approach should be the default. So does anyone know why my configuration does not work? What am I doing
wrong?
Sincerely,
Garret
On 8/28/2014 10:18 AM, Francois Meillet wrote:
use *.utf8.properties
François Meillet
Formation Wicket - Développement Wicket
Le 28 août 2014 à 17:47, Garret Wilson <gar...@globalmentor.com> a écrit :
I have Wicket 7.0.0-M2 running on embedded Jetty, which is correctly returning
a content type of UTF-8 for my Wicket page:
Date: Thu, 28 Aug 2014 15:37:52 GMT
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Pragma: no-cache
Cache-Control: no-cache, no-store
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Server: Jetty(9.1.0.v20131115)
I have a properties file FooterPanel.properties that contains the following
line (encoded in ISO-8859-1, as properties files unfortunately require):
copyright=© 2014 Example, Inc.
FooterPanel.html is encoded in UTF-8, has the appropriate XML prolog, and
contains the following reference to the property resource:
<?xml version="1.0" encoding="utf-8"?>
...
<p><small><wicket:message key="copyright">©
Example</wicket:message></small></p>
When this all is rendered, here is what I see in Firefox 31 and Chrome 37:
� 2014 Example, Inc.
I thought I had all the correct encoding indicators at each stage in the
pipeline. But somebody blinked. Where is the problem?
Garret
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
