>>>>> "RL" == Robert Lipe <robertlipe@...> writes:
RL> Working as intended.
RL> GPX doesn't have a way to specify if those fields are HTML or not.
RL> Kml always allows HTML there. We have to entity encode them.
You are not entity encoding them.
You are just not entity decoding them.
Or you are yes just leaving them alone, however still slapping a
CDATA holder around them.
So maybe don't slap the CDATA wrapper, and everything would be fine.
Or if you do, first decode any entities.
I personally don't have much of a real grip on what is wrong actually.
All I know is I was given a GPX file with
which becomes in KML
So I had do decode it with the programs you see there in
One might explore
Substitute CDATA section by equivalent text nodes.
But that would just doubly encode things.
needs a new option,
because as you say,
the program doesn't know which kind of input it is getting,
so give the user a way to tell it...