I am still working on the foreign character display problem in this php
created RSS newsfeed
and i know one thing for SURE
on my other feed i create all by hand in my Quanta plus html editor ..
http://www.kriyayoga.com/rss/love.rss
ALL is perfectly displayed and validated
after MANY hours of searching and configuring and reconfiguring this
blog created php newsfeed
i find that creating by hand is zero problem
all foreign German characters are fully correct
that means
the problem has to do with the fact that
php uses a database which is stored in a undefined format or a format
out of my known control in regard to charset for file system and data system
data used to finally create the php created newsfeed com from OTHER than
a plain html editor and html file
are assemble on the fly and very apparently complex to configure as many
posts OUT THERE in www, in forums and blogs deal with these many charset
and validation problems
while a hand created RSS newsfeed apparently is baby easy to make
i published the very same minutes ago by hand in my other feed
and all looks perfect to me and in my newsreader as well - all parts,
title, description is displayed in perfect foreign characters - because
its all in one single file - stored in a cleanly configured environment
with clean and fully controllable apache config for encoding and charset
and language ...
while in the php created newsfeed the title - emerging form the email
subject line - is handled differently even though the system wide apache
config is the very same - it may have to do only with the MySQL stored
data ???
Now i know that foreign posts destroy the validation of my RSS news feed
- so i most likely have to post only in English language until i either
have figured out the solution or another blog only for German language
with a totally different apache and sys config or a new host with
different database config.
many problems - but since in my own user space all is working fine -
there is a chance now that either it is a typical php only problem or a
mySQL related problem - both quite a bit out of direct control as i have
NO dedicated server of my own yet - hence exact facts about kernel
charset default configuration is unknown and out of control as well as
system wide configuration is undefined by me and unknown to me ...
the essence is
if you have full control over all factors
all problems easily can be solved
if you depend on other factors and other software that are out of FULL
control and configurability by you
then you either pray and hope all may work
or you are screwed by those things out of reach of your administration
life only is easy if ALL is under your own responsibility and direct
personal access
!
there are many pros for using CMS - but as i hve seen
manual publication sometimes is 10 to 1000 times faster, more efficient
and MORE PRECISE - more accurate because every bit and byte can be
controlled by every knowledgeable and skilled pro. While opposed to that
manual control - in CMS most or all is controlled by the programmer /
developer who created the CMS software. if HE forgot any single
combination of possibilities of handling data in ANY way and all
possible ways for all possible presentation formats
then we have a mess totally out of control
love and bliss
hans