Menu

#10 Error in GPX file when exporting with special characters

closed-fixed
nobody
None
5
2010-08-30
2010-08-18
Anonymous
No

When i try to open a GPX file that was previously exported with a description/name containing one of the norwegian special characters æ ø å i get the following error: Error reading file:Invalid byte 1 of 1-byte UTF-8 sequence. Using version 11 build 204.

Discussion

  • activityworkshop

    Confirmed - I'm not sure what's causing this :(

     
  • activityworkshop

    • status: open --> open-accepted
     
  • activityworkshop

    On further investigation, it seems that the following are _all_ necessary to trigger this error:
    - The computer is setup to use a default encoding other than UTF-8 (maybe it's a Windows-only effect?)
    - And the waypoint names or the entered name/description fields for the file contain non-ASCII characters (such as the Danish characters mentioned but also German ones such as ä, ö, ü)
    - And the file is exported to GPX (saving as text still works ok)

    One remedy which might work for you is to open the file in a text editor and change the top line to this:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    This may fix the problem, depending on your computer's default file-encoding, and would allow Prune (and other programs) to open the file again.

    A proper fix will be for Prune to examine what the default file-encoding is, and write the appropriate code into the top of the file.

     
  • activityworkshop

    • status: open-accepted --> closed-fixed
     
  • activityworkshop

    Fixed with version 11.1 - please test

     
MongoDB Logo MongoDB