Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


On 08/05/2013 01:19 PM, Wagner Macedo wrote:
On 5 August 2013 12:26, Kohei Yoshida <kohei.yoshida@suse.de <mailto:kohei.yoshida@suse.de>> wrote:

    In short, these two take two different code paths.  The HTML
    export one goes through an internal, C++ export filter (I
    believe), whereas the XHTML export one goes through a XSLT based
    export path, which is super slow and is not scalable.

    In the future we should probably organize this area, and just have
    one C++-based export filter that always exports XHTML.  But we are
    not there yet.


Korei, thanks by information.

But I was not referring (yet) to code, sorry for I haven't been clearer. But I'd like to know why we have two options to, apparently, do the same thing.
I can't answer why there are two ways, since I'm not the one who made that decision in the first place.

All I can say is that there *shouldn't* be two options, and someone has to spend time combining the two export filters into one.

Does that answer your question?

Kohei


--
Kohei Yoshida, LibreOffice Calc hacker, SUSE.


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.