On Friday 06 of January 2012, Michael Stahl wrote:
On 06/01/12 12:19, Tor Lillqvist wrote:
Maybe the easiest way out would be to turn pdfimport from an .oxt
extension into an (optionally installable) part of LO.
Makes a lot of sense, I think. Ditto for other "extensions" included in
the source code.
in the case of pdfimport, isn't there a potential licensing problem
because it uses GPL-licensed xpdf/poppler code?
 I confess to having no clue about .oxt whatsoever, but assuming that now the 
pdfimport extension is binary code that eventually ends up dlopened by the 
soffice.bin process, how does turning it into a normal LO component, which is 
binary code that eventually ends up dlopened by the soffice.bin process, 
change anything? It shouldn't matter whether we open a pdf by finding out we 
have this filter that can handle it or by finding out we have this extension 
that can handle it.
-- 
 Lubos Lunak
 l.lunak@suse.cz
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.