Georgy Kibardin wants to merge 3 commits from /u/shashurup/isync/ to master, 2022-06-20
No more cryptic UTF7 folder names! By default it is not enabled, so backward compatibility is preserved.
Commit | Date | |
---|---|---|
[1f020b]
(utf8-mailboxes)
by
Georgy Kibardin
Print synchronization summary when progress isn't reported |
2018-09-15 14:28:31 | Tree |
2018-09-15 10:31:46 | Tree | |
[63407f]
by
Georgy Kibardin
Support for UTF-8 mailbox names There is new config parameter UseUTF8Mailboxes which tells isync to decode IMAP |
2018-08-31 12:32:59 | Tree |
i've been pondering this previously, and found that it would be quite some effort, because technically we need to transcode to/from whatever the system locale dictates. you just chose to use utf-8, which is probably the right choice nowadays, at least on unix, but presumably it would be a good idea to at least check whether the locale does indeed use utf-8.
i don't know how anyone could seriously use the non-decoded names, so it seems kinda pointless to make this optional, especially as this is part of the IMAP spec itself.
i haven't really reviewed the implementation; i'll get to it later.
what i can already say is that the indentation and coding style in general are completely wrong.
Oswald Buddenhagen writes:
I've been thinking about implementing this correctly, i.e. taking into
account system locale, however, as you mentioned, it would require to
put some effort on this, especially identifying non-unicode encodings
and deciding what to do with it. Also many people run it as root which
is usually just "C" locale. So I just wanted to make it work.
The reason to make it off by default is compatibility. I'm not sure this
option won't break existing configuration.
I'll take a look. I haven't done plain C for years and it looks like I
unconsciously picked up more recent C++ habits.
Do you have a progress on the issue? It is very unconvinient to use isync with non-ascii2 folder names (e.g. cyrillic folder name).
Would very like to see this merged.
For the locale let's put it this way, what happens if your locale don't support UTF-8, well... you get a name as cryptic as with UTF-7. But the point is nobody uses UTF-7 as a locale, but many uses UTF-8.
UTF-8 could be the default translation target, and you could make an other translation target optional into the config file (per maildir store), as Georgy Kibardin says it would be pointless to look at the current locale as it could be different from the locale of the user.
Last edit: Aurélien Rouëné 2021-01-09
Hi, just expressing my support on implementing/merging this.
Using UTF-8 is about diversity and inclusion, just like using far/near instead of master/slave. People have different languages with different symbols and they shouldn't have to rename their folders to comply with the English alphabet.
Last edit: Someone 2021-07-02
Hello,
Just expressing my support on this MR.
Also wanted to share with @shashurup and others a small fix that is needed for me:
without this fix I have a decoding error, you can check it with this small program:
Unpatched, the output is:
Patched, the output is:
Hi Ludovic!
Thank you for the fix!
Merged.
Hello, I'm here expressing my support on merging this too. My email provider also uses UTF-8 encoding for names of mail boxes and the problem is that I can't rename them. I really like how fast and lightweight isync is, there is only one missing piece for me (not only for me I bet) - this feature. Please add this, it fixes my names too :)
Thank you for your work on isync!
i've merged a significantly modified version of this as 52c063fd45.