Quickies: Kile, Quanta, Independent Qt Tutorial, KDE-NL, KDE China

We were notified about a
small article about Kile in the recent issue of
c't, Germany's largest IT magazine.
Check the table of content online, and/or
buy the magazine and check out page 55.
The Independent Qt Tutorial has been updated with two
completely new chapters about file handling
and XML
and numerous small fixes. Eric Laffoon, the project leader of Quanta Plus,
has been asked by techDigest to do an interview. They are
collecting some questions
for this interview as well. Wilbert Berendsen
reported that the website www.kde.nl has undergone a
metamorphosis to serve the KDE community in Belgium and the Netherlands much better. More on websites:
Shiyu Tang mentioned on the kde-www mailinglist
about the launch of a KDE-China website.

Dot Categories: 


by not rendered co... (not verified)

The KDE CHINA Website ist not correctly rendered in my Konqueror , there are serveral Glyphs missing , that are only represented by a box.

Are there more People where it is not correctly rendered ?

i am using kde 3.2 rc


Looks perfectly fine here, are you sure you have the necessary fonts containing all Chinese glyphs on your system?

by Paul Koshevoy (not verified)

You must have the right fonts installed to render Chinese!
It renders correctly for me (SuSE 8.2 KDE 3.2.0 RC1)


by Anonymous Coward (not verified)

Hmm, where can the fonts in question be found?

I don't think it has anything to do with not having the right fonts installed. KDE kinda suck when it comes to detecting fonts, I'm sure kde China displaid perfectly with your mozilla which mean u have the right fonts installed. I had the same problem, it worked with mozilla but not konqueror so I had to add them myself with the kcm module.

The site sets the correct charset in its meta tag so no auto detection is involved at all. He is clearly missing the right font if some characters are showed as squares (do a google search for different sources of Chinese fonts if you miss them on your system).

by Peter Robins (not verified)

You may need to set up your font substitution tables (strictly speaking part of qt, not kde). You can use kcharselect to see whether you have the fonts/glyphs. Chinese chars are around table 80. If you have fonts like Fangsong Ti or Song Ti, they will/should! display the right chars for those tables. If western fonts don't, use qtconfig to add Fangsong Ti or whatever to the western fonts. KDE Taiwan are using Tahoma (don't ask me why), so if you add (Fang)Song Ti to Tahoma and restart konqueror, it should then display.

These substitutions are stored in ~/.qt/qtrc

is there a way to do this automatically ? no editing or clicking involved ?

the china website displays perfectly in mozilla, the glyhps are not antialiased like the arabian one , but ....


by Ian Monroe (not verified)

Its always been the opposite for me, works in Konqueror and not in Mozilla without me trying as I don't know any languages in other alphabets. So it doesn't really make any difference in my case, but if I do need to browse a site I do like seeing those pretty characters and, in some languages, playing with right-to-left highlighting. (-:

i think its not a fonts problem (it works in moz, doesn't work in konq), but a QT problem. i see the problem when using qt 3.2 and kde 3.2, but it goes away when i go to qt_copy 3.3 (also, kopete starts showing other glyphs right with qt_copy 3.3). Unfortunately, it seems 3.3 is not yet stable...

by Jethro Cramp (not verified)

There is a bug with the Qt font substitution system.

If you have other glyph fonts (such as Japanese, Korean or full form Chinese) and they appear in the font substitution list before the simplified Chinese fonts then they will be used to render the text.

These other character sets do not contain all the characters necessary to render simplified Chinese and therefore some glyphs will be missing.

The font substitution list is in your .qtrc file.

Good luck.


Nothing just a testing on this form.

by Rischwa (not verified)

Hey ho!
There was also a small article about k3b in the issue before.
Just check out C't 2/2004 page 58 for a small review of "the probably most comfortable burning program for linux". :-)


by dhaumann (not verified)

yes, I've read that too, and I have to agree!
Good work, Sebastian Trueg&Co!

by Eric Laffoon (not verified)

I second that. Before K3B I was having to switch between different more or less annoying package, but now it's like it's too easy. ;-)

by Frans Englich (not verified)

And I second that. k3b is so intelligent, and so userfriendly, and so usable, and so capable, etc, etc.

Thanks Sebastian, do you get paid for this? You really keep up the activity, according to kde-cvs..



by Elektroschock (not verified)

In my opinion language support has to be integrated into the main site rather than prioviding a bunch of national website that are out of date.

Also easier translation tools for long texts are needed. t7e perhaps, haven'zt tried it yet.

by alekibango (not verified)

Plone can do this well. It is best opensource CMS available.
Try it on http://test.plone.org

Some tweaks would be needed to run huge site, but it is not so hard and plone gurus on irc.freenode.net (channel #plone) can help a lot.

btw: there was a bug in konqueror before Xmas which was causing plone website to look funny. so if it looks ugly, upgrade now :)

by Holger Schurig (not verified)

Well, the Typo3 CMS is also very capable when it comes to multi-language. Every snippet (article, newsitem, whatever) can be submitted several times, e.g once in english, then some editor submits the german version and so on.

When someone with language "german" views a page, then all the german entries get display. If for some entry the german entry does not exist, then the english (or whatever you set up as default language) will be shown. This way you won't have an information-loss if you're a non-native speaker.


by Gagamemnon (not verified)


What features issued of this site had to be postponed to the 3.3 release of Quanta?

by Eric Laffoon (not verified)

> What features issued of this site had to be postponed to the 3.3 release of Quanta?

I think the idea was to post to the site for interview questions... you must be looking for a shortcut. ;-) I'll answer anyway. First of all much of what didn't make it into 3.2 will be out soon in Quanta BE releases. They are marked development so we won't get flack if a new feature is not fully complete but they are stable. Also, we're considering releasing Quanta 3.3 before the KDE 3.3 release. We don't have to have the same release numbers and most KDE apps don't. What we have to do is adhere to freezes in the KDE schedule. External releases allow users to benefit from new features as they become usable but do not benefit from translation and and other release benefits.

* Templates - directory templates and installed templates as well as an online template repository is scheduled for early this year
* Project docs made it in but you have to generate them. Doc generation via the parser and configuration is under review
* Getvars - probably nobody knows what it is, but it's enhanced html form debugging tools
* Site Planner - It's morphed into two separate projects and will not likely show up before mid year at the soonest
* New CSS tools did make it in, but updates have since arrived and integration for much better CSS use is in work. Look for this early this year.
* Supplemental file data
* Enhanced undo/redo - we had problems with this and back burnered it since Nicolas was also working on VPL
* Toolbar Dropdowns - this would be similar to the recent file toolbar button and would have an extra interface in actions to allow listing tags or scripts. I seem to be the only person excited about this. Is anyone else?
* Multiple upload profiles - using multiple instances, separate projects or changing settings is it for now.
* VPL - It's in there, but it still has a few rough edges. Look for a more refined version that makes it easier to work with CSS and do other tasks early this year.

There are a lot of other new things we're working on now too. I apologize for the site being behind. I'm dealing with moving my business site after having been shafted by my hosting provider and we are looking to do a complete redesign this month of the site.

by Gagamemnon (not verified)


how do you think can multilanguage environments be managed. We do have the text.en.txt text.gr.txt format, but how can we manage the problem.

Where do the tools have to be improved?
- webeditors?
- network tools for translators?
- distributed translation environments?
- better multilanguage support for CMS??
- standards?

What can be done?

by Eric Laffoon (not verified)

> how do you think can multilanguage environments be managed. We do have the text.en.txt text.gr.txt format, but how can we manage the problem.

That's a really loaded question. I'm probably not the best person to ask because I'm not currently doing it... though I'm considering doing that on our new site.

> Where do the tools have to be improved?
> - webeditors?
I don't think you're going to want me to offer you a "mandated" solution because it would constrain your options. In that regard Quanta does offer you extensive abilities to customize it and build script and dialog extentions.

> - network tools for translators?
> - distributed translation environments?
I'm at a loss here...
> - better multilanguage support for CMS??
Several people on my team refer to CMS as "Can't Manage S***". Effectively these tools try to become everything instead of offering pluggable extensible functionality. That could be why there's not a consensus tool and so many people write their own.
> - standards?
That's an ugly thought unless you can tell me how you will do that without really messing with existing standards like HTTP and XHTML.

Like many design factors it comes down to how the development team wants to define what they do. KDE and Quanta both have additional guidelines that constraing the project development and are consistent with lead developers, good design and our objectives. This is where project vision comes in. You have to define a framework, and you probably won't like someone else's. for instance, it's not too difficult to develop an abstracted layout using PHP and CSS. Then you include your content files into your structure files and manage your look and layout with CSS. That way you develop one structure, as many looks as are required and language content in parallel. That would be my approach. Default to /content/en/ and allow switching to /content/de/ or whatever.

by testerus (not verified)

>> - better multilanguage support for CMS??
> Several people on my team refer to CMS as "Can't Manage S***".
> Effectively these tools try to become everything instead of
> offering pluggable extensible functionality. That could be why
> there's not a consensus tool and so many people write their own.

Any plans to change that? I can't imagine that there are no projects for CMS-(brick like)-modules. Maybe they are not visible because there are so many CMS? Including support for such an CMS in Quanta could mean a huge boost for a small CMS project.

by Emiel Kollof (not verified)

It's actually useful now, go figure :)

by gerd (not verified)

What aid can be provided for colorblind people
- "color check" assistence for webdesigners?
- help for color blind to detect whether a color was red or green