Re: Encoding problem - strategy needed SOLVED

[Andreas Pardeike <an...@pardeike.net>]

On 13 okt 2004, at 09.47, Mind Bridge wrote:

> 1) The character set(s) used to encode the templates.
>
> 2) The character set used to encode the generated HTML
>
>
> The two are different, and are not related. If I understand your  
> message
> correctly, you have a problem with (1) -- your templates are most  
> likely not
> read correctly by the application.

You're right.

> Please have a look at the following part of the documentation:
> http://jakarta.apache.org/tapestry/doc/TapestryUsersGuide/ 
> configuration.character-sets.html

Good pointer.

> In short, you could add something like this:
>
> <property name="org.apache.tapestry.template-encoding" value="UTF-8"/>
>
> to the .application file or to the relevant .page files and the  
> templates
> would use the UTF-8 encoding.

Works perfectly and I don't need to overwrite getResponseWriter. Great!

> Please note that (2) defaults to UTF-8 and covers almost all encodings  
> that
> could be used for the templates as a result. Typically there is no  
> need to
> change that (although it is possible).

I thought so.

Thanks a lot,
Andreas Pardeike


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org