Re: [trinity-devel] Re: Resolving the TWin/KWin Fork Issue

I do, and there's no office package that can handle docx the "correct" way despite M$-Office. I don't get the point of this prolonged discussion: let's state somebody would really want to trade twin for something else, why should he use kwin? What's the benefit? As I see it, there's simply no point to prefer kwin to e.g. fvwm or openbox. By the way, I still have the infamouse problem of slugish qt4 experience. Nik