I found some info about an 'encoding' attribute for f:view element and
someone even reported it worked even though the attribute is not listed
in the tld (?!?) Myfaces 1.1.3 is complaining that the attribute cannot
be used with f:view element.
The question still stands: is there another way for making myfaces treat
files as utf-8 other than the magical line: '<%@ page
pageEncoding="UTF-8" contentType="text/html;charset=UTF-8"
language="java" %>' ??
Regards,
Tom Pasierb
Mike Kienenberger napisał(a):
I've seen postings on the facelets mailing list that indicate that
this can be set as an f:view attribute. Try looking at that
component.
On 9/20/06, Tomasz Pasierb <[EMAIL PROTECTED]> wrote:
Hello there,
I'm trying to use myfaces with characters other than ascii. All of the
characters that are utf-8 or iso-8859-2 (which I'm trying to use)
specific get encoded to html entities and as a result utf-8 characters
do not display correctly.
I suppose a line '<%@ page pageEncoding="UTF-8"
contentType="text/html;charset=UTF-8" language="java" %>' would correct
the problem if only I was using jsp as a display technology. In fact I'm
trying to take advantage of shale clay's composition features. And what
I am actually using are html files where the mentioned line will have no
meaning or even cause errors.
Is there any setting to either:
1. set an option so that MyFaces wouldn't encode characters as
entities or
2. set an option that would make myfaces treat all files as encoded with
i.e. UTF-8 and thus not turn utf-8 two-byte characters into entities
Maybe there's another solution. I'd be grateful for any.
Regards,
Tom Pasierb
------------------------------------------------------------------------
Szybko i tanio ubezpiecz samochod!
Kupno polisy zajmie Ci 15 minut! Kontakt przez telefon albo Internet.
Kliknij i sprawdz: http://link.interia.pl/f19a0
----------------------------------------------------------------------
Jestes kierowca? To poczytaj! >>> http://link.interia.pl/f199e
