Re: Bidi support

[Kenichi Handa]

In article <address@hidden>, Eli Zaretskii <address@hidden> writes:

> > By the way, the case of emacs-unicode is very special.  It
> > simply can't be in the trunk while developing because the
> > new unicode feature can't be toggled.

> Exactly, and that's precisely why the bidi development _can_ be done
> on the trunk without the burden of distinguishing its bugs from the
> others: toggle the feature off, and if the bug persists, it's not from
> bidi.

Even if that bug is not from bidi, as far as bidi support
suffers from it, the work for bidi support must be suspended
until that bug is fixed.  For instance, please consider the
situation that face-handling code gets unstable at some
point.  If we are working on a bug that bidi-text can't be
displayed by a correct face (just a hypothetical bug), that
work must be suspended.

> OTOH, the HUGE advantage of working on the trunk is that you don't
> need to merge all the time, or risk falling out of sync.  You also
> don't inherit random bugs that existed at the time of the branch
> creation.

I understand that merit too.  I even tend to agree on having
the bidi code in the trunk.  I just wanted to point out the
possibility of the above demerit.

---
Kenichi Handa
address@hidden