Again the website of the KDE Education Project is ahead. It was the first site that migrated to the new Chihuahua skin of kde.org. It is the only one which displays info pages for applications in the same way as the main site does – but improved with 2 levels of categories. And now it is the first page with Chihuahua Skin that can be translated.
I inserted a language selection selector into the so called tool-bar next to the breadcrumbs.
But after the change to different skins (first Chihuahua and now Derry) there were several issues to take care of:
- translation of the new PlasmaMenu, especially the dynamically generated part of it (application list)
- translation of the page title, wich is automatically inserted at the top of the page
- translation of the json-files containing information all about the applications
Issues
The skin contains some neat images with text messages like “Back home?” or “Search”. I am not sure if it is worth to translate them, too. At least the greeting “Welcome to KDE Edu!”, which is an image, should probably be replaced by a real translatable text line.
Credits
I got really much help from
- Albert (tsdgeos) who introduced me to the translation system used on the Okular site
- Luca (einar77) with python scripting for the json-files
- Tom (toma) with debugging all the i18n calls in the php-files during WebSprint2011
Thanks a lot for their work.
Translators are very welcome to help doing the real translation. French and Greece translators did a lot already.


Why is Rocs under “Science”? Graph Theory is a branch of Mathematics!
Thank you for this hint. You are right. I moved Rocs to the correct category.
You turned kdeedu.org into a great website with a great theme!!! In my opinion, you should translate ALL user visible strings on the website. Leaving some strings in English because they happen to be images, is amateurism and I guess amateurism is not how you want to present kdeedu
The problem is of course that when you don’t use images, you don’t know which fonts the user has installed, so the “Search” and “Back home?” texts may appear much uglier than with the images. A possibility is to hope that the user uses a web browser which support CSS3 and use the @font-face rule to link to a font-file installed on the server (see e.g. http://www.w3.org/TR/css3-fonts/#font-face-rule or http://nicewebtype.com/notes/2009/10/30/how-to-use-css-font-face/). A disadvantage of this is that the font is also downloaded when the user accesses the web page.
Unfortunately, the kdeedu website suffers from the same problem as almost all KDE websites (except userbase): it assumes a browser window width that is larger than mine (no, I am not on a 10 years old computer and no, I don’t want my Konqueror to fill up the whole screen, 800×600 is large enough, but I want to be able to read my text so my “medium font size” is 11pt). As a consequence I have a lot of horizontal scrolling to do. IMHO kdeedu.org should be an accessible website (as described at e.g. http://www.w3.org/TR/WCAG10/wai-pageauth.html). Therefore for widths (and all sizes) relative units should be used (see http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-relative-units).