You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Christian Dutaret <cd...@gmail.com> on 2006/12/04 14:26:24 UTC
wrong rendering of non-ascii characters in ajax response
Hi all,
I have a property selection that contains a string with accented characters,
which is created from a java string literal such as "Mod\u00E8le" (\u00E8 is
unicode for character 'è').
When the property selection is first rendered, it displays fine, but if I
update the property selection from an @EventListener, then the rendered
string becomes "Mod�le".
This didn't happen some time ago, it was introduced by some recent fix on
the 4.1.1 snapshot. Unfortunately, I haven't worked on this stuff for some
time (3 weeks or so), so I can't tell exactly what version is incriminated.
If anyone can think of a workaround until this is fixed, I'd be very happy
to hear.
Thanks all
Ch.
Re: wrong rendering of non-ascii characters in ajax response
Posted by Christian Dutaret <cd...@gmail.com>.
Fixed. Thanks a lot for the quick reaction (and thanks to maven2 for the
immediate availability ;-)
Ch.
2006/12/4, Jesse Kuhnert <jk...@gmail.com>:
>
> Ok. Changes related to ajax/json responses have been reverted and
> should work for you now. Sorry for any issues. (obviously I have some
> new test cases to create)
>
> On 12/4/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> > This may be my fault somehow. I'll look into it today and get back to
> > you with an answer. (still waking up right now)
> >
> > On 12/4/06, Christian Dutaret <cd...@gmail.com> wrote:
> > > Hi all,
> > >
> > > I have a property selection that contains a string with accented
> characters,
> > > which is created from a java string literal such as "Mod\u00E8le"
> (\u00E8 is
> > > unicode for character 'è').
> > > When the property selection is first rendered, it displays fine, but
> if I
> > > update the property selection from an @EventListener, then the
> rendered
> > > string becomes "Mod�le".
> > >
> > > This didn't happen some time ago, it was introduced by some recent fix
> on
> > > the 4.1.1 snapshot. Unfortunately, I haven't worked on this stuff for
> some
> > > time (3 weeks or so), so I can't tell exactly what version is
> incriminated.
> > >
> > > If anyone can think of a workaround until this is fixed, I'd be very
> happy
> > > to hear.
> > >
> > > Thanks all
> > > Ch.
> > >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
Re: wrong rendering of non-ascii characters in ajax response
Posted by Jesse Kuhnert <jk...@gmail.com>.
Ok. Changes related to ajax/json responses have been reverted and
should work for you now. Sorry for any issues. (obviously I have some
new test cases to create)
On 12/4/06, Jesse Kuhnert <jk...@gmail.com> wrote:
> This may be my fault somehow. I'll look into it today and get back to
> you with an answer. (still waking up right now)
>
> On 12/4/06, Christian Dutaret <cd...@gmail.com> wrote:
> > Hi all,
> >
> > I have a property selection that contains a string with accented characters,
> > which is created from a java string literal such as "Mod\u00E8le" (\u00E8 is
> > unicode for character 'è').
> > When the property selection is first rendered, it displays fine, but if I
> > update the property selection from an @EventListener, then the rendered
> > string becomes "Mod�le".
> >
> > This didn't happen some time ago, it was introduced by some recent fix on
> > the 4.1.1 snapshot. Unfortunately, I haven't worked on this stuff for some
> > time (3 weeks or so), so I can't tell exactly what version is incriminated.
> >
> > If anyone can think of a workaround until this is fixed, I'd be very happy
> > to hear.
> >
> > Thanks all
> > Ch.
> >
>
>
> --
> Jesse Kuhnert
> Tapestry/Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
Re: wrong rendering of non-ascii characters in ajax response
Posted by Jesse Kuhnert <jk...@gmail.com>.
This may be my fault somehow. I'll look into it today and get back to
you with an answer. (still waking up right now)
On 12/4/06, Christian Dutaret <cd...@gmail.com> wrote:
> Hi all,
>
> I have a property selection that contains a string with accented characters,
> which is created from a java string literal such as "Mod\u00E8le" (\u00E8 is
> unicode for character 'è').
> When the property selection is first rendered, it displays fine, but if I
> update the property selection from an @EventListener, then the rendered
> string becomes "Mod�le".
>
> This didn't happen some time ago, it was introduced by some recent fix on
> the 4.1.1 snapshot. Unfortunately, I haven't worked on this stuff for some
> time (3 weeks or so), so I can't tell exactly what version is incriminated.
>
> If anyone can think of a workaround until this is fixed, I'd be very happy
> to hear.
>
> Thanks all
> Ch.
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com