Kate & bidi

[Christoph Cullmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Seems like it might be possible, somewhere, sometime down the road to
> clobber all 3 text editors
> just enough to get the unified feature set of all of them into one
> great text editor.  I remember bidi being a problem
> in Kate way back when I first got my KDE commit bit.    If we haven't
> found an easy solution yet it may be that
> the design of Kate is just such that it may have hit a wall in terms of
> design.  No offense intended to anyone
> involved with Kate... its a killer application in my book :).  Its just
> that I want to see it be the only editor KDE users need to have.
>
> Its pretty clear until something like that happens that KEdit must stay
> for bidi functionality.  We can't alienate that
> group of people who may use KDE who need it.
The greatest problem with kate & bidi: Nobody in the kate team really had the 
time to dive into the bidi docs and come up with an implementation in the 
last years ;/ Hamish has read a bit over it some weeks ago I think, and he 
has allready done great work to make the kate rendering stuff much more 
generic (about further infos, have crossposted to kwrite-devel and hamish, 
perhaps has missed some important mailtraffic in the last weeks).
If we would find some volunteer with deeper bidi knowledge integration into 
kate part should not be an unsolvable problem, perhaps I should look again at 
the qt parts lars pointed me too last year.

cu
Christoph

- -- 
Christoph Cullmann
KDE Developer, kde.org Maintainance Team
http://www.babylon2k.de, cullmann at kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+oWw5yPjDGePm9UIRAh4aAKCFtaoQKqPK0GcmTHWJqoYbt8HNYwCg1StE
tyUX0UueM2jLDYl2R3A+JUM=
=hAPB
-----END PGP SIGNATURE-----