Skip to content
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

Quelea fails to open or save file if path contains unicode characters #646

Closed
kukymbr opened this issue Feb 4, 2024 · 5 comments
Closed
Assignees
Labels
accepted The issue will be worked on by the developers bug Something isn't working
Milestone

Comments

@kukymbr
Copy link
Contributor

kukymbr commented Feb 4, 2024

Quelea fails to save files with Unicode non-latin characters in the path: if file name contains these characters, the file is saved with ? symbols instead of them; if the directory name contains unicode characters, operation is failing at all.

Also, it fails when opening paths with unicode.

Ubuntu 22.04, Quelea 2024.0
quelea-debuglog.txt

@berry120
Copy link
Member

berry120 commented Feb 4, 2024

Hmm, is this on Mac? It works for me fine on Windows:

image

If so, there's nothing we're explicitly doing to manage file locations that I can think of that would cause this issue, so I'm tempted to say this is another reason to expedite #641.

@kukymbr
Copy link
Contributor Author

kukymbr commented Feb 4, 2024

Nope, this is Ubuntu 22.04 machine

@berry120
Copy link
Member

berry120 commented Feb 4, 2024 via email

@berry120 berry120 self-assigned this Feb 8, 2024
@berry120 berry120 added bug Something isn't working accepted The issue will be worked on by the developers labels Feb 8, 2024
@berry120 berry120 added this to the 2024.1 milestone Feb 8, 2024
@berry120
Copy link
Member

berry120 commented Feb 8, 2024

@kukymbr This should now be fixed in the CI release - as part of the Java 21 / OpenJFX 21 upgrade work we now use GTK3 which supports & uses UTF-8 by default.

@berry120 berry120 closed this as completed Feb 8, 2024
@kukymbr
Copy link
Contributor Author

kukymbr commented May 12, 2024

Checked this, works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted The issue will be worked on by the developers bug Something isn't working
Development

No branches or pull requests

2 participants