Thanks a lot, man! That helped.
I did:
glassfish@Ubuntu-1110-oneiric-64-minimal:~$ bin/asadmin --secure
create-jvm-options -- -Dfile.encoding=utf-8
and stop-domain, start-domain.
I just thought that previous comment was referring to some system jvm
option.
--
View this message in context:
http:
On Fri, 16 Mar 2012 14:02:40 -0300, bigcache1
wrote:
This is only in case when russian letters are in .tml file.
When they are returned values, or from .properties files - everything is
ok.
File encodings:
.tml - utf-8
.properties ISO-8859-1
Not ok. For Tapestry, .properties files should
No. You need to add this into JVM options tab in glassfish and make sure it's
on the command line when you do a ps.
On Mar 16, 2012, at 1:15 PM, bigcache1 wrote:
> I added this option to maven.
> mvn install -Dfile.encoding=utf-8
> Am I right?
>
> --
> View this message in context:
> http:
I added this option to maven.
mvn install -Dfile.encoding=utf-8
Am I right?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-encoding-issues-tp2427143p5571968.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
Did you try adding -Dfile.encoding=utf-8 to the jvm command line?
On Fri, Mar 16, 2012 at 10:02 AM, bigcache1 wrote:
> BUMP!!
>
> I've recently updated my app to the Tapestry 5.3
> Everything works great, thanks to all developers.
> Just have a little problem with encoding of russian symbols in
BUMP!!
I've recently updated my app to the Tapestry 5.3
Everything works great, thanks to all developers.
Just have a little problem with encoding of russian symbols in tml files.
Instead of russian or just wrong "chinese" symbols, I get this ? ???
? ?.
This is only in case when russian
Use -Dfile.encoding=utf-8 when starting up Java; you can set it as JVM
default properties in Eclipse.
Kalle
On Tue, Jan 6, 2009 at 11:42 AM, Christoph Jäger <
christoph.jae...@derwald.at> wrote:
> Hi Lutz,
>
> thanks for your thoughts. As far as I can see, the encoding in the
> generated HTML is
Hi Lutz,
thanks for your thoughts. As far as I can see, the encoding in the
generated HTML is correct (everything works nicely if the special
characters come from some different place than a compiled .java file).
Additionally, I found the same behaviour in graphics generated using
JFreeCh
