Re: 4.1.2-SNAPSHOT String in specification escaped

2007-06-25 Thread Jesse Kuhnert
Damnit Drew.,I mean Jesse. I'm afraid you'll have to latch on to the new 2.7.1-SNAPSHOT version of OGNL if you want this particular problem fixed. Sorry. On 6/25/07, Manri Offermann <[EMAIL PROTECTED]> wrote: Hi Marcus, Yes I did, I will just post everything here. ;-) The same thing work

Re: 4.1.2-SNAPSHOT String in specification escaped

2007-06-25 Thread Manri Offermann
Hi Marcus, Yes I did, I will just post everything here. ;-) The same thing works with 4.1.1. The interesting thing is that my spec's japanese characters are being transformed into something like 'u5e74', which looks like the unicode 'code'. Best regards, Manri --

Re: 4.1.2-SNAPSHOT String in specification escaped

2007-06-25 Thread Marcus Schulte
did you put the in the beginning of you spec? 2007/6/25, Manri Offermann <[EMAIL PROTECTED]>: Hi, I have changed my tapestry version for my simple test app to 4.1.2-SNAPSHOT. I have a simple japanese property: which renders fine in 4.1.1-SNAPSHOT: but when switching to 4.1.2-SNAPSHOT I

4.1.2-SNAPSHOT String in specification escaped

2007-06-25 Thread Manri Offermann
Hi, I have changed my tapestry version for my simple test app to 4.1.2-SNAPSHOT. I have a simple japanese property: which renders fine in 4.1.1-SNAPSHOT: but when switching to 4.1.2-SNAPSHOT I the output looks like this: u5e74MMu6708ddu65e5 All settings are UTF-8 for my test app, is