Bug 137433

Summary:	LO in Linux incorrectly saves filenames
Product:	LibreOffice	Reporter:	lachend
Component:	LibreOffice	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED NOTABUG
Severity:	normal	CC:	lachend, libreoffice-ux-advise, lo_bugs
Priority:	medium	Keywords:	needsUXEval
Version:	7.0.2.2 release
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
Crash report or crash signature:		Regression By:

Description lachend 2020-10-12 18:36:28 UTC

Description:
LO in Linux can save files starting with ? and & signs.

Steps to Reproduce:
1. Create a file.
2. Try to save its filename starting with "?" sign or other characters, restricted in Windows systems.
3. It saves.

Actual Results:
LO can save files starting with ? and & signs.

Expected Results:
Saving filenames should be restricted with first ?, & or other symbols, that won't be read by other systems or mailers.


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.0.2.2
Build ID: 8349ace3c3162073abd90d81fd06dcfb6b36b994
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: kf5
Locale: uk-UA (uk_UA.UTF-8); UI: en-US
Calc: threaded

Comment 1 Terrence Enger 2020-10-19 16:16:20 UTC

As much as I myself dislike special characters in filenames, I am not
convinced that the reported behaviour is wrong.  I am adding keyword
needsUXEval.

Comment 2 Heiko Tietze 2020-10-22 09:00:58 UTC

Clearly a bug to me. It's possible to name a file "?Untitled 1*" and actually it is saved properly. And surprisingly Kate (text editor), GIMP, Inkscape, and WPS allow wildcards while Blender converts it to underscore (you have to press Save twice).
Even a "touch ?test*" works.

Not sure that we need to block it. Let's keep as it is.

Comment 3 lachend 2020-10-22 09:20:12 UTC

I define this as a bug, because program behavior should be the same in different OSes.
When I (suggesting newbie unix user) send a file to Windows user, he (she) won't open it.
Possibilities of each filesystem - is another question.
For this reason, a restriction to 'naming' in LO should be bypassed by possibilities of user's filesystem.