texi2html-bug
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Texi2html-bug] Re: FSF assignment?


From: Patrice Dumas
Subject: Re: [Texi2html-bug] Re: FSF assignment?
Date: Mon, 27 Oct 2008 16:58:47 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

On Mon, Oct 27, 2008 at 11:03:14AM -0400, Derek Price wrote:
> Hi Karl, Patrice,
> 
> Are you planning on leaving Texi2HTML as its own project and importing
> releases to Texinfo or moving the whole source tree into the Texinfo
> repository?

The plan is to move the whole tree into texinfo.

> I've had a plan in the back of my head for some time to move the
> majority of the texi2html.pl functionality into a Texi2HTML.pm Perl
> module and release it on CPAN.  My motive for doing so is to make the
> functionality available for a Wiki::Toolkit::Formatter plugin I was also
> hoping to write and which I could use in conjunction with some MediaWiki
> plugins for Wiki::Toolkit and a MediaWiki clone that I have already
> written.  Do you think it would be possible to make Texi2HTML available
> under a dual Perl Artistic/GPL license?  What would be the right way to
> go about getting THAT change in place?  Is this compatible with your plans?

I would be happy to relicense my work under any free software license,
even public domain.

About making something really modular, I don't know how feasible it is.
Currently the separation between output and texinfo parsing is quite
good, and now that texi2html can process more than one texinfo file,
there is a beginning of separation from the main program and texinfo 
processing. However, the processing is still very linked with the init
file, and many data structures are initialized in the main loop. I don't
know which interface should be done for something acceptable as
stand-alone module.

That being said, it is the right time for a complete reorganization of
the interfaces toward something more modular. I think we can break
everything for the merge in texinfo (and I already have broken quite a
bit...).

--
Pat




reply via email to

[Prev in Thread] Current Thread [Next in Thread]