Yup, doing it in UTF-8 end-to-end seems to be the right solution. We
are converting our database as well.
On Apr 29, 10:04 am, "Miguel Beltran R." wrote:
> 2009/4/26 Diodeus
>
>
>
>
>
> > Miguel,
>
> > I am having a similar problem and have spent many hours looking for an
> > answer.The answer
2009/4/26 Diodeus
>
> Miguel,
>
> I am having a similar problem and have spent many hours looking for an
> answer.The answer I always get is: "serve it as UTF-8", which requires
> the program answering the AJAX call to do the conversion.
> Unfortunately the system I am using does not allow me to
Miguel,
I am having a similar problem and have spent many hours looking for an
answer.The answer I always get is: "serve it as UTF-8", which requires
the program answering the AJAX call to do the conversion.
Unfortunately the system I am using does not allow me to do this and I
need to support Fr
2009/4/24 Miguel Beltran R.
>
>
> 2009/4/24 Miguel Beltran R.
>
> Hi list
>>
>> Here in my job the system use MS Sql Server 2000 what not have support
>> utf-8, so I need work with ISO-8859-1.
>> Using Ajax this send the parameters with encoding utf-8, after read a lots
>> post I tried with the
2009/4/24 Miguel Beltran R.
> Hi list
>
> Here in my job the system use MS Sql Server 2000 what not have support
> utf-8, so I need work with ISO-8859-1.
> Using Ajax this send the parameters with encoding utf-8, after read a lots
> post I tried with the options
> modifica: function(evt){
>
