Subject: Re: bidi status report
From: Tomas Frydrych (tomas@frydrych.uklinux.net)
Date: Wed Dec 12 2001 - 16:02:31 CST
> Fair enough. This wasn't really a hanging point for me. In fact, your
> whole "rant" never contradicted a single point of mine and mostly just
> let out your frustrations. Sounded like you needed it.
Yes, that's because I pretty much agreed with what you said :-).
> For the record, I would *not* be opposed to making BiDi the default
> build in DEBUG builds only. That way, you'll potentially get more
> feedback from people like Hub, Martin, and myself, and this could
> definitely be useful. The reason I say "potentially" here is that:
> So even if we turn this on by default in DEBUG builds, we're still not
> gaining much (if anything) in terms of bug reports and usability info
> for you. Those who download CVS and play with BiDi will continue to do
> so. Those who don't probably don't know what to look for, and therefore
> are of little use to you.
Acutally, that would be more useful than you think, because the
bugs I am most weary off are those that would disrupt the non-bidi
user: too much / to little screen refreshing, incorrect caret
positioning, crashes during normal usage. Now that we use fribidi
to do the ordering, most of the layout related bugs went away -- the
text is piped to the screen in the same manner whether it is pure
LTR or genuine bidi, and so the worst bugs will be experienced by
all. But I do have to say that am very weary of making the debug
build bidi and the release not, it would make layout bug fixing more
difficult, masking potential problems in the non-bidi-non-debug build.
Tomas
This archive was generated by hypermail 2b25 : Wed Dec 12 2001 - 16:04:18 CST