Hi, I suggest to also revisit logging. Last week I opened an issue for that (PDFBOX-5695 <https://issues.apache.org/jira/browse/PDFBOX-5695>), but it seems everybody is tired by this subject and no none even looked at it. Nonetheless, please take a look. The last time a switch to a logging facade was proposed (and rejected) has been 10 years ago. I think it is worth reconsidering, and a new major release would be the right time to do a change like that. More details in the issue.
Whatever the project decides, I am willing to contribute the required patch(es). Cheers, Axel > Am 11.10.2023 um 07:53 schrieb [email protected]: > > Dear colleagues, > > with 3.0 being released and 4.0 being started I'd like to start > discussing what the major plans are for 4.0. And maybe in a way that > the release can be made faster than what we had for 3.0. (maybe size it > in a way that we can do the dev stuff by spring 2024 and then release > in summer 2024 followed by a 4.1 release to add to that instead of > doing a big bang like 3.0) > > Shall we share some ideas via the mailing list or start a page on our > website (I think ml is easier to do). We can still document the major > initiatives as soon as we have agreed in a blog post. > > Here are my current thoughts (some of which might also be backported to > 3.0) in no particular order > > - appareance stream handlers for interactive form widgets (similar to > what we have for annotations) also allowing one to add their own > handler > - replacement or at least new base for XMPBox (current thought is to > have a new base parser and add if possible XMPBox current end user api > on top - might be able to reuse xmlgraphics XMP lib). Would allow to > better deal with XMPs which are not standard and make it easier to add > to existing XMPs low level. > - then we had the discussion about an event handler/listener similar to > what fop provides so one can listen to corrections/repairs done under > the hood (I know that we can only lay the ground for that as this is a > major undertaking given all the places where we correct things) > - enhance the parsing to keep the information about incremental > versions (better debugging, trace of changes done ...) > - review and add some more PDF 2.0 capabilities > - better text formatting/language support (maybe by including fop parts > or looking into using HarfBuzz) > - I'd also like to discuss reaching out to fop to look at integrating > some of their font handling into fontbox > ... > > That list is already long and I think would be too much given above > idea of release planning. > > With regards to versioning I'd like to propose that we have 2.0 as LTS > and 4.x being the next LTS. > > Thoughts > BR > Maruan > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
