Re: GnomeFontSelector
- From: Owen Taylor <otaylor redhat com>
- To: Bill Haneman <bill haneman sun com>
- Cc: Havoc Pennington <hp redhat com>, Maciej Stachowiak <mjs noisehavoc org>, Michael Meeks <michael ximian com>, Anders Carlsson <andersca gnu org>, George <jirka 5z com>, gnome-2-0-list gnome org
- Subject: Re: GnomeFontSelector
- Date: 10 Oct 2001 10:33:01 -0400
Bill Haneman <bill haneman sun com> writes:
> Havoc Pennington wrote:
> >
> > Maciej Stachowiak <mjs noisehavoc org> writes:
> > > On 09Oct2001 11:02PM (-0400), Michael Meeks wrote:
> > > >
> > > >
> > > > [1] - gnome-terminal cannot be effectively pangoized.
> > > >
> > >
> > > Is there a fundamental technical reason for this, or is it just that
> > > it would be hard to restructure the code?
> >
> > All the Pango layout, cursor handling, etc. algorithms are
> > inappropriate. Terminals have to do special funky stuff. Basically
> > Pango isn't designed for this at all.
> >
> > If we wanted a terminal with UTF-8 support we'd want to look at what
> > xterm does and try to use that code.
>
> I'm not sure that we can effectively go that route, without a lot of
> addon code, since we need full accessibility features for
> gnome-terminal. Most likely AtkEditableText, AtkText, and possibly
> AtkTable.
>
> Without an accessible terminal we are pretty much doomed to be
> effectively "inaccessible".
I don't see any real reason why adding accessibility hooks to the
XTerm code is harder than adding them to gnome-terminal.
Yes, you might need some extra indirection to avoid having
the core code depend on ATK, but I doubt the "accessible terminal"
interface is that huge.
Regards,
Owen
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]