File format war

At work, I’m currently helping out with a report. In our department, there is a mix of different OSes en office suites, mainly Mac OS X (MS Office 2008), Windows (Office 2003) and Linux (OpenOffice.org 2.4 and 3.0). Because of this, I very often get involved in the office file format mess these days.

Mac and Windows users never have heard of things like open standards and OpenOffice.org. They use whatever is used by default by their MS Office suite, which generally gives either proprietary doc files or docx files which are in practice almost as proprietary as doc (office 2008 docx definitely is not OpenXML!). While doc is pretty universal, docx is much more problematic, because it makes MS Office 20O3 users on Windows complain (of course they have never heard of the docx plug-in for Office 2003), and also OpenOffice.org does not know this file format perfectly yet (although it’s already good and very usable).

Microsoft admitted that OpenXML has lost the standard war. Unfortunately, I have the feeling that proprietary docx has won. The number of times I have received an OpenDocument file can be counted on one hand, but I see fairly often docx files passing here…

Anyway, I’m happy with OpenOffice.org: it can open all of the involved file formats, and can save in a format which everyone can read (which is unfortunately MS Office 2000/XP/2003 DOC/XLS/PPT formats). Now I should go find a way to get OpenOffice.org a bit more generally known on the department…

Hiding failure thanks to photo editing

Today, there were two funny pictures in the newspaper. You’ve surely seen the picture of 4 Iranian missiles which were launched recently in Iran. It appears that the pictures have been edited to hide the failure of one of the missiles: on the original picture one of the missiles is still on its launch pad. Apparently on the Iranian TV, yet another edited version was shown: on that picture the launch pad with the missle has been removed completely. This and other funny photo editing failures can be found in the Photoshop Disasters blog.

15 great music albums

About two weeks ago, I bought 15 music albums from an action by a Belgian newspaper. Those are 15 albums which take up an important place in the modern pop and rock history:

  • Oasis – (What’s the Story) Morning Glory?
  • The Police – Regatta de Blanc
  • dEUS – In A Bar, Under The Sea
  • Radiohead – OK Computer
  • Coldplay – A Rush of Blood to the Head
  • Lou Reed – Transformer
  • Michael Jackson – Thriller
  • Bob Dylan – Highway 61 revisited
  • Dire Straits – Brothers in Arms
  • Lenny Kravitz – Mama Said
  • David Bowie – Ziggy Stardust
  • The Cure – Seventeen Seconds
  • Eurythmics – Sweet Dreams (Are Made of This)
  • R.E.M. – Murmur
  • Eric Claptop – 461 Ocean Boulevard

I have been enjoying these albums a lot during the last two weeks. It’s difficult to choose which ones I like best. But if I really try: Oasis, Radiohead, Coldplay, Dire Straits, Lenny Kravitz. It is such a shame I did not had any of those great albums before!

Distrowatch: Mandriva is the winner distribution of the first half of 2008

“Distrowatch.com called Mandriva 2008.1 (Spring) “the distribution that found the best balance between features and stability“. Compared to Fedora 9, Ubuntu 8.04 and OpenSUSE 11.0, “once again, Mandriva seems to be a winner here, earning high marks from both the reviewers and the users on various forums for its 2008.1 release”.

It’s a great thing that an authoritative site like distrowatch.com is recognising Mandriva’s work lately. Still, it’s extremely difficult to pass this message to the public with all the (in my opinion greatly exaggerated) Ubuntu marketing and hype…

Getting nice anti-aliased fonts in Debian

Since about a year I’m using Debian on an Apple Powerbook G4 PowerPC laptop. Mandriva does not have an active PowerPC port anymore, I don’t really like Ubuntu (and their PowerPC port does not get the same priority anymore as the x86 ports), so Debian was an obvious choice for me, and I have never regretted this.

One of the things that annoyed me however, was the default looks of fonts. Some fonts (especially in Firefox) did not look anti-aliased, while those that were, did not look as nice as I’m used to from Mandriva. At that time, I did not found anything better than compiling a more recent version of freetype (just standard ./configure, make, make install, no patches for enabling any patented stuff) and replacing the contents of /etc/fonts/conf.d by the one from a Mandriva system. And installing the Liberation fonts from Red Hat’s tarball.

Today, things are a bit easier: a Liberation package is now available in the Debian repository as are up to date packages of Freetype. And I learned a bit more about Debian’s Freetype configuration, so I was able to tweak the default settings now, instead of just replacing everything by Mandriva’s.

Here’s a quick howto. I assume you are using Debian Lenny, and have the unstable/sid repositories added to apt’s sources.list (use apt pinning so that testing is preferred over unstable).

  • Make sure you have the basic font packages installed: apt-get install ttf-dejavu ttf-liberation (the latter currently only exists in unstable)
  • Make sure you have a recent version of freetype installed. Run apt-cache policy libfreetype6 to see which versions are currently available in Debian. I installed version 2.3.6 from Unstable: apt-get install -t unstable libfreetype6
  • Install a recent fontconfig version. Run apt-cache policy fontconfig to see which versions are available. I installed version 2.6.0 from unstable: apt-get install -t unstable fontconfig libfontconfig1 fontconfig-config
  • Go the the directory /etc/fonts/conf.d. You’ll see that it contains all symbolic links to /etc/fonts.conf.avail which contains some more interesting configuration files which we’ll activate by adding a symbolic link. Especially I want to use the autohinter, enable RGB subpixel hinting and don’t want to use bitmap fonts:
    ln -s ../conf.avail/10-autohint.conf<br/>
    ln -s ../conf.avail/10-sub-pixel-rgb.conf<br/>
    ln -s ../conf.avail/70-no-bitmaps.conf
  • Now in GNOME go to the menu System – Preferences – Appearance and go to the Fonts tab and play a bit with the settings until you are happy with them. I used Deja Vu Sans Book 9pt for desktop and application fonts and Liberation Mono 9pt as fixed width font. Rendering is set to subpixel smoothing, and in the details panel I chose suppixel (LCD) smoothing, full hinting and RGB subpixel order. If you are using KDE 3, you can make similar settings in KDE’s Control Center under Look & Feel – Fonts (make sure anti-aliasing is enabled and click on the Configure button).
  • In Firefox/Iceweasel 3 go to Edit – Preferences – Content and click on the Advanced button in the Fonts & Colors section. Configure the fonts you like best (I chose Liberation fonts, and set sans-serif by default) and play a bit with the default and minimum font size (I chose 15 pt as default size, and 9 pt as minimum).

Enjoy your nice fonts!

KDE 4.1 beta 2 bug status

This week-end, I installed KDE 4.0.83 also known as 4.1 beta 2. Here’s a quick round-up of issues I reported:

Looking at the bugs of previous weeks, those are fixed now:

So in total, this means 4 out of 31 bugs reported during the last two weeks are fixed now. Unfortunately, most other bugs did not see much progress at all: either they are considered as feature request for KDE 4.2 or later, either they are completely ignored, either the only progres is that the developer says it is working for him, even if I can easily reproduce these bugs. I could not find the feature “folder view widget used as desktop”, which is really needed in my opinion, so it seems indeed that this is only a KDE 4.2 feature, as was suggested in an earlier comment on this blog. Together with all other bugs/feature requests for Plasma I reported, I am still convinced that Plasma is not mature enough today to be used in a production environment by non-geeks.

KDE 4.0.82 beta testing report

This week-end I upgraded my KDE 4 test installation to KDE 4.0.82, which is now included in Mandriva Cooker. Time to follow up on the bugs I reported last week and to take a deeper look at Plasma, the new desktop concept introduced in KDE 4.

KDE 4.1 desktop with Dolphin

Plasma

The good news is that the Folder View widget, which is used to display desktop icons, has been fixed so that right clicking on a file now gives a meaningful menu. So finally you can easily trash or rename icons in the folder view widget or execute other common actions for normal files.

However, the more I use KDE 4, the more problems I see with this whole Plasma thing. Especially the Folder View widget is problematic, not only because of bugs, but especially because the whole thing works rather counterintuitively.

In other desktops (including KDE 3.5, GNOME and XFCE), icons can be placed on the whole desktop surface and those files and application launchers are saved in the ~/Desktop directory. KDE 4 takes a radically different approach. All items on the desktop are Plasma widgets. Plasma widgets can be small applications (like an RSS readers or a clock) but also file and application launchers and they do not correspond with a file in ~/Desktop. To circumvent this limitation, the folder view widget was created. It’s actually a widget which shows all the files in a certain directory. By default, a folder view widget showing the contents of the directory ~/Desktop is added to the desktop. This creates a highly confusing situation:

  • Because the contents of ~/Desktop is not shown over the whole desktop but only in a widget, files in ~/Desktop can only be shown on a limited area on the desktop.
  • All widgets get some sort of transparent overlay over the desktop wallpaper. In my opinion, this looks ugly. It creates unnecessary complication, while it is not aesthetically pleasing to my eyes, because it ruins the background too much.
  • There are now two different ways of creating items on the desktop: either by creating a separate plasma widget which represents a file or application launcher, either by putting the file or application launcher in the the ~/Desktop directory.

Because of this fundamental change and some bugs which worsen the situation, very strange things can happen:

  • Moving files or applications to or from the visible desktop folder view widget does not work at all,
  • Move a file from KDE’s program menu to the desktop, outside of the folder widget. A Plasma widget representing the program is created at the location where you dropped it, however it only shows the “broken” icon. The application name is ellipsized to three letters. At the same time the icon is also added to the folder view widget, so there are now two desktop icons…
  • I could drag and drop a Kopete avatar image file to the desktop, so that a Plasma widget was created. There was no way to copy or move this file to another location any more, so I could access it somewhere with my file browser…
  • When moving a file to the desktop, in the past this moved the file to ~/Desktop, so you could easily find the file there in all applications. Now the file is not moved anymore, but a Plasma widget linking to that file is created. That means that in applications, you can’t find the file anymore in ~/Desktop, although the file is shown on your visible desktop.

Even with the impossibility of dropping files on the folder view widget and the double icons when dropping outside the folder view widget fixed, the two different type of icons on the desktop, will be very confusing for users. At work there are users who are constantly using the desktop for saving files. If there does not come a complete rethinking of the way the desktop is implemented in KDE 4, I am planning on migrating these users to GNOME instead of KDE 4, because this Plasma thing will cause too much support interventions because ueser won’t find their documents anymore.

Half of the Plasma widgets are still not working for me. The most widgets, only show a grey area when I drop them on my desktop and I still could not add the Show Desktop widget to the panel.

Changing the size of a Plasma widget neither is very intuitive. You have to click on the resize icon which appears normally at the left upper side of the widget (but this can be the right side too, if your widget is near the left side of the screen!), and then the widget will be expanded or reduced around the centre of the widget. This is of course very annoying if your widget is already near the side of the screen, as this means you’ll probably have to move the widget too. I don’t understand why the same idiom of resizing and moving application windows was not reused.

Other problems

There has not been much progress in my bug reports of last week. Most remain unanswered or only have got a “I can’t reproduce” answer. Most promising for the moment is the KMail text encoding bug, where I was able to find some more information about the circumstances which trigger this problem. Let’s hope this helps in fixing the problem soon now. The slowliness of KMail’s message list is getting more and more annoying too. Actually already in folders with only a few hundreds message, the slowliness is noticeable. Speaking about slowliness, Konqueror’s KHTML web browsers also feels very sluggish today, compared to Firefox 2 and 3. Scrolling with the mouse scroll wheel often feels sluggish, as does the loading and rendering of complex pages. Konqueror’s KHTML on my Athlon 64 3500+ feels much slower than Epiphany/Webkit on my old PowerPC G4 laptop. It’s unfortunate that GTK+ and QT/KDE Webkit are still not really ready for production use.

List of today’s new KDE bugs:

Update 15 June 2008: two new bugs related to the Plasma desktop problems:

Testing KDE 4.1 beta 1

During the past few days, I have been testing KDE 4.1 beta on Mandriva Cooker. Actually the version I tested is even a bit more recent than KDE 4.1 beta: Cooker currently includes the KDE 4.0.81 snapshot.

Overall, the desktop is basically in a usable state. I experienced a few crashes, but generally it was not too bad. Unfortunately I could not report them all, because I don’t have the -debug packages installed (thanks to our infamous download limits in Belgium, it’s a bit difficult to keep these big packages up to date). Most problems are related to things not working correctly or not very intuitively. In my opinion this has always been the weak spot of KDE.

Here’s a list of bugs which I reported during the last few days:

A lot of this problems are not too bad, but they make the desktop loop a bit unfinished and less professional. The finishing touch is still lacking.

So apart from that, I experienced some more random crashes for which I did not find a reproducible test case yet. Sometimes a combo box in Konqueror’s web browser shows completely black when opened for the first time. Also in Konqueror, there are some refreshing issues, where you get part of the page overlapping with other parts, until you scroll the problematic part of the page out of the window and back in. Sometimes sound notifications in all KDE applications stop working completely. Some dialogs are not heigh enough by default (for example in Kopete’s new account wizard), a bug which was already reported on KDE’s bugzilla.

Plasma is still a mixed bag in KDE 4.1. The folder view, which is used for showing the normal icons on the desktop we are used to, does not have a correct right click menu for the menu icons, which makes it difficult/impossible to rename or remove icons on the desktop for example. I failed to add a “show desktop” button on the panel (nothing seems to happen when I do this). It’s deceiving that such basic features are still not working correctly now. All in all, I also have the impression that this whole Plasma thing also makes the desktop much more complex. It also adds little gain (only a few interesting gadgets mostly used by more advanced users and geeks) while it has still many drawbacks in basic features which are used by many less experienced people.

What’s also very problematic, is that there is a huge speed regression in KMail. in KMail 4.1, it is simply mail folders containing ten thousands of messages are barely usable, something which worked fine in KMail 3.5 and also works fine in Evolution. I reported this problem and apparently this is a known problem in QT 4.4’s Q3ListView class. Trolltech does not want to fix this bug anymore and so the only possible solution is to port KMail to use QTreeView, which will not happen for KDE 4.1. Unfortunately this is yet another example of things which won’t be complete for KDE 4.1.

KDE 4.1 generally feels very fast. Dolphin is a very nice addition to the desktop and while I was not really a fan of the KickOff menu earlier, it’s actually very usable. KDE finally can access file systems on encrypted LUKS devices (although it’s currently not working for me, probably because of a bug which is also affecting GNOME). and Gwenview is a very nice default picture viewer. Amarok 2 however does not seem very usable yet at this moment. I also like the new default setting of showing the text under the toolbar icons (however I don’t understand why this is not the case in Konqueror) and the integrated desktop effects in KDE are nice, while being a bit less bloated and bombastic than Compiz.

While KDE 4.1 has some very nice improvements, I think I will never install it on systems I manage for others (normal, non-technical computer users) which are now using KDE 3.5. For those kind of users, I want a (near) perfect desktop where everything is polished and things are working perfectly as intended and as would be reasonably expected by normal users. I’m afraid it will take until somewhere in the the KDE 4.2 series until this will become reality. If you are a more experienced user and don’t mind basic Plasma things not being finished and other unpolished things all over the desktop and don’t have any huge mail folders, then even already KDE 4.1 beta could be right what you need. Personally, I will continue to use GNOME 2.22.2. For now, I consider this as the most professional desktop which is capable of offering the kind of stability and smoothness most new Linux expect.