URLs in point descriptions (embraced as CDATA) are not displayed as links
When I import POIs (Points of Interest) into Locus Map Pro (v3.20.1), URLs in the point description are not clickable.
The <desc> element is protected against misinterpretation with a CDATA section like this. The CDATA makes it easier to paste arbitrary content into the XML element.
- <desc><![CDATA[...]]></desc>
Here is an example of two points.
- <wpt lat="9.958177" lon="76.259345"> <name>Mattancherry Palace</name> <desc><![CDATA[https://goo.gl/maps/Y76pbbPFdJF2
Mattancherry Palace was a generous gift presented to the Raja of Kochi, Veera Kerala Varma (1537–61), as a gesture of goodwill by the Portuguese in 1555. The Dutch renovated the palace in 1663, hence its alternative name, the Dutch Palace. The star attractions here are the astonishingly preserved Hindu murals, depicting scenes from the Ramayana, Mahabharata and Puranic legends in intricate detail.]]></desc> <sym><![CDATA[z-favorites]]></sym> <extensions> <gpxx:WaypointExtension> <gpxx:Address> <gpxx:StreetAddress>Mattancherry</gpxx:StreetAddress> <gpxx:City>Stadt</gpxx:City> <gpxx:PostalCode>682002</gpxx:PostalCode> </gpxx:Address> </gpxx:WaypointExtension> </extensions> </wpt>
<wpt lat="9.957477" lon="76.259374"> <name>Pardesi Synagogue</name> <desc><![CDATA[https://goo.gl/maps/6tBrWkU7F9s
Originally built in 1568, this synagogue was partially destroyed by the Portuguese in 1662, and rebuilt two years later when the Dutch took Kochi. It features an ornate gold pulpit and elaborate hand-painted, willow-pattern floor tiles from Canton, China, which were added in 1762. It’s magnificently illuminated by Belgian chandeliers and coloured-glass lamps. The graceful clock tower was built in 1760. There is an upstairs balcony for women, who worshipped separately according to Orthodox rites. Note that shorts, sleeveless tops, bags and cameras are not allowed inside.]]></desc> <sym><![CDATA[z-favorites]]></sym> <extensions> <gpxx:WaypointExtension> <gpxx:Address> <gpxx:StreetAddress>Synagogue Lane</gpxx:StreetAddress> <gpxx:City>Kochi
</gpxx:City> <gpxx:PostalCode>682002</gpxx:PostalCode> </gpxx:Address> </gpxx:WaypointExtension> </extensions> </wpt>
When I open a point, I cannot click on the links in the description (Beschreibung), beacuse they are treated as simple text. See screenshot:
Please make Locus handle URLs in point descriptions as clickable links, even if the descriptions are embraced in a CDATA section in the source GPX.
Good day Johannes,
I do not consider this as an "issue", anyway agree that clickable links should be useful in most cases. Issue/feature will be implemented in next version. Thanks for "idea".
Good day Johannes,
I do not consider this as an "issue", anyway agree that clickable links should be useful in most cases. Issue/feature will be implemented in next version. Thanks for "idea".
Works perfectly in 3.21.0!
Thanks and Merry Christmas! :)
Works perfectly in 3.21.0!
Thanks and Merry Christmas! :)
It turned out that this feature works only if the description contains nothing but a single URL (Locus Pro 3.23.0). If you have a Point or a Track with a description containing both URLs and text, the URLs won't be neither highlighted nor made clickable.
I'd expect all URLs within descriptions to be clickable (and I'm missing this feature).
It turned out that this feature works only if the description contains nothing but a single URL (Locus Pro 3.23.0). If you have a Point or a Track with a description containing both URLs and text, the URLs won't be neither highlighted nor made clickable.
I'd expect all URLs within descriptions to be clickable (and I'm missing this feature).
Good day Johannes,
give me please some "sample file" I may use for a test and I'll look at it. Thanks
Good day Johannes,
give me please some "sample file" I may use for a test and I'll look at it. Thanks
Good day Johannes,
in your files is mess of html code and links without <a href=""> attribute.
If your description contains any html code, it needs to be all as html web page. If you extra content of description into single test.html file, you will see that link won't be clickable as well. So current behavior is perfectly correct.
About description ... result GPX is not broke. It just contain in description copy of statistics so after import back, it may double it's content. I'll think what is possible to do with it, cannot promise any change for now.
Good day Johannes,
in your files is mess of html code and links without <a href=""> attribute.
If your description contains any html code, it needs to be all as html web page. If you extra content of description into single test.html file, you will see that link won't be clickable as well. So current behavior is perfectly correct.
About description ... result GPX is not broke. It just contain in description copy of statistics so after import back, it may double it's content. I'll think what is possible to do with it, cannot promise any change for now.
Thanks gynta!
Because You ( @Johannes ) are not the first who had problems with this unwanted re-import generated description, I've improved this system. In next version, generated description will be covered with html comment. When anyway will try to re-import this point/track back, generated description will be removed and only user's inserted text will be used as a valid description. Thanks for pushing me to do this .. finally.
Thanks gynta!
Because You ( @Johannes ) are not the first who had problems with this unwanted re-import generated description, I've improved this system. In next version, generated description will be covered with html comment. When anyway will try to re-import this point/track back, generated description will be removed and only user's inserted text will be used as a valid description. Thanks for pushing me to do this .. finally.
I recently noticed that names of cache child waypoints are no longer displayed after import.
Something like this works correctly:
<wpt lat="50.519067" lon="14.976917">
<name>QA18W1Z</name>
<desc>Nazev bodu</desc>
<sym>Virtual Stage</sym>
<type>Waypoint|Virtual Stage</type>
</wpt>
But when desc is enclosed in CDATA, the name is empty, like in the attached image. I have the latest version of application 3.24.1.
I recently noticed that names of cache child waypoints are no longer displayed after import.
Something like this works correctly:
<wpt lat="50.519067" lon="14.976917">
<name>QA18W1Z</name>
<desc>Nazev bodu</desc>
<sym>Virtual Stage</sym>
<type>Waypoint|Virtual Stage</type>
</wpt>
But when desc is enclosed in CDATA, the name is empty, like in the attached image. I have the latest version of application 3.24.1.
Replies have been locked on this page!