New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filename for Note can contain "forbidden" characters #126

Closed
workflowsguy opened this Issue Mar 31, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@workflowsguy

workflowsguy commented Mar 31, 2016

When creating a new note, the first line is used as the file name.
If this line contains non-letters or non-digits, this can lead to unallowed characters in the file name.

E.g.
if the first line contains

EyeTV: zu automatisierende Funktionen

the resulting file will be named

EyeTV/ zu automatisierende Funktionen.txt

which will cause problems when opening. I am experiencing this on OS X.
I would suggest replacing those problematic characters with an "_".

Thanks,
Guy

@pbek

This comment has been minimized.

Owner

pbek commented Mar 31, 2016

Thank you for the report!

There are no problems here with EyeTV: zu automatisierende Funktionen on Linux. Neither are there any problems with it when creating such a note with the ownCloud notes app. Are you using ownCloud too? If yes, could you please be so kind to test it on our instance?

I will later test it on OS X.

@pbek

This comment has been minimized.

Owner

pbek commented Mar 31, 2016

Yes, under OS X the file will be named like you said, but I had no troubles opening it with QOwnNotes or TextEdit. What problems are you perceiving?

@pbek pbek added this to the 1.3.4 milestone Apr 3, 2016

@pbek

This comment has been minimized.

Owner

pbek commented Apr 3, 2016

Characters like :, / and \, as well as multiple whitespace characters will now be removed from the note file name if the first line of the note is containing them in version 1.3.4. Can you please test if this solves your problems?

@pbek pbek closed this Apr 3, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment