Opened 13 years ago
Closed 13 years ago
#5049 closed Bug report (invalid)
.txt file not recognized as ASCII for transfer
|Reported by:||jim||Owned by:|
|Component version:||Operating system type:||Windows|
|Operating system version:||XP|
I recently noticed that a .txt file from a Unix machine was download as binary to a windows machine, even though "txt" is in the ASCII file list. The file is named like filename.20091204.165157742.txt. I am guessing that the reason for this is because it sees the text after the first "." as the extension and not the text after the last "." as the extension. I would contend that only the text after the last "." should be looked at for the extension. This is consistent with how windows works (don't know about other OSes).
Change History (1)
comment:1 by , 13 years ago
|Status:||new → closed|
Note: See TracTickets for help on using tickets.
Did some further testing I believe I did not have my client set to "Auto" transfer. Sorry for the false alarm.