Always write consistent .gpx filenames

[jidanni]

Please always write consistent .gpx filenames.

$ find * -name \*.gpx
2017-02-03_08-18-49/2017-02-03_08-18-49.gpx
2017-02-03_08-34-46/2017-02-03_08-34-46.gpx
2017-02-03_08-35-34/2017-02-03_08-35-34.gpx
2017-05-11_15-28-44/2017-05-11_15-28-44.gpx
2017-05-11_15-34-11/2017-05-11_15-34-11.gpx
2017-05-11_15-50-45/2017-05-11_15-50-45.gpx
2017-05-16_16-43-59/May_16,_2017_16;43;59_2017-05-16_16-43-59.gpx
2017-05-17_05-50-17/May_17,_2017_05;50;17_2017-05-17_05-50-17.gpx
2017-05-17_07-00-14/2017-05-17_07-00-14.gpx
2017-05-23_08-03-21/2017-05-23_08-03-21.gpx
2017-05-23_08-33-26/2017-05-23_08-33-26.gpx
2017-05-23_08-44-19/2017-05-23_08-44-19.gpx
2017-05-23_09-13-18/2017-05-23_09-13-18.gpx
2017-05-26_07-29-25/2017-05-26_07-29-25.gpx
2017-05-26_09-04-43/2017-05-26_09-04-43.gpx
2017-05-27_05-47-47/2017-05-27_05-47-47.gpx
2017-05-29_10-50-38/2017-05-29_10-50-38.gpx

No I have no idea why there are two odd ones.
Did I press a different button to generate them?

[nguillaumin]

I believe it's related to the setting controlling how to name the GPX files. The default option is "Name, start date and time", so for the case like 2017-05-16_16-43-59/May_16,_2017_16;43;59_2017-05-16_16-43-59.gpx it's because the track name is actually May_16,_2017_16;43;59 (Colons are replaced by ; to avoid issues on Windows where the colon is a reserved character, same with spaces replaced by _ although those should work in practice).

I suspect that happened because you saved the default name proposed for a track when editing its details, which is the date and time. When a track is not named it will just use its date and time (as in 2017-02-03_08-18-49/2017-02-03_08-18-49.gpx). If the track had a proper name, it would be 2017-05-16_16-43-59/My_Road_Trip_2017-05-16_16-43-59.gpx.

So I guess while it may be a bit surprising in some edge cases, it's working as intended.