modal page encoding

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

modal page encoding

Anna Simbirtsev
Hi,

Encoding issue in Wicket:
we want to change encoding from "utf-8" to "iso-8859-01", after adding the
following codes in application, it works for page, but doesn't work with
modal page, which is still using 'utf-8' encoding.

getRequestCycleSettings().setResponseRequestEncoding("iso-8859-1");
getMarkupSettings().setDefaultMarkupEncoding("iso-8859-1");
Reply | Threaded
Open this post in threaded view
|

Re: modal page encoding

Martin Grigorov-4
disable your browser caches
or give more details what exactly is the problem

On Mon, Aug 22, 2011 at 5:39 PM, Anna Simbirtsev <[hidden email]> wrote:

> Hi,
>
> Encoding issue in Wicket:
> we want to change encoding from "utf-8" to "iso-8859-01", after adding the
> following codes in application, it works for page, but doesn't work with
> modal page, which is still using 'utf-8' encoding.
>
> getRequestCycleSettings().setResponseRequestEncoding("iso-8859-1");
> getMarkupSettings().setDefaultMarkupEncoding("iso-8859-1");
>



--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: modal page encoding

Anna Simbirtsev
 it seems that Ajax form processing should always be encoded in UTF-8, is
there alternative way to let Ajax form processing using 'iso-8859-1' except
changing wicket-ajax.js

On Mon, Aug 22, 2011 at 10:51 AM, Martin Grigorov <[hidden email]>wrote:

> disable your browser caches
> or give more details what exactly is the problem
>
> On Mon, Aug 22, 2011 at 5:39 PM, Anna Simbirtsev <[hidden email]>
> wrote:
> > Hi,
> >
> > Encoding issue in Wicket:
> > we want to change encoding from "utf-8" to "iso-8859-01", after adding
> the
> > following codes in application, it works for page, but doesn't work with
> > modal page, which is still using 'utf-8' encoding.
> >
> > getRequestCycleSettings().setResponseRequestEncoding("iso-8859-1");
> > getMarkupSettings().setDefaultMarkupEncoding("iso-8859-1");
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Anna Simbirtsev
(416) 729-7331
Reply | Threaded
Open this post in threaded view
|

Re: modal page encoding

Martin Grigorov-4
W3C requires UTF-8

On Mon, Aug 22, 2011 at 6:56 PM, Anna Simbirtsev <[hidden email]> wrote:

>  it seems that Ajax form processing should always be encoded in UTF-8, is
> there alternative way to let Ajax form processing using 'iso-8859-1' except
> changing wicket-ajax.js
>
> On Mon, Aug 22, 2011 at 10:51 AM, Martin Grigorov <[hidden email]>wrote:
>
>> disable your browser caches
>> or give more details what exactly is the problem
>>
>> On Mon, Aug 22, 2011 at 5:39 PM, Anna Simbirtsev <[hidden email]>
>> wrote:
>> > Hi,
>> >
>> > Encoding issue in Wicket:
>> > we want to change encoding from "utf-8" to "iso-8859-01", after adding
>> the
>> > following codes in application, it works for page, but doesn't work with
>> > modal page, which is still using 'utf-8' encoding.
>> >
>> > getRequestCycleSettings().setResponseRequestEncoding("iso-8859-1");
>> > getMarkupSettings().setDefaultMarkupEncoding("iso-8859-1");
>> >
>>
>>
>>
>> --
>> Martin Grigorov
>> jWeekend
>> Training, Consulting, Development
>> http://jWeekend.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
> --
> Anna Simbirtsev
> (416) 729-7331
>



--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: modal page encoding

Bruno Borges
We work with projects based on Portuguese and we are having some problems
because of that too. It seems that it is easier to just use UTF-8 instead of
ISO.


*Bruno Borges*
(21) 7672-7099
*www.brunoborges.com*



On Mon, Aug 22, 2011 at 1:01 PM, Martin Grigorov <[hidden email]>wrote:

> W3C requires UTF-8
>
> On Mon, Aug 22, 2011 at 6:56 PM, Anna Simbirtsev <[hidden email]>
> wrote:
> >  it seems that Ajax form processing should always be encoded in UTF-8, is
> > there alternative way to let Ajax form processing using 'iso-8859-1'
> except
> > changing wicket-ajax.js
> >
> > On Mon, Aug 22, 2011 at 10:51 AM, Martin Grigorov <[hidden email]
> >wrote:
> >
> >> disable your browser caches
> >> or give more details what exactly is the problem
> >>
> >> On Mon, Aug 22, 2011 at 5:39 PM, Anna Simbirtsev <[hidden email]
> >
> >> wrote:
> >> > Hi,
> >> >
> >> > Encoding issue in Wicket:
> >> > we want to change encoding from "utf-8" to "iso-8859-01", after adding
> >> the
> >> > following codes in application, it works for page, but doesn't work
> with
> >> > modal page, which is still using 'utf-8' encoding.
> >> >
> >> > getRequestCycleSettings().setResponseRequestEncoding("iso-8859-1");
> >> > getMarkupSettings().setDefaultMarkupEncoding("iso-8859-1");
> >> >
> >>
> >>
> >>
> >> --
> >> Martin Grigorov
> >> jWeekend
> >> Training, Consulting, Development
> >> http://jWeekend.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
> >
> >
> > --
> > Anna Simbirtsev
> > (416) 729-7331
> >
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>