Bug 324966

Summary:	Applications don’t open file when called with a filename that contains certain characters
Product:	kde-windows	Reporter:	Lukas Sommer <sommerluk>
Component:	general	Assignee:	KDE-Windows <kde-windows>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	adaptee, sommerluk
Priority:	NOR
Version:	4.10
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:

Description Lukas Sommer 2013-09-16 16:21:05 UTC

Applications don’t open file when called with a filename that contains certain characters.


Reproducible: Always

Steps to Reproduce:
1. Have a PDF file with a filename that contains the character U+2010 (typografic hyphen).
2. Open Windows Explorer or Dolphin and go to the directory that contains this file.
3. Open the file from Windows Explorer or Dolphin.

Actual Results:  
You get an error message: “<filename> can’t be opened.” Okular doesn’t open the file.


Expected Results:  
Okular opens the file without problems.


The problem is KDE specific. It’s not a problem of Windows. Adobe Acrobat Pro and PDF XChange Viewer open the file without problems.

This bug isn’t specific to Okular, but also occurs with other KDE programs. Example: Opening a .txt file (who’s filename contains the character U+2010) in kwrite. Error message: “The file <filename> couln’t be loaded because it isn’t readable. Please review your access rights.”

I asume this is not specific to the character U+2010 either, but also occurs with other unusual characters?!

I’m using Okular 0.16.2, MinGW 4 64 bit.

Comment 1 Jekyll Wu 2013-09-19 06:50:03 UTC

Can't reproduce the problem with the U+2010 character .

Comment 2 Lukas Sommer 2013-09-27 07:48:21 UTC

I’m using Windows 8.

Comment 3 Lukas Sommer 2013-09-28 08:55:29 UTC

When opening KWrite or Okular first, then going through menu→file→open, then I can choose files with a U+2010 in the filename and the program opens them correctly.

The bug only occurs when opening a file using the file manager.

Comment 4 Jekyll Wu 2013-09-30 16:36:23 UTC

Strange, I just can't reproduce the problem under any condition.

Comment 5 Andrew Crouthamel 2018-11-10 03:21:23 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Andrew Crouthamel 2018-11-21 04:45:19 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!

Comment 7 Justin Zobel 2023-01-13 01:36:06 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 8 Lukas Sommer 2023-01-13 08:44:28 UTC

Cannot reproduce.