-
Notifications
You must be signed in to change notification settings - Fork 213
UTF-8 calendar names not displayed correctly #649
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
Comments
maybe related to #640? |
No, it isn't related. |
can you show the part of your config file that deals with that calendar? |
khal:
vdirsyncer:
|
Can you make sure khal is using a supported python version? The output of these should be enough: head -n 1 $(which khal)
A="$(head -n 1 $(which khal))" && echo $(which ${A:15})
A="$(head -n 1 $(which khal))" && eval ${A:2} --version |
It's Python 3.6.0. Can you reproduce this on your end? |
No, I can't reproduce this on my end:
(calendar What version of python and khal are you using? What OS and how are those filenames encoded? |
any news on this? |
Sorry, I've lost the config and don't use khal very much lately. But even on your own output the name isn't parsed correctly (khal printcalendars gives 'σωπικό' instead of 'Προσωπικό') I was using OpenBSD 6.0 and Python 3.4 and the then master branch. |
I have a calendar with a greek title, and both in
khal printcalendars
and in the event editor inikhal
I see a blank space instead of the name. Greek event titles appear correctly.In the debug logs, I see
for the greek calendar. And in the config print I get:
I have
metadata = ["displayname", "color"]
in vdirsyncer config but thedisplayname
file doesn't get created.Creating a
displayname
file in the calendar's vdir shows the calendar name. But I have other calendars in ascii with no displayname files and khal deduces their name from the path correctly (I think).The text was updated successfully, but these errors were encountered: