You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, on devices with Persian locale, by exporting tracks as GPX, time stamps and file names use Perso-Arabic digits and this makes some difficulties to read generated GPX files later. For example some softwares don't understand Perso-Arabic digits and omit them or some other can't open them because of file name.
example:
file name: ۲۰۰۰-۰۱-۰۱_۱۰-۰۱-۰۲_۲۰۰۰-۰۱-۰۱_۱۰-۰۱-۰۲.gpx
part of content:
<wpt lat="37.13575057" lon="49.68532362">
<ele>47.0</ele>
<time>۲۰۰۰-۰۱-۰۱T۱۰:۳۸:۲۰Z</time>
<name><![CDATA[نانوایی لواش]]></name>
<cmt><![CDATA[دقت: 6.067999839782715م]]></cmt>
<sat>14</sat>
</wpt>
<trk>
<name><![CDATA[با OSM Tracker for Android™ ضبط شده است]]></name>
<trkseg>
<trkpt lat="37.2766247" lon="49.93418447">
<ele>-8.0</ele>
<time>۲۰۰۰-۰۱-۰۱T۱۰:۲۰:۱۱Z</time>
<extensions>
<speed>4.820000171661377</speed>
</extensions>
</trkpt>
The text was updated successfully, but these errors were encountered:
Hi, on devices with Persian locale, by exporting tracks as GPX, time stamps and file names use Perso-Arabic digits and this makes some difficulties to read generated GPX files later. For example some softwares don't understand Perso-Arabic digits and omit them or some other can't open them because of file name.
example:
file name:
۲۰۰۰-۰۱-۰۱_۱۰-۰۱-۰۲_۲۰۰۰-۰۱-۰۱_۱۰-۰۱-۰۲.gpx
part of content:
The text was updated successfully, but these errors were encountered: