XML problem...

bigowner · Post by **bigowner** » Tue Feb 14, 2006 4:23 pm

when i opened a RSS feed near a category
it gave an erro like this

<b>Warning</b>:  mb_convert_encoding(): Illegal character encoding specified in <b>/home/imacin/domains/bo...

my site is : http://www.boshver.com

thanx

bigowner · Post by **bigowner** » Tue Feb 14, 2006 4:30 pm

sample xml error

http://www.boshver.com/index.php?/feeds ... -Sanat.rss

judebert · Post by **judebert** » Tue Feb 14, 2006 6:15 pm

Serendipity is trying to encode your language (which is not currently set to UTF-8 encoding) to UTF-8 for your browser. It's using the mb_convert_encoding() function because your server doesn't support iconv.

The charset of your blog is not recognized by mb_convert_encoding(). It's expecting something like "JIS", "EUC-JP", "sjis-win", or the like.

What is your Serendipity's charset?

bigowner · Post by **bigowner** » Tue Feb 14, 2006 6:50 pm

i am from Turkey and my charset is windows-1254

Post by **garvinhicking** » Wed Feb 15, 2006 11:56 am

Serendipity has no turkish language distributed. You'll need to use a charset as LANG_CHARSET constant inside your language file that is supported by mb_convert_encoding.

I suggest you to use UTF-8.

Regards,
Garvin

bigowner · Post by **bigowner** » Wed Feb 15, 2006 6:57 pm

but UTF-8 is so many problem with turkish...

dont we solve this probkem?

Post by **garvinhicking** » Thu Feb 16, 2006 12:08 pm

Why should there be a problem? UTF-8 should contain all turkish characters.

You can ask the PHP developers if they plan to add windows-1254 support to PHP in the future, then you wouldn't need UTF-8. But I guess that is not an option.

Regards,
Garvin

bigowner · Post by **bigowner** » Wed Feb 22, 2006 4:18 pm

when i choose UTF-8 charset it gices so many error. it doesnt support some of Turkish charecters...

Post by **garvinhicking** » Wed Feb 22, 2006 4:51 pm

What errors do you get?

UTF-8 does support all turkish characters, I'm sure. Of course when you change to UTF-8 charset while already having some win-1254 characters, those will break. So you would either need to convert your existing entries to UTF-8 first, or you ignore the problems with old entries. All new entries should show up fine.

I'm sorry, but I can only suggest you to use UTF-8; without it, you won't be able to solve the XML problems.

Regards,
Garvin