On Thu, Aug 21, 2008 at 1:50 PM, Filip S. Adamsen <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Tapestry 5.0.14 changes the way .properties files are read so they are read
> in a way that works with UTF-8 encoded files, at least on Java 6.
JDK 1.5 and 1.6.
>
> Now, my guess is that they were being read co
Strict US-ASCII character set is afaik made up of characters <= 127.
Your special characters were therefore not pure ASCII. I think that in
your case the machine your are coding on defaulted to a charset that
could handle your special characters as you intended them to be. If you
would have loaded
This is what I'm already doing :)
I just thought strange because nobody noticed yet. I had to go through
all my .properties files changing the encoding. But fortunately, as I
see, it's just me.
Thanks.
On Thu, Aug 21, 2008 at 5:32 PM, Martijn Brinkers (List)
<[EMAIL PROTECTED]> wrote:
> So what y
Hi,
Tapestry 5.0.14 changes the way .properties files are read so they are
read in a way that works with UTF-8 encoded files, at least on Java 6.
Now, my guess is that they were being read correctly before because Java
read the .properties files using the default encoding, which would
probab
So what you are saying is that when you save your property file as UTF-8
the 'special' characters are shown correctly but not when you save your
propery file as a ANSI file?
If so why don't you save it as UTF-8 and leave it this way? Or am I
missing something?
Martijn
On Thu, 2008-08-21 at 17:0
No one is having this kind of problem? I tested in other situations
and this is still happening... I'll try to change my eclipse's default
configuration, maybe will help for now...
On Wed, Aug 20, 2008 at 9:42 AM, Marcelo Lotif <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm experiencing a little pro
