Bug 155476 - 'Store on server' garbles filenames from unixoid sources (Linux & probably MacOSX, xxxBSD)
Summary: 'Store on server' garbles filenames from unixoid sources (Linux & probably Ma...
Status: UNCONFIRMED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.3.7.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: QA:needsComment
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-24 17:22 UTC by hpheidinger
Modified: 2023-06-08 03:15 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hpheidinger 2023-05-24 17:22:15 UTC
Description:
LibreOffice (here: Writer 7.3.7.2 on Fedora 36) treats all (source-)file-names as if they would come from a MicroSoftish Windows box, if one transfers stuff to a server with the 'File -> Store on server' function.
I.e. it splits the file name at the first dot (.) into:
    <name>.<extention>
By this it garbles a source file name 'Watcher-Master-1.4doc' being:
'Watcher-Master-1' with extention '4doc'.
Even worse: It then thinks, that there already is an 'extention' "4doc" and ignores to attach the '.odt' to the end of the target file.

Steps to Reproduce:
1. Create a writer document (odt) with a filename that has probably _several_
   dots (.) in it; e.g. 'Release-notes-1.5.6-Patchlevel-12.8' which has/gets a
   '.odt' ending as it is a 'Writer' document.
   This is absolutely a legal filename on ALL NON-MICROSOFTISH systems.
   (Linux, MacOS, xxxBSD, etc.)
2. Provide a server with a path were files can be stored; 
   e.g. '/var/www/docs/' where the particular user has rigths to store data.
3. Store above file, that you have created in (1.) from within 'Writer' with 
   the 'File -> Store on Server' function.
4. Wonder what you get on the target server ...

Actual Results:
Names of transfered files come out garbled on the target server.

Expected Results:
Above ODT file name 'Release-notes-1.5.6-Patchlevel-12.8' should come out in the target path on the target server as:
'Release-notes-1.5.6-Patchlevel-12.8.odt'
Care should be taken that the '.odt' ending is NOT doubled, even if the user typed-in the '.odt' ending erronously in the file name box and one gets a result like:
'Release-notes-1.5.6-Patchlevel-12.8.odt.odt'


Reproducible: Always


User Profile Reset: No

Additional Info:
There is NO SUCH THING than an 'extention' in filenames, that come from an unixoid OS. A filename can contain ANYTHING EXCEPT a slash (/), since this denotes directories in file-hierarchy on all unixoid platforms.
Filenames are just names + an ending that provides a 'hint' of what it is.