Re: Bug#95018: UTF-8 Patch breaks slrn display on UTF-8 terminal
Hi, sorry for delay.
In <oa3daydnw4.fsf@arroz.fake>,
on 24 Apr 2001 16:49:15 -0400,
Adam Di Carlo <adam@onshore.com> wrote:
> Jim Mintha <jim@ic.uva.nl> writes:
>
> > Any thoughts at what should be done? Can these be fixed, or should we
> > make a seperate slang-utf8 package?
As Edmund replied, I think most of the problem will be solved
by simply recompiling the related packages. There may be some
minor problems, but it should be fixed in each package.
I've checked the bug reports on your slang1. And I think the problems
related to utf8 enabled console should be fixed at console code or at
related packages since utf8-aware xterm seems to work well in the same
environment.
> I always thought the plan was that we make a separate slang-utf8
> package. If done intelligently, such a package doesn't even need to
> conflict with the standard slang package (e.g., include files in a
> different dir, shared library named differently).
I originally thought to create a separate slang-utf8, but there is a
claim on my ITP at the BTS that says the forking should be avoided
by integrating the utf8 patch into the main slang1 package, and no
objection arrived for that claim.
I know that Jim has integrated the utf8 patch into his main slang1,
but it is the requested action on the BTS, and there are no major
problem with the recompiled newt as far as I checked, so I agree,
or rather, welcome that change.
> Any packages we need for the boot-floppies rescue system would of
> course have to be specifically built with these utf8 libs.
At least libnewt-utf8-0 requires utf8-aware slang1 to be compiled
with, and if main slang1 does not provide utf8 support, Enrique
might have extra difficulties in order to build up his newt related
packages. The build-dependency will be hard to define, since the
normal newt requires normal slang1 while the newt-utf8 requires
slang1-utf8. Well, if both of slang1 and slang1-utf8 can coexist
at the same time, then the problem of build-dependency can be solved,
but we can't test the utf8 libraries much at that setup, since other
softwares linked to normal slang1 library can not be used with the
slang1-utf8 library because of binary-incompatibility.
In my opinion, current setup (normal slang1 having utf8 support)
is not so bad one, unless the severe damage to the system is found.
In <20010424165526.L24522@daisy.vocalis.com>,
on Tue, 24 Apr 2001 16:55:26 +0100,
Edmund GRIMLEY EVANS <edmundo@rano.org> wrote:
> Jim Mintha <jim@ic.uva.nl>:
>
> > There seem to be a whole bunch of problems with the utf8 slang
> > packages. People are having trouble with slrn, lynx, etc. Possibly
> > these packages just need to be recompiled but the following seems more
> > serious:
> >
> > > On Sat, Apr 21, 2001 at 11:36:38PM +0200 , Jim Mintha wrote:
> > > > I just uploaded them. (I just realized that i missed adding the
> > > > Closes, but I'll do it by hand) Let me know if there are problems.
> > >
> > > there are. like debconf/whiptail segfaulting. Not evern recompile helps.
> > > Arguably it's a bug in newt, because it's not using the correct slang type
> > > defines, but still. It changes the API of slang, so every program using it,
> > > must be recompiled. Also querybts doesn't work
> > >
> > > Petr Cech
> >
> > Any thoughts at what should be done? Can these be fixed, or should we
> > make a seperate slang-utf8 package?
>
> Was this the latest, patched newt that you recompiled (0.50.17-4)? If
> so, please tell me more about the segfault.
As far as I see, the first report above is with the old newt.
The second report on the BTS said that the reporter found the
recompiled newt in Incoming area, and it solves the most of
problems except minor ones. It seems to me at least.
> The UTF-8 slang certainly has a changed binary interface, so
> recompilation of other packages is required. It's debatable whether
> you should call it a changed API, but it's not surprising if some
> packages require minor bug fixes as well as recompilation. The same
> fixes will be required for slang2, anyway.
>
> Edmund
Thanks for providing the patch for us, Edmund. We appreciate
your work well. Maybe we'll need your skills later again.
Regards.
--
Taketoshi Sano: <sano@debian.org>,<sano@debian.or.jp>,<kgh12351@nifty.ne.jp>
Reply to: