O.K , I see the problem is with the content providers. But the fact that all the content providers use Turkish charset in Turkey and most of them do not apply any declaration to the wml source. All tho other wap gateways give successful output with this format, but Kannel does not.
I should find someway to remove this check from the gateway or I should use another wap gateway. I can not force all the wap sites to declare charset in their wml's. Can't you help me remove the check from the libxml ? Regards, ilker --- Oded Arbel <[EMAIL PROTECTED]> wrote: > No - there is no way, as this check isn't in the > Kannel gateway but in the libxml2 XML handling code > which is not part of the gateway's code, but simply > a library it is using. I suggest you contact your > content provider and make sure that they use > compliant XML, as no one can gurantee correct > results if using non-standardized input. > > XML is defined as using charset utf-8 by default if > not explicitly set other wise in the content. by > assuming a different implied character set w/o > specifing it explicitly, you are essentialy breaking > the XML standard and making sure that no standard > compliant XML parser can handle your content. > > -- > Oded Arbel > m-Wise mobile solutions > [EMAIL PROTECTED] > > +972-9-9581711 (116) > +972-67-340014 > > ::.. > The safest seat in a aeroplane is within the black > box. > > > > > > -----Original Message----- > > From: ilker Aktuna [mailto:[EMAIL PROTECTED]] > > Sent: Monday, August 19, 2002 7:48 AM > > To: Oded Arbel; [EMAIL PROTECTED] > > Subject: RE: charset problem > > > > > > Hi, > > > > Thanks for your reply. > > I can not declare the encoding in the XML because > I am > > not the owner of these wap sites. > > Is there another way to remove this check from the > > gateway ? > > > > Kind Regards, > > ilker > > > > --- Oded Arbel <[EMAIL PROTECTED]> wrote: > > > > > > > -----Original Message----- > > > > From: Paul Keogh [mailto:[EMAIL PROTECTED]] > > > > This is a libxml error; From the libxml src; > > > > > > > > /* > > > > * If we detect an UTF8 error that > probably > > > mean that the > > > > * input encoding didn't get properly > > > advertized in the > > > > * declaration header. Report the error > and > > > switch the encoding > > > > * to ISO-Latin-1 (if you don't like this > > > policy, just declare the > > > > * encoding !) > > > > */ > > > > > > > > Without trawling the src further, seems like > the > > > gateway only accepts > > > > UTF-8 encoding. > > > > > > Or - declare the character set in the XML as per > the > > > syntax. > > > > > > -- > > > Oded Arbel > > > m-Wise mobile solutions > > > [EMAIL PROTECTED] > > > > > > +972-9-9581711 (116) > > > +972-67-340014 > > > > > > ::.. > > > "Did you ever wonder if the person in the puddle > is > > > real, and you're just a reflection of HIM?" > > > -- Calvin and Hobbes > > > > > > > > > ===== > > ilker Aktuna > > Network Expert > > CCNP, CCDA > > > > __________________________________________________ > > Do You Yahoo!? > > HotJobs - Search Thousands of New Jobs > > http://www.hotjobs.com > > ===== ilker Aktuna Network Expert CCNP, CCDA __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com
