Re: XFT fonts
>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
Depends on how you define "as good as". By the historical
standard
of releases, it isn't.[1]
I define it as good as 21.4. If a 21.4 user will accept it as a usable
replacement that would be good enough I think.
Does 21.5 have new features like [...]
21.5 is GPLv3 or later which gives new possibilities.
Xft is not "blocking progress". [...]
Not directly but indirectly since 21.4 users might give up on porting
elisp code due to to much incompatibility. E-lisp developers stop
supporting XEmacs for the same reason. All the burden for making
packages work with XEmacs is on us.
[...] New users are going to want the fonts, I think, or they'll
go
where they can get them.
They are also likely to want to have updated elisp packages. So we
would want to have bo.
The main thing that people can do without committing too much time
is to sync GNU code. If you want to start on that, be my guest.
You don't need to worry too much about my taste in code; I'll
complain about crappy stuff like `display-message-or-buffer', but I
won't veto it, or revert it if you commit it.
At a small scale this has been done. But it will not really solve the
problem. Yes, we can port new packages to 21.5 and 21.5 user will
benefit from that. This is the current situation I think.
My point is that if there was a small step we could talk so that 21.4
users could move to 21.5 then all users would benefit. It wouldn't be
the grand 21.5 or 21.6 release once planned but it would allow for
updates to packages in parallel with the longer term GUI updates.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta