I agree. This patch definitely should be in the core. I also have to
apply this patch myself in the similar way.
δΊ 2013/7/20 13:38, Alex Kotchnev ει:
I thought I'd just drop a note on the list to report on how I dealt with
this issue.
At first, I started going down the path of building a modul
I thought I'd just drop a note on the list to report on how I dealt with
this issue.
At first, I started going down the path of building a module that would
somehow override this service, and in the end it turned out that I had to
make way too many changes to make it happen.
Today, I decided, scr
wow, i didn't know that!
i had problems with encoding of properties in recent t5 projects but maybe
maven got in the way or this service did not get used.
cheers,
andi.
On May 23, 2013, at 10:26 , Lance Java wrote:
> You underestimate tapestry :)
>
> Tapestry's PropertiesFileParserImpl assumes
You underestimate tapestry :)
Tapestry's PropertiesFileParserImpl assumes UTF-8 properties files and
performs a native2ascii transformation on the fly
http://tapestry.apache.org/current/apidocs/src-html/org/apache/tapestry5/internal/services/messages/PropertiesFileParserImpl.html#line.79
Hi Lance.
Unfortunately this is not the case. Property files are treated ISO 8859-1 while
reading/writing.
If you want to have special chars, you have to run the file through
native2ascii first.
http://docs.oracle.com/javase/6/docs/api/java/util/Properties.html
On May 22, 2013, at 9:49 , Lance
Yes, patching the bug would require a copy of TemplateParserImpl (71 lines)
and SaxTemplateParser (1197 lines)
The great thing about tapestry / tapestry IOC is that you can workaround a
bug like until a fix is provided in a later release.
Much better than rebuilding a custom version of tapestry f
Alejandro,
unfortunately, adding the XML declaration doesn't help. .
This obviously wouldn't be an issue if a) I was running my own JVM,
which in most situations where one hosts an application is the case
(unfortunately, not the case in PAAS like GAE) or b) Tapestry didn't use
the default pl
Josh Canfield 've asked a very good question in TAP5-1778.
does Tapestry respect the XML declaration for changing charset?
Have you tried adding an xml header to your templates?, like:
Alejandro.
On Wed, May 22, 2013 at 9:49 AM, Lance Java wrote:
> I think you've hit the nail on the head and
I think you've hit the nail on the head and that this relates to TAP5-1778.
As a work around, can you put your special chars in a language specific
properties file? By default, prop files are treated as UTF-8. You can also
override the PropertiesFileParser if you need.
Another option is to overri
I have an application on Tapestry 5.3.6 that is deployed to GAE 1.8.0. The
problem I have seems to be appengine specific (and not necessarily tapestry
specific) as I have older versions of this application running on GAE and
rendering the locale specific templates normally (whereas now the older
ve
10 matches
Mail list logo
