My tentative plan: - Do the meeting, know each other, discuss important stuff :-) - (pdfmm-repo) Finish "mechanical" port of tools to pdfmm. As said previously I will do the port but other people should ensure the tools still work as expected; - (pdfmm-repo) Finish API review, check-in text extraction API, create a pdfmm 0.10[1]; - (pdfmm-repo) Rename back references from pdfmm -> PoDoFo; - (pdfmm-repo) Change license of pdfmm **newly** created files to something compatible with PoDoFo license. These files are currently in LGPL 2.1 (fixed), so they are currently incompatible with PoDoFo (LGPL 2.0+). This will occur independently on decisions on relicensing of PoDoFo, which you all know it's something I'm actively pursuing (but can happen later the merge); - (podofo github) Create a podofo-next branch; - (podofo-next) Check-in the above modified pdfmm into podofo-next; - (podofo-next) Continue development there an discussions in ML aiming for a PoDoFo 1.0 release.
As you can understand, all of this it's not imminent. I hope everything can be done within july-august. If not, I will also have more time to dedicate to PoDoFo in september. Cheers, Francesco [1] https://github.com/pdfmm/pdfmm/blob/master/TODO.md On Thu, 5 May 2022 at 09:53, Christopher Creutzig <ccreu...@mathworks.com> wrote: > > Hi Francesco, > > Thanks for the confirmation, I was hoping that was the situation. Sorry for > the poor phrasing. > > What are your plans for the remaining steps before the back-merge, will that > happen in the pdfmm repository or in a branch in the new podofo one? > > > Cheers, > Christopher > > The MathWorks GmbH | Friedlandstr.18 | 52064 Aachen | District Court Aachen | > HRB 8082 | Managing Directors: Bertrand Dissler, Steven D. Barbo, Jeanne > O’Keefe > > > > -----Original Message----- > From: Francesco Pretto <cez...@gmail.com> > Sent: Thursday, May 5, 2022 9:42 > To: Christopher Creutzig <ccreu...@mathworks.com> > Cc: Podofo-users <podofo-users@lists.sourceforge.net> > Subject: Re: [Podofo-users] Future ABI stability of PoDoFo > > Hi Christopher, > > On Thu, 5 May 2022 at 08:16, Christopher Creutzig <ccreu...@mathworks.com> > wrote: > > > > Backporting required parts of std::span and having a layer that switches > > between std::format and fmtlib shouldn’t be too hard, assuming these are > > only used internally and nothing in the API expects span inputs, for > > example. But would we require contributors to use a C++20 enabled compiler? > > > > > > Please note that what you suggest it's already in place in pdfmm: I use > fmtlib in place of std::format and a backported std::span. > > Thinking a little bit more about the topic, let's not argue too much about > this: for the API/ABI surface I will just stick to C++17 requirement and hide > the fact I'm using std::format and std::span. > > Cheers, > Francesco > _______________________________________________ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
