-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Waypoint name encoding utf-8 does not work #6
Comments
Thanks for your comment. This is the intended behaviour of the module. Many of the GPS devices using *.gpx files do not support Unicode so invoking HTML::Entities allows for the use of many accented characters in various languages. When I open foo.gpx with GPS software (e.g. Garmin's Basecamp) and on my device, the waypoint turns up properly. Of course, a drawback of that design is that searching waypoints based on its name with the module's methods can be trickier -- e.g. waypoint_search() -- but not breaking compatibility with devices is more important. |
The issue is that WHEN you open it with a utf-8 capable client its broken. For example OSMAnd. Flo |
Can you provide a link to the application or web services you are using so
I can try to reproduce.
Thanks.
Le dim. 2 juin 2024 à 11:26, Florian Lohoff ***@***.***> a
écrit :
… The issue is that WHEN you open it with a utf-8 capable client its broken.
For example OSMAnd.
The XML Envelope advertises utf-8, but contains only US-ASCII + HTML
Encoding.
Flo
—
Reply to this email directly, view it on GitHub
<#6 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHICOWTGEMSPEJVYRTR44QLZFM2SFAVCNFSM6AAAAABGSLTA2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTHA4TSNBWGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
In the original opening there is a testcase - I switched away from using Geo::Gpx because i could not work around as using HTML::Entities->encode_entities is unconditional - So i created the GPX myself using XML::TreePP Here is the script i was creating while stumbling on the Bug. I used to open the GPXes with OSM |
"In the original opening there is a testcase": see my reply to the opening of yesterday. Where in the OSM interface do you open a *.gpx files? I use OSM but never opened a file with it. |
... from https://www.openstreetmap.org/traces I can open a Track from a *.gpx but not just waypoints. Importing results in failure when the *.gpx file has only waypoints and no tracks -- not an encoding issue, it fails with just plain characters in the name:
|
Not OSM/OpenStreetmap - OSMAnd - ist a Mobile App able to show GPX tracks, or use the GPX Track Waypoint as Markers. See the link to the Android App Store. |
Yes I have it.
Le lun. 3 juin 2024 à 11:12, Florian Lohoff ***@***.***> a
écrit :
… Not OSM/OpenStreetmap - OSMAnd - ist a Mobile App able to show GPX tracks,
or use the GPX Track Waypoint as Markers.
See the link to the Android App Store.
—
Reply to this email directly, view it on GitHub
<#6 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHICOWRNR5R3UTDMJYGLI4LZFSBVZAVCNFSM6AAAAABGSLTA2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVGQ3DEMRVGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
As reported by @flohoff in Debian Bug #1069657:
The text was updated successfully, but these errors were encountered: