Hi Takeo.
> If you are using Turbine with Velocity, You can use following line in
> TR.properties,
> please remove that comment mark. It will works.
>
> #services.VelocityService.input.encoding=UTF-8
Oh ... Yes I'm using velocity, I tried it before, but it didn't work.
Maybe there's something wrong in my setting.
OK , I will check up and try it again .
Thanks .
>
> TSUCHIDA Takeo
> On 2003.6.16, at 04:30 AM, Kaimai Mizuhiro wrote:
>
> > Hello All
> >
> > I'm a Japanese, using Turbine-2.2_01.
> > Here in Japan, I need Japanese characters , so I'm using UTF-8
> > encoding.
> >
> > The problem is that:
> >
> > A1) I can specify response content-type by setting
> > locale.default.charset in TurbineResources.properties. It's OK.
> >
> > A2) But I cannot specify request character-encoding . There seems no
> > such property in TR.properties. I wonder why?
> >
> >
> > I think if there's some property corresponding to Request Character
> > Encoding, it is natural and easy to recognize.
> >
> > The reason is that:
> >
> > B1) At first, I cannot get proper Japanese Characters on the screen at
> > all.
> > Then I found locale.default.charset property (UTF-8).
> > After setting it properly, it worked well. Readable Japanese
> > Characters were displayed.
> >
> > B2) There's still a problem that when I enter some Japanese Characters
> > on a FORM, submit it, and always it goes broken.
> >
> > B3) So I thought there should be some property by which I can tell the
> > servlet the request character encoding is UTF-8. But there's nothing
> > like that.
> >
> > B4) I read Turbine servlet's source code (Turbine.java).
> > I thought if I put a code in the beginning of doGet() method , such
> > as
> > ...........................
> > public final void doGet(HttpServletRequest req,
> > HttpServletResponse res)
> > throws IOException, ServletException
> > {
> > // changing request character encoding to fixed value "UTF-8"
> > // just for experiment
> > String localencoding = "UTF-8"
> > req.setCharacterEncoding( localencoding );
> > ...........................
> >
> > and above change worked well. The problem was solved.
> > So if there's some property that specify 'localencoding' value
> > above, it could be useful.
> >
> > How do you think about it?
> > I read this mailing-list searching for similar problem, then noticed
> > that there's other solution which use Filer class. OK, but it seems
> > more complicated.
> >
> > The method I took may cause some other problem , I want your
> > opinion, more information .
> >
> > Thanks.
> >
------------------------------------------------------------------------
Kaimai Mizuhiro <[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
