Delta Chat treats a part of file name as an extension #5338
Comments
|
Search for the last dot (file name extension) from the end of the file name backwards. |
|
Should be done in the scope of #4309. We will save the original file name which is passed in the message, so both sides will see it. Looks like the source of the problem is using the |
|
ftr, for the extensions there was some discussion at #3227 - which is probably also the reason for the lowercasing in this issue as all of indeed, it is better to preserve the name completely, and do all comparisons case-insensitive; #4309 may indeed help on that. however, that needs to be done carefully, with tests and all, to not open larger issues in any case, it seems there is not much desktop can do about this issue, so we can close it if it is included in (#4309 here, otherwise, we should move the issue to core |
iequidoo
changed the title
…pace (#5338) Before file extensions were also limited to 32 chars, but extra chars in the beginning were just cut off, e.g. "file.with_lots_of_characters_behind_point_and_double_ending.tar.gz" was considered to have an extension "d_point_and_double_ending.tar.gz". Better to take only "tar.gz" then. Also don't include whitespace-containing parts in extensions. File extensions generally don't contain whitespaces.
…pace (#5338) Before file extensions were also limited to 32 chars, but extra chars in the beginning were just cut off, e.g. "file.with_lots_of_characters_behind_point_and_double_ending.tar.gz" was considered to have an extension "d_point_and_double_ending.tar.gz". Better to take only "tar.gz" then. Also don't include whitespace-containing parts in extensions. File extensions generally don't contain whitespaces.
…pace (#5338) Before file extensions were also limited to 32 chars, but extra chars in the beginning were just cut off, e.g. "file.with_lots_of_characters_behind_point_and_double_ending.tar.gz" was considered to have an extension "d_point_and_double_ending.tar.gz". Better to take only "tar.gz" then. Also don't include whitespace-containing parts in extensions. File extensions generally don't contain whitespaces.
…pace (#5338) Before file extensions were also limited to 32 chars, but extra chars in the beginning were just cut off, e.g. "file.with_lots_of_characters_behind_point_and_double_ending.tar.gz" was considered to have an extension "d_point_and_double_ending.tar.gz". Better to take only "tar.gz" then. Also don't include whitespace-containing parts in extensions. File extensions generally don't contain whitespaces.
…pace (#5338) Before file extensions were also limited to 32 chars, but extra chars in the beginning were just cut off, e.g. "file.with_lots_of_characters_behind_point_and_double_ending.tar.gz" was considered to have an extension "d_point_and_double_ending.tar.gz". Better to take only "tar.gz" then. Also don't include whitespace-containing parts in extensions. File extensions generally don't contain whitespaces.
On Desktop I attached a file to the message. Filename: "Chor St. Otto Bismarck - Mitglieder.html".
But the attached file was renamed to "Chor St.otto bismarck mitglieder.html".
Seems that changes happens after the first dot instead of the last one. Problem happens when more than one dot is in the file name.
Solution could be to find the last dot by searching the dot from the end of the file name.
The text was updated successfully, but these errors were encountered: