Re: Thoughts on bug 10602

On Wed, 2006-11-22 at 15:18 -0500, Dominic Lachowicz wrote:
> This is one of several HTML import bugs filed against Abi. Thanks to
> Sum1 and a host of others, our XHTML importer is reasonable, for some
> definition thereof. But it chokes on HTML4 and a variety of other
> things.
>
> In abiword-plugins, we have a HTML and a Multipart-HTML (MHT) import
> plugin. These can be based around either libxml2 or tidy, and they
> piggy-back on top of the XHTML importer. They can handle a lot of
> files that our XHTML importer can't.
>
> Now, since we now require libgsf, we indirectly require libxml2. This
> means that there aren't any new dependencies that should keep the
> libxml2-based importer out of the main tree. But there may be good
> reasons to keep this as a plugin, especially the MHT bits. Plus, since
> there are dueling implementations (libxml2 vs. tidy), I'm not really
> sure if one is quantitatively better than another. But then one also
> has to consider the likelihood of people installing a plugin vs.
> having this support right in AbiWord itself.
>
> So my question to you is, "how should I proceed?" I'd like to fix this bug.
>
> 1) Move the plugin's bits to abiword proper, and merge with the XHTML importer
> 2) Keep this as a separate plugin, and close the bug as "invalid,
> install the HTML import plugin"
> 3) <insert suggestion here>
>

Hi Dom,
       I vote to move the plugin into AbiWord proper and to use the
libxml2 library for that purpose. The libxml2 library is fundamental to
so many different applications that it just has to be maintained in the
future even if DV steps down.

I'm not sure about libtidy.

Cheers

Martin

> Thanks,
> Dom
Received on Thu Nov 23 01:02:14 2006