[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: [RFC] Future of KWord's PDF import filter
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2005-01-21 11:30:09
Message-ID: 200501211230.09767.nicolasg () snafu ! de
[Download RAW message or body]

On Thursday 20 January 2005 17:43, Nicolas wrote:
> once again I am the author/maintainer of this filter (hadacek@kde.org)
> and I have a version using xpdf 3 that seems to work ok. Unfortunately
> my time is very tight at the moment to work on KDE :(
>
> I will try to commit the xpdf 3 version but I understand the issues
> you raise and you are obviously free to move it aside if you think it
> doesnt fit anymore in the project...

I do not mind to keep the filter in KOffice, if you think it is the best. As 
for lacking time, well, it is a common problem of many KOffice developers... 
unfortunately.

If you do not want to commit the xpdf 3 version because you think that it is 
not stable enough, you might make a private branch (lower case name) for 
koffice/filter/kword/pdf . This way it would have the advantage to be in CVS 
without to have to be automatically released with KOffice 1.4. (And perhaps 
if committed, we could try to see if some KPDF developers would like to help 
KOffice.)

Have a nice day!

>
> Nicolas Hadacek
>
> On Thu, 20 Jan 2005 17:16:23 +0100, Nicolas Goutte <nicolasg@snafu.de> 
wrote:
> > I am wondering what the future of the PDF import filter of KWord might
> > be.
> >
> > Today there is now the third security vulnerability published for it and
> > again the xpdf security patch is being discussed as being not good enough
> > (and again only after been released).
> >
> > If I would have time to play such games, I would not mind; I would not
> > mind to do it once too, but slowly I am getting the feeling that it will
> > not end anywhere.
> >
> > Also the filter has currently following (long-term) drawbacks:
> > - how to support OASIS?
> > - how to support PDF 1.5 (i.e. using xpdf 3 instead of xpdf 2)?
> > - who will maintain it in future? (We have already problems with simplier
> > KWord filters to keep them up-to-date as much as possible, so for a
> > complex filter like the PDF one, it will be even more complex.)
> >
> > Also using xpdf 3 is important to keep getting security fixes, as one day
> > nobody will support kdegraphics 3.2.x anymore.
> >
> > So I am wondering if we should not move the filter back to one of the
> > kdeplayground modules (the successors of the kdenonbeta module).
> >
> > Or may be somebody has a middle-term solution that would be more
> > constructive. (Or of course real volunteers for this filter, but here I
> > am probably dreaming...)
> >
> > Have a nice day!
> >
> > _______________________________________________
> > koffice-devel mailing list
> > koffice-devel@kde.org
> > https://mail.kde.org/mailman/listinfo/koffice-devel
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]