Hi,

See this:

http://jakarta.apache.org/tapestry/doc/TapestryUsersGuide/configuration.character-sets.html

Basically, place the following in your .application file (for example):

<property name="org.apache.tapestry.template-encoding" value="ISO-8859-1"/>

Use the encoding above that you need.

-mb

----- Original Message ----- 
From: "Dirk Dittert" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, June 19, 2005 2:10 PM
Subject: How to set file encoding/proper way for cross platform development


> Hi,
>
> I started developing my first Tapestry web application while reading
> through the "Tapestry in Action" book.
>
> My development system is OS X, deployment will be on x86 linux.
> Currently, all files are saved with ISO 8859-15 encoding by my IDE to
> avoid cross platform encoding issues. File encoding also is declared
> properly in the html header.
>
> My files are served properly, if I access them statically by Tomcat
> (e.g. http://.../Home.html) but not if I access them through Tapestry
> (http://.../app). Tapestry seems to read my files in the native
> MacRoman Encoding and then converts them to ISO 8859-15 which is not
> what I want (e.g. Umlauts are not rendered properly that way). Of
> course, Umlauts are correct if I save the file im MacEncoding. This
> will break later when the application is deployed on Linux.
>
> Is there any way to tell Tapestry about the encoding of template html
> files? Or is there another approach I should take for cross platform
> development?
>
> Best,
>
> Dirk Dittert
> -- 
> Don't Program by Coincidence
> Rely only on reliable things. Beware of accidental complexity, and
> don't confuse a happy coincidence with a purposeful plan.
>      The Pragmatic Programmer
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to