KDE-SIG meeting report (08/2012)

[Michal Hlavinka]

On 02/23/2012 11:32 AM, Jaroslav Reznik wrote:
> Brno FAD wrap-up
> * new colored systray icons for 4.8, done, not uploaded yet by kkofler
> * update of git-cola in Fedora to latest upstream, done in Rawhide, in updates-testing for F1[567] by kkofler
> * Solid udisks2 front, a first compilable version was finished and pushed to kdelibs git by ltinkl
> * plasma-active packaged by jreznik and rnovacek
> * Qt 5 talk by jreznik

Regarding Qt 5 - is it still early enough for bigger changes?
In Qt 4 there is ugly bug:
https://bugs.kde.org/show_bug.cgi?id=165044

This bug was closed wontfix (and because of heated discussion, bug 
assignee removed himself from cc list), after some time they changed 
resolution to "upstream" which just means "wontfixed in upstream".

There is also
http://www.macieira.org/blog/2011/09/qurl-in-qt-5-encoding/
where this is going to be fixed in QUrl (if I read it correctly), but 
Thiago said the same again - file names with broken (non-utf-8) encoding
are filesystem corruption and applications creating such files should be 
fixed.

It's nice theory, but even in 2012 (4 years after the bug was reported) 
those files still happen to exist. One (not the only one) possible 
source are archives with old files. This is how I met with this bug for 
first time. My gf got some slides from professor packed inside a zip 
file. Once you unzip this file (doplhin - rightclick file - extract 
here) you get files you can't open, rename nor delete. You can delete 
whole folder (it's just moved to Trash bin), but you can't empty your 
trash afterwards. AFAIK all other DE and all other operating systems can 
handle such files without any problem. Only Qt (and KDE) apps can do 
nothing with them.

For testing purposes you can generate such files using konsole -> switch 
to different encoding (like iso-8859-2), and create some file using 
non-ascii letters and try to do anything with such file in doplhin.

I hope there is still a chance to fix this Qt bug.