Bug 381846 - Can't render to filename inside a directory with non-ascii characters
Summary: Can't render to filename inside a directory with non-ascii characters
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: Rendering & Export (show other bugs)
Version: 16.12.2
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-01 06:18 UTC by Jean Chalard
Modified: 2018-12-15 16:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
fritzibaby: timeline_corruption+


Attachments
Screenshot of the error I'm getting (28.51 KB, image/png)
2017-07-01 06:18 UTC, Jean Chalard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jean Chalard 2017-07-01 06:18:26 UTC
Created attachment 106396 [details]
Screenshot of the error I'm getting

Repro steps :
- Have a project, anything will do.
- Open the render dialog.
- Give a filename inside an existing directory with Japanese characters in it.
- In the name for the target file, use a file name with Japanese characters, e.g. "/tmp/テスト/a.mp4".
- Try to render.

Expected : File renders as usual to the filename.
Actual : Error on opening the target file : Cannot write to <filename>, check permissions. Note that in the error, the Japanese characters are replaced with question marks. Screenshot attached.

Additional notes :
・ The system locale is correctly configured. en_US.UTF-8 everywhere since install, ext4 filesystem, and filenames in Japanese are rather common on my machine and working in every application, including KDE apps (and including kdenlive for anything else than rendering, e.g. it has no problem adding such a file as a source clip to the project bin).
Comment 1 Jean Chalard 2017-07-01 06:20:28 UTC
Oh and of course I have permissions to read/write/traverse this directory. Whether an existing (writable) file exists there also makes no difference.
Comment 2 emohr 2018-12-10 16:38:17 UTC
Do you still encounter this problem?
Comment 3 Jean Chalard 2018-12-15 16:24:39 UTC
No I don't. I just tried and now it works as expected.
I'm using it on the same machine I used to, and the version is still listed as 16.12.2.
I have no idea what changed :/

Anyway, thank you.