Opened 17 years ago
Closed 13 years ago
#1839 closed defect (worksforme)
KML Driver rev12157 - Description string content not escaped properly
| Reported by: | darkblueB | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | OGR_SF | Version: | unspecified |
| Severity: | normal | Keywords: | kml |
| Cc: | Mateusz Łoskot |
Description
(relates to #1791 and previous)
Steps: convert KML file minPlusDesc.kml to SQLite convert SQLite to KML
Notice that the Description html tags are not completely converted (>) and the resulting HTML display is now mangled
Attachments (1)
Change History (3)
by , 17 years ago
| Attachment: | minPlusDesc.kml added |
|---|
comment:1 by , 16 years ago
| Cc: | added |
|---|
comment:2 by , 13 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I think it is perfectly normal that the Description html tags are escaped in KML output. Just look at http://code.google.com/apis/kml/documentation/kml_tut.html, section "Descriptive HTML in Placemarks". We have two possibilities : output as "good-looking" HTML within CDATA, or output, as we do, as escaped strings. output.kml returned by "ogr2ogr -f KML outpout.kml minPlusDesc.kml" works well with Google Earth (I didn't try with the SQLite intermediate)