podofo-users — PoDoFo - A free PDF library

[Podofo-users] PoDoFo re-licensed to MPL-2.0/LGPLv2+

[Francesco P. <ce...@gm...>]

Hello PoDoFo users,
present and past contributors (BCC),

This is a final status update regarding the PoDoFo library dual
MPL-2.0/LGPL2+ relicensing effort, which is now complete and has been
pushed[1] to the repository.

To achieve this result, we carried out a small number of localized
code rewrites, as we did not receive relicensing permission from a
couple of contributors. All such interventions and analyses are
documented in the corresponding reports[2]. Tools retain their original
GPL2+ license for the time being.

Dominik and I act as custodians of the relicensing authorizations
granted by the copyright holders.

To mark this milestone, PoDoFo 1.1 will be released in the coming
days, after testing the last modifications and fixes. Thank you
to everyone who supported this effort.

Francesco Pretto
Dominik Seichter

[1] https://github.com/podofo/podofo/commit/b023d4e885d2aecfcfcd6d49f38694ef923629ee
[2] https://github.com/podofo/podofo/blob/master/governance/relicensing/PoDoFo-LGPL2%2B_MPL2-relicensing.ods

Re: [Podofo-users] Resumption of the PoDoFo LGPL2+/MPL-2.0 dual licensing effort

[Francesco P. <ce...@gm...>]

Hello PoDoFo users and contributors (BCC),

I have a small status update regarding the PoDoFo LGPLv2+/MPL-2.0
re-licensing effort: of the 20[1] people with copyright claims on the
PoDoFo library code we obtained 17 permission grants. Of the remaining
3, a couple were unresponsive (or we don't have an updated email
contact). For one contributor we never found a valid email address. If
you know any of these people please let us know privately. One or two
contributors may have chosen to alter their name to protect their
privacy.

The next steps:
- As for the library code, we'll start by assuming that no more
permissions will be granted: we'll thoroughly analyze the
contributions of people whose permissions haven't arrived and
determine if, and which, code will require a rewrite. Of course the
names of these people will remain in AUTHORS.md as previous
contributors;
- As for the tools we will send a few more pending requests (around 5)
to re-license tools to dual GPLv2+/MPL-2.0. There are currently no
plans to use any of the tools code into the library, but MPL2 leaves a
open door in case later some functionalities are chosen to be included
in the library as extra (non core) functionalities.

A final update will be sent once all the code that needs to be
rewritten has been completed and the PoDoFo library (and possibly
tools) is officially re-licensed.

Best,
Francesco

[1] https://docs.google.com/spreadsheets/d/1o6XRJowO_6nBnYZcgqu6YYp_UNS9x2qzYGUSMna6BXU/edit?gid=0#gid=0

Re: [Podofo-users] Resumption of the PoDoFo LGPL2+/MPL-2.0 dual licensing effort

[Francesco P. <ce...@gm...>]

Hello,

Another status update: we have reached 65% of permissions from the people
we contacted. We are still experiencing some delays in reaching a few
individuals, but I am confident that more replies will arrive soon. I have
also recently added a couple more names to the list of people with library
copyright claims. As promised, we are providing more details on the process
that determined this list.

As you know, until 2022 PoDoFo was a Subversion-based project, and public
contributions from people without write access to the SF.net repository
were submitted through the mailing list as patches. A manual review of all
commits has been carried out to collect all contributors, resulting in a
total of around 100 individual contributors up to December 2022 (after that
date, we require all contributions to be licensed under LGPLv2+/MPL-2.0).
Major contributors and maintainers were easily identified. For the
remaining cases, criteria were defined to identify people with potential
copyright claims. We took inspiration from successful re-licensing efforts
such as VLC (GPLv2 -> LGPLv2.1+) and similar projects. The defined criteria
are (either one is sufficient):

- Enough "lines of code" for the single patch, with most of them still in
place and recognizable (i.e., not substantially rewritten by contributors
already supporting the dual licensing). In most cases, the observed cutoff
is around ~10 lines, although qualitative considerations have also been
applied;
- A sufficient number of submitted patches. In practice, the observed
cutoff is 10 patches, again with additional qualitative considerations
where appropriate.

By "lines of code" we mean methodic/algorithmic LOC: non-empty,
non-delimiting (e.g., block braces), excluding build configuration files
and, in most cases, headers and comments. Contributions not meeting these
criteria are considered small patches or collections of small patches.

Since we are prioritizing the dual licensing of the library, the following
have not been taken significantly into account (for now): tests, tools, man
pages, and CMakeLists.txt files (which have since been heavily rewritten).
The application of the above criteria resulted in the following
contributions not requiring explicit consent for the dual licensing:

https://docs.google.com/spreadsheets/d/1o6XRJowO_6nBnYZcgqu6YYp_UNS9x2qzYGUSMna6BXU/edit?usp=sharing?gid=1925947523#gid=1925947523

The remaining 20 individuals are those we are currently contacting
regarding **library-only** copyright claims:

https://docs.google.com/spreadsheets/d/1o6XRJowO_6nBnYZcgqu6YYp_UNS9x2qzYGUSMna6BXU/edit?usp=sharing

Overall, the results show a tendency in arbitrating between casual (or
near-casual) contributions and more substantial ones. In particular, the
"sufficient patches" criterion helps recognize the work of contributors who
may not have provided major implementations but invested significant time
in making the project broadly usable.

Please feel free to raise any doubts or concerns regarding the methodology
used.

Kind regards,
Francesco

On Sat, 7 Feb 2026 at 01:39, Francesco Pretto <ce...@gm...> wrote:
>
> Hello PoDoFo users,
>
> I think it's time already for a quick update on the status of the dual
> licensing operation. Here is the list of people (most likely) holding
> some copyrights on the library code:
>
>
https://docs.google.com/spreadsheets/d/1o6XRJowO_6nBnYZcgqu6YYp_UNS9x2qzYGUSMna6BXU/edit?usp=sharing
>

Re: [Podofo-users] Resumption of the PoDoFo LGPL2+/MPL-2.0 dual licensing effort

[Dominik S. <dom...@go...>]

Hi,

Small heads-up from my side!

Thanks to Francesco for coordinating, organizing and following up on the
re-licensing effort! The process is very well structured!!
Thanks also to everyone who gave a quick reply already!

To everyone else, if you still have a mail regarding the copyright topic in
your inbox, we would be glad to get a positive reply. If you have any
questions, do not hesitate to contact us!!

Kind regards,
Dominik

On Sat, Feb 7, 2026 at 1:40 AM Francesco Pretto <ce...@gm...> wrote:

> Hello PoDoFo users,
>
> I think it's time already for a quick update on the status of the dual
> licensing operation. Here is the list of people (most likely) holding
> some copyrights on the library code:
>
>
> https://docs.google.com/spreadsheets/d/1o6XRJowO_6nBnYZcgqu6YYp_UNS9x2qzYGUSMna6BXU/edit?usp=sharing
>
> So far ~40% of the people answered positively to the request.
> Excluding me and Dominick it's 6 people that promptly answered in the
> first 24 hours. All the yellow marked people were sent an email to an
> address that didn't bounce with errors (you can find attached the
> template that was used for the email). Some may be dormant recipients,
> but let's wait a bit before sending reminders or try to find other
> addresses.
>
>  We also have a couple of missing contacts:
> - Reinhard Mitteregger: the old email address is deactivated was on
> the domain on Michelic&Partner, a company that should be closed now.
> Waiting for connection by other means;
> - Palmer Zent: this case is more interesting. The old email was a
> deactivated @gmail.com address, and so it is his user "pzent" on
> sourceforge. The only relevant matches for this user are related to
> PoDoFo. I don't want to speculate, so I will simply ask: do you know
> him/can you provide a contact (also privately)?
>
> As a last note: Dominik doesn't have any statistics related to this ML
> as they are not available anymore in SF.net, and recently it has been
> quite silent. There may be no more than 10 people still reading it,
> who knows? If you have something to say, please do :) .
>
> Cheers,
> Francesco
>
>
>
> On Thu, 5 Feb 2026 at 00:49, Francesco Pretto <ce...@gm...> wrote:
> >
> > Dear PoDoFo users/maintainers,
> >
> > I just wanted to inform you that, together with Dominik, we resumed
> > the effort begun in 2022 to dual license[1] the PoDoFo code to
> > LGPL2+/MPL-2.0. We have identified around 20 people who most likely
> > hold some copyright on the library code. Other contributors' code got
> > rewritten, or their contributions were too small. We will disclose
> > more about the process once it is at a more advanced stage.
> >
> > Anyone on the copyright holders list will soon receive an email.
> > Please understand if the tone is a bit formal and impersonal.
> >
> > Cheers,
> > Francesco
> >
> > [1] https://sourceforge.net/p/podofo/mailman/message/37746122/
> _______________________________________________
> Podofo-users mailing list
> Pod...@li...
> https://lists.sourceforge.net/lists/listinfo/podofo-users
>

Re: [Podofo-users] Resumption of the PoDoFo LGPL2+/MPL-2.0 dual licensing effort

[Francesco P. <ce...@gm...>]

Hello PoDoFo users,

I think it's time already for a quick update on the status of the dual
licensing operation. Here is the list of people (most likely) holding
some copyrights on the library code:

https://docs.google.com/spreadsheets/d/1o6XRJowO_6nBnYZcgqu6YYp_UNS9x2qzYGUSMna6BXU/edit?usp=sharing

So far ~40% of the people answered positively to the request.
Excluding me and Dominick it's 6 people that promptly answered in the
first 24 hours. All the yellow marked people were sent an email to an
address that didn't bounce with errors (you can find attached the
template that was used for the email). Some may be dormant recipients,
but let's wait a bit before sending reminders or try to find other
addresses.

 We also have a couple of missing contacts:
- Reinhard Mitteregger: the old email address is deactivated was on
the domain on Michelic&Partner, a company that should be closed now.
Waiting for connection by other means;
- Palmer Zent: this case is more interesting. The old email was a
deactivated @gmail.com address, and so it is his user "pzent" on
sourceforge. The only relevant matches for this user are related to
PoDoFo. I don't want to speculate, so I will simply ask: do you know
him/can you provide a contact (also privately)?

As a last note: Dominik doesn't have any statistics related to this ML
as they are not available anymore in SF.net, and recently it has been
quite silent. There may be no more than 10 people still reading it,
who knows? If you have something to say, please do :) .

Cheers,
Francesco



On Thu, 5 Feb 2026 at 00:49, Francesco Pretto <ce...@gm...> wrote:
>
> Dear PoDoFo users/maintainers,
>
> I just wanted to inform you that, together with Dominik, we resumed
> the effort begun in 2022 to dual license[1] the PoDoFo code to
> LGPL2+/MPL-2.0. We have identified around 20 people who most likely
> hold some copyright on the library code. Other contributors' code got
> rewritten, or their contributions were too small. We will disclose
> more about the process once it is at a more advanced stage.
>
> Anyone on the copyright holders list will soon receive an email.
> Please understand if the tone is a bit formal and impersonal.
>
> Cheers,
> Francesco
>
> [1] https://sourceforge.net/p/podofo/mailman/message/37746122/

[Podofo-users] Resumption of the PoDoFo LGPL2+/MPL-2.0 dual licensing effort

[Francesco P. <ce...@gm...>]

Dear PoDoFo users/maintainers,

I just wanted to inform you that, together with Dominik, we resumed
the effort begun in 2022 to dual license[1] the PoDoFo code to
LGPL2+/MPL-2.0. We have identified around 20 people who most likely
hold some copyright on the library code. Other contributors' code got
rewritten, or their contributions were too small. We will disclose
more about the process once it is at a more advanced stage.

Anyone on the copyright holders list will soon receive an email.
Please understand if the tone is a bit formal and impersonal.

Cheers,
Francesco

[1] https://sourceforge.net/p/podofo/mailman/message/37746122/

Re: [Podofo-users] Space after letter "A"

[Francesco P. <ce...@gm...>]

Hi Christian,

I'm sorry: I won't do any support for the 0.9.x series. You have been
subscribed to the mailing list for a long time: you certainly know that we
had 0.10.x and we now have a 1.0.x series (soon there will be also a
1.1.x). You should stop living in the past and upgrade, because it brings
you real value. This is how you do it with the 1.x stable API:

    PdfMemDocument doc;
    auto& font =
doc.GetFonts().GetOrCreateFont(R"(D:\haborocontrastnormregular.otf)");
    auto& page = doc.GetPages().CreatePage();
    {
        PdfPainter painter;
        painter.SetCanvas(page);
        painter.TextState.SetFont(font, 18);
        painter.DrawText("ABCDEFGHIKLMNOPQRSTVXYZ", 50, 700);
    }
    doc.Save(R"(D:\font-text-drawing.pdf)");

You don't have to deal with encodings: everything is handled automatically,
with full unicode support. Requirement for manual handling of encodings in
pre 0.10.x PoDoFo versions was probably the result of lack of time to
implement features that turned out to be much more complex than they
appeared to be. Attached is the result of the above code and, surprise, no
glitches. Not everything is perfect, because we still don't have proper
text shaping[1], which is not relevant only for bidi languages but for
proper latin scripts kerning as well. In the past I received private
comments who stated that text writing in PoDoFo is a toy because of such a
lack, and adding HarfBuzz support was easy: well, I'm still waiting for
their patches to close the gap.

Regards,
Francesco

[1] https://github.com/podofo/podofo/issues/297


On Mon, 8 Dec 2025 at 08:30, Christian Sakowski <
chr...@he...> wrote:

> Hi,
>
> i identified the problem.
>
> When using GlobalPdfDocEncodingInstance() it works correctly, but NOT with
> GlobalIdentityEncodingInstance()! I Used this because the docs say: "useful
> for writing direct UTF8 strings“!
>
>    //EXAMPLE
>
> PoDoFo::PdfMemDocument  writer;
> PoDoFo::PdfPage* pPage =
> writer.CreatePage(PoDoFo::PdfPage::CreateStandardPageSize(PoDoFo::ePdfPageSize_A4));
> PoDoFo::PdfPainter ppainter;
> const PoDoFo::PdfEncoding* encFac;
>
> encFac = PoDoFo::PdfEncodingFactory::GlobalIdentityEncodingInstance();
>
> ppainter.SetPage(pPage);
>
> PoDoFo::PdfFont* pFont = NULL;
> try {
> pFont = writer.CreateFont("HaboroContrast-NorReg", false, false, false,
> encFac, PoDoFo::PdfFontCache::eFontCreationFlags_AutoSelectBase14, true);
> }
> catch (PoDoFo::PdfError& e) {
> pFont = writer.CreateFont("Arial",
> PoDoFo::PdfEncodingFactory::GlobalWinAnsiEncodingInstance(), false);
> }
> if (!pFont)
> {
> PODOFO_RAISE_ERROR(PoDoFo::ePdfError_InvalidHandle);
> }
>
> pFont->SetFontSize(16.0);
> ppainter.SetFont(pFont);
> ppainter.DrawText(100, 100, "ABC");
> ppainter.FinishPage();
>
> writer.Write("C:\\Users\\christian\\Desktop\\podofo.pdf“);
>
> I am using v0.9.6
> --
>
> Grüße/Regards,
> [heubach-media] | Christian Sakowski
> Chr...@he...
> Tel: +49/(0)40/52 10 59-23
>
>
>
>
> > Am 04.12.2025 um 10:29 schrieb Francesco Pretto <ce...@gm...>:
> >
> > Hello,
> >
> > please: attach a self compilable code which shows the problem and report
> the PoDoFo version.
> >
> > Francesco
> >
> > On Thu, 4 Dec 2025 at 09:38, Christian Sakowski <
> chr...@he...> wrote:
> > Hi,
> >
> > i have created a simple output with the letter „A“ and the font
> "haboro-contrast-normal-medium.otf“.
> > But in PoDoFo there is a space after the letter „A“, when creating an
> output with MS Print To PDF, there is no such space.
> > See attachments.
> > Any hint where to find a solution?
> > Many thanks!
> >
>
>
>
> ---
> heubach media
> Osterfeldstr. 12-14 | Haus 1 | Eingang Nord
> 22529 Hamburg
> tel: 040 / 52 10 59 - 10 | fax: -99
> mail: in...@he...
> home: www.heubach-media.de
> Geschäftsführer|CEO: Matthias Heubach
>
> Mieten Sie Ihre Computer, iPads & Drucker für Ihre Events bei:
> http://www.milo-rental.com
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen.
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
> erhalten haben, informieren Sie bitte sofort den Absender
> und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
> die unbefugte Weitergabe dieser Mail ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information.
> If you are not the intended recipient (or have received this e-mail in
> error)
> please notify the sender immediately and destroy this e-mail.
> Any unauthorized copying, disclosure or distribution of the
> material in this e-mail is strictly forbidden.
>
>

Re: [Podofo-users] Space after letter "A"

[Christian S. <chr...@he...>]

Hi,

i identified the problem.

When using GlobalPdfDocEncodingInstance() it works correctly, but NOT with GlobalIdentityEncodingInstance()! I Used this because the docs say: "useful for writing direct UTF8 strings“!

   //EXAMPLE

PoDoFo::PdfMemDocument  writer;
PoDoFo::PdfPage* pPage = writer.CreatePage(PoDoFo::PdfPage::CreateStandardPageSize(PoDoFo::ePdfPageSize_A4));
PoDoFo::PdfPainter ppainter;
const PoDoFo::PdfEncoding* encFac;

encFac = PoDoFo::PdfEncodingFactory::GlobalIdentityEncodingInstance();

ppainter.SetPage(pPage);

PoDoFo::PdfFont* pFont = NULL;
try {
pFont = writer.CreateFont("HaboroContrast-NorReg", false, false, false, encFac, PoDoFo::PdfFontCache::eFontCreationFlags_AutoSelectBase14, true);
}
catch (PoDoFo::PdfError& e) {
pFont = writer.CreateFont("Arial", PoDoFo::PdfEncodingFactory::GlobalWinAnsiEncodingInstance(), false);
}
if (!pFont)
{
PODOFO_RAISE_ERROR(PoDoFo::ePdfError_InvalidHandle);
}

pFont->SetFontSize(16.0);
ppainter.SetFont(pFont);
ppainter.DrawText(100, 100, "ABC");
ppainter.FinishPage();

writer.Write("C:\\Users\\christian\\Desktop\\podofo.pdf“);

I am using v0.9.6
--

Grüße/Regards,
[heubach-media] | Christian Sakowski
Chr...@he...
Tel: +49/(0)40/52 10 59-23




> Am 04.12.2025 um 10:29 schrieb Francesco Pretto <ce...@gm...>:
> 
> Hello,
> 
> please: attach a self compilable code which shows the problem and report the PoDoFo version.
> 
> Francesco 
> 
> On Thu, 4 Dec 2025 at 09:38, Christian Sakowski <chr...@he...> wrote:
> Hi,
> 
> i have created a simple output with the letter „A“ and the font "haboro-contrast-normal-medium.otf“.
> But in PoDoFo there is a space after the letter „A“, when creating an output with MS Print To PDF, there is no such space.
> See attachments.
> Any hint where to find a solution?
> Many thanks!
> 



---
heubach media
Osterfeldstr. 12-14 | Haus 1 | Eingang Nord
22529 Hamburg
tel: 040 / 52 10 59 - 10 | fax: -99
mail: in...@he...
home: www.heubach-media.de
Geschäftsführer|CEO: Matthias Heubach

Mieten Sie Ihre Computer, iPads & Drucker für Ihre Events bei:
http://www.milo-rental.com

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten haben, informieren Sie bitte sofort den Absender 
und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie 
die unbefugte Weitergabe dieser Mail ist nicht gestattet.
 
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the
material in this e-mail is strictly forbidden.

Re: [Podofo-users] Space after letter "A"

[Francesco P. <ce...@gm...>]

Hello,

please: attach a self compilable code which shows the problem and report
the PoDoFo version.

Francesco

On Thu, 4 Dec 2025 at 09:38, Christian Sakowski <
chr...@he...> wrote:

> Hi,
>
> i have created a simple output with the letter „A“ and the font
> "haboro-contrast-normal-medium.otf“.
> But in PoDoFo there is a space after the letter „A“, when creating an
> output with MS Print To PDF, there is no such space.
> See attachments.
> Any hint where to find a solution?
> Many thanks!
>
>

[Podofo-users] Space after letter "A"

[Christian S. <chr...@he...>]

Hi,

i have created a simple output with the letter „A“ and the font "haboro-contrast-normal-medium.otf“.
But in PoDoFo there is a space after the letter „A“, when creating an output with MS Print To PDF, there is no such space.
See attachments.
Any hint where to find a solution?
Many thanks!

--

Grüße/Regards,
[heubach-media] | Christian Sakowski
Chr...@he...
Tel: +49/(0)40/52 10 59-23





---
heubach media
Osterfeldstr. 12-14 | Haus 1 | Eingang Nord
22529 Hamburg
tel: 040 / 52 10 59 - 10 | fax: -99
mail: in...@he...
home: www.heubach-media.de
Geschäftsführer|CEO: Matthias Heubach

Mieten Sie Ihre Computer, iPads & Drucker für Ihre Events bei:
http://www.milo-rental.com

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten haben, informieren Sie bitte sofort den Absender 
und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie 
die unbefugte Weitergabe dieser Mail ist nicht gestattet.
 
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the
material in this e-mail is strictly forbidden.


---
heubach media
Osterfeldstr. 12-14 | Haus 1 | Eingang Nord
22529 Hamburg
tel: 040 / 52 10 59 - 10 | fax: -99
mail: in...@he...
home: www.heubach-media.de
Geschäftsführer|CEO: Matthias Heubach

Mieten Sie Ihre Computer, iPads & Drucker für Ihre Events bei:
http://www.milo-rental.com

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten haben, informieren Sie bitte sofort den Absender 
und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie 
die unbefugte Weitergabe dieser Mail ist nicht gestattet.
 
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the
material in this e-mail is strictly forbidden.


---
heubach media
Osterfeldstr. 12-14 | Haus 1 | Eingang Nord
22529 Hamburg
tel: 040 / 52 10 59 - 10 | fax: -99
mail: in...@he...
home: www.heubach-media.de
Geschäftsführer|CEO: Matthias Heubach

Mieten Sie Ihre Computer, iPads & Drucker für Ihre Events bei:
http://www.milo-rental.com

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten haben, informieren Sie bitte sofort den Absender 
und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie 
die unbefugte Weitergabe dieser Mail ist nicht gestattet.
 
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the
material in this e-mail is strictly forbidden.


---
heubach media
Osterfeldstr. 12-14 | Haus 1 | Eingang Nord
22529 Hamburg
tel: 040 / 52 10 59 - 10 | fax: -99
mail: in...@he...
home: www.heubach-media.de
Geschäftsführer|CEO: Matthias Heubach

Mieten Sie Ihre Computer, iPads & Drucker für Ihre Events bei:
http://www.milo-rental.com

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten haben, informieren Sie bitte sofort den Absender 
und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie 
die unbefugte Weitergabe dieser Mail ist nicht gestattet.
 
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the
material in this e-mail is strictly forbidden.


---
heubach media
Osterfeldstr. 12-14 | Haus 1 | Eingang Nord
22529 Hamburg
tel: 040 / 52 10 59 - 10 | fax: -99
mail: in...@he...
home: www.heubach-media.de
Geschäftsführer|CEO: Matthias Heubach

Mieten Sie Ihre Computer, iPads & Drucker für Ihre Events bei:
http://www.milo-rental.com

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
erhalten haben, informieren Sie bitte sofort den Absender 
und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie 
die unbefugte Weitergabe dieser Mail ist nicht gestattet.
 
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the
material in this e-mail is strictly forbidden.

[Podofo-users] PdfXRef rewriting

[Francesco P. <ce...@gm...>]

Hello,

I just wanted to inform you that an important update has just been
pushed: The PdfXref class has been mostly rewritten[1] and cleaned to
address a serious PoDoFo bug. Per ISO 32000-2:2020 chapter 7.5.4
Cross-reference table "For a PDF file that has never been
incrementally updated, the cross-reference section shall contain only
one subsection, whose object numbering begins at 0". PoDoFo was not
strictly following this requirement, ending sometimes in producing
files that were unreadable[2] in Adobe Acrobat, especially when flat
saving files that were incrementally updated several times and with
many deleted objects. This change at first looked easy but 1 planned
working day turned to be at least 5, because the approach previously
adopted in PdfXRef was using several insertions with manual sorting
plus hammering with iterations in other locations, both of them were
not guaranteeing readability and easy to prove correctness to my
evaluation. It ended up being a big work that touches several places
in the code and fixes a multitude of bugs related to handling of XRef
sections. Since this is a sensible change, I urge you to have a look
and test it: you should notice a better use of free object XRef
entries, which stopped growing at each save. PoDoFo unit testing is
still lacking, and certainly the couple of tests I added is not enough
to fill the gap. Still, a lot of testing is done under the hood, and I
hope more PDF writing unit tests can still come in the future, also
based on the received feedback, if any.

I hope to have more exciting news for you soon.

Cheers,
Francesco

[1] https://github.com/podofo/podofo/commit/599de1b8cb01b7db55a196b6a4071d98963879cc
[2] https://github.com/podofo/podofo-resources/blob/master/TestFixInvalidCrossReferenceTable.pdf

Re: [Podofo-users] test failures in master?

[Francesco P. <ce...@gm...>]

CI agents I control don't reproduce this. Try have a look at this public
MAC github workflow:

https://github.com/podofo/podofo/actions/workflows/build-mac.yml
https://github.com/podofo/podofo/blob/master/.github/workflows/build-mac.yml

On Mon, 15 Sept 2025 at 16:26, Christopher Creutzig via Podofo-users <
pod...@li...> wrote:

> Hi everyone,
>
> With the current git HEAD master, I am getting test failures in the
> signature tests, on maca64:
>
> $ ctest --rerun-failed --output-on-failure
>
> Test project […]/podofo/build-maca64
>
>     Start 139: TestSignature1
>
> 1/4 Test #139: TestSignature1 ...................***Failed    0.24 sec
>
> Filters: TestSignature1
>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> podofo-unit is a Catch v2.13.7 host application.
>
> Run with -? for options
>
>
>
> -------------------------------------------------------------------------------
>
> TestSignature1
>
>
> -------------------------------------------------------------------------------
>
> […]/podofo/test/unit/SignatureTest.cpp:26
>
>
> ...............................................................................
>
>
> […]/podofo/test/unit/SignatureTest.cpp:26: FAILED:
>
>   {Unknown expression after the reported line}
>
> due to unexpected exception with message:
>
>   PdfErrorCode::IOError, Tried to do something unsupported to an I/O device
>
>   like seek a non-seekable input device
>
>   Callstack:t#0 Error Source: auxiliary/StreamDevice.cpp(857), Information:
>
>   Error accessing file […]/podofo/test/out/
>
>   TestSignature1.pdf
>
>
>
> ===============================================================================
>
> test cases: 1 | 1 failed
>
> assertions: 3 | 2 passed | 1 failed
>
>
>
>     Start 140: TestSignature2
>
> 2/4 Test #140: TestSignature2 ...................***Failed    0.20 sec
>
> Filters: TestSignature2
>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> podofo-unit is a Catch v2.13.7 host application.
>
> Run with -? for options
>
>
>
> -------------------------------------------------------------------------------
>
> TestSignature2
>
>
> -------------------------------------------------------------------------------
>
> […]/podofo/test/unit/SignatureTest.cpp:82
>
>
> ...............................................................................
>
>
> […]/podofo/test/unit/SignatureTest.cpp:82: FAILED:
>
> due to unexpected exception with message:
>
>   PdfErrorCode::IOError, Tried to do something unsupported to an I/O device
>
>   like seek a non-seekable input device
>
>   Callstack:t#0 Error Source: auxiliary/StreamDevice.cpp(857), Information:
>
>   Error accessing file […]/podofo/test/out/
>
>   TestSignature2.pdf
>
>
>
> ===============================================================================
>
> test cases: 1 | 1 failed
>
> assertions: 1 | 1 failed
>
>
>
>     Start 141: TestSignature3
>
> 3/4 Test #141: TestSignature3 ...................***Failed    0.12 sec
>
> Filters: TestSignature3
>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> podofo-unit is a Catch v2.13.7 host application.
>
> Run with -? for options
>
>
>
> -------------------------------------------------------------------------------
>
> TestSignature3
>
>
> -------------------------------------------------------------------------------
>
> […]/podofo/test/unit/SignatureTest.cpp:124
>
>
> ...............................................................................
>
>
> […]/podofo/test/unit/SignatureTest.cpp:124: FAILED:
>
> due to unexpected exception with message:
>
>   PdfErrorCode::IOError, Tried to do something unsupported to an I/O device
>
>   like seek a non-seekable input device
>
>   Callstack:t#0 Error Source: auxiliary/StreamDevice.cpp(857), Information:
>
>   Error accessing file […]/podofo/test/out/
>
>   TestSignature3.pdf
>
>
>
> ===============================================================================
>
> test cases: 1 | 1 failed
>
> assertions: 1 | 1 failed
>
>
>
>     Start 142: TestSignEncryptedDoc
>
> 4/4 Test #142: TestSignEncryptedDoc .............***Failed    0.12 sec
>
> Filters: TestSignEncryptedDoc
>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> podofo-unit is a Catch v2.13.7 host application.
>
> Run with -? for options
>
>
>
> -------------------------------------------------------------------------------
>
> TestSignEncryptedDoc
>
>
> -------------------------------------------------------------------------------
>
> […]/podofo/test/unit/SignatureTest.cpp:162
>
>
> ...............................................................................
>
>
> […]/podofo/test/unit/SignatureTest.cpp:162: FAILED:
>
> due to unexpected exception with message:
>
>   PdfErrorCode::IOError, Tried to do something unsupported to an I/O device
>
>   like seek a non-seekable input device
>
>   Callstack:t#0 Error Source: auxiliary/StreamDevice.cpp(857), Information:
>
>   Error accessing file […]/podofo/test/out/
>
>   TestSignEncryptedDoc.pdf
>
>
>
> ===============================================================================
>
> test cases: 1 | 1 failed
>
> assertions: 1 | 1 failed
>
>
>
>
> 0% tests passed, 4 tests failed out of 4
>
>
> Total Test time (real) =   0.73 sec
>
>
> The following tests FAILED:
>
> 139 - TestSignature1 (Failed)
>
> 140 - TestSignature2 (Failed)
>
> 141 - TestSignature3 (Failed)
>
> 142 - TestSignEncryptedDoc (Failed)
>
> Errors while running CTest
>
>
> Cheers,
> Christopher
>
> The MathWorks GmbH | Friedlandstr.18 | 52064 Aachen | District Court
> Aachen | HRB 8082 | Managing Directors: Bertrand Dissler, Steven D. Barbo,
> Jeanne O’Keefe
>
>
>
>
> _______________________________________________
> Podofo-users mailing list
> Pod...@li...
> https://lists.sourceforge.net/lists/listinfo/podofo-users
>

[Podofo-users] PoDoFo joins PDF Association

[Francesco P. <ce...@gm...>]

Hello,

I wanted to inform you that the PoDoFo Community joined the PDF
Association[1]. This allowed me to release some press news[2][3] for the
association audience/members and gave me the opportunity to submit a topic
for a presentation[4] that took place during the PDF Days Europe 2025 event
this week in Berlin[5]. The presentation is going to be published in the
PDF Association YouTube channel later this fall.

I'm sorry if I didn't announce this properly before the event: I talked
with Dominik a few months ago but it would have been a good idea also to
advertise the event here in the ML, just in case one of you was interested
in participating. I don't get easily caught up in a communication frenzy,
and this is the first breath I can take after a summer of intense work and
preparation for such an event (the presentation featured the XMP packets
validation that was recently committed into PoDoFo).

Just to inform you and be transparent about: I am personally sustaining the
expenses for joining the association for this year and 2026. I hope I will
be able to secure proper sponsorship for the next few years (I am already
working on this). Also please note: because of "PoDoFo community"
membership is still linked to my name, but I will ask to unlink it with the
next renewal. In the future I will try to write here earlier if other
events related to PoDoFo are going to happen. Unfortunately such seminars
like "PDF Days" events organized by the PDF Association are rare: they have
"PDF Week" events every six months but they are very technical/formal
events that are reserved for PDFA members.

Cheers,
Francesco

[1] https://pdfa.org/member/francesco-pretto/
[2] https://pdfa.org/product/podofo/
[3] https://pdfa.org/podofo-10-released/
[4]
https://pdfa.org/presentation/pdf-xmp-metadata-validation-with-relax-ng-schemas-and-the-podofo-library/
[5] https://pdfa.org/agenda/pdf-days-europe-2025/

Re: [Podofo-users] Patch for pdfParser - findToken function

[Francesco P. <ce...@gm...>]

On Wed, 27 Apr 2022 at 18:27, Michal Sudolsky <sud...@gm...> wrote:

> Attached are 6 PDF files and all of them open well in 3 pdf viewers I
> tested.
>

Hello, sorry for resurrecting this old thread. Here[1] you can find the old
Michael's message as it was answered by me (unfortunately the
original wasn't persisted in the archives for some reason). Shortly: all
parsing issues with those attached files are solved and unit tested in
PoDoFo. We also have a new recovery algorithm[2] that tries to rebuild
cross reference tables/streams in case reading the document structure fails
for any reason, similarly to what major PDF implementations do. All of this
will appear in PoDoFo 1.1.

Also [...] rev.pdf [...] has reordered xref and trailer. Note that there is
> nothing in the pdf specification which says that trailer and xref must be
> in particular order just that trailer is before startxref. It also does not
> say how far from the end can be trailer or startxref (only that %%EOF must
> be within 1024 bytes).
>

I tend to disagree with the statement that the trailer can appear before
xref, see ISO 32000-2:2020 "Figure 2 - Initial structure of a PDF" file or
any previous PDF reference.
This file is opened in recovery mode in pdf.js (as it was broken) and
that's the approach I decided to follow in PoDoFo as well.

[1]
https://www.mail-archive.com/pod...@li.../msg04811.html
[2]
https://github.com/podofo/podofo/commit/449622d57e7cfe8e4ec6fbd795832d3f4b8e736b

Re: [Podofo-users] LibXml2 Maintainer Stepping Down - Impact on Podofo 1.x ?

[zyx <zy...@gm...>]

On Wed, 2025-09-17 at 11:43 +0200, Francesco Pretto wrote:
> My 2 cents: at some point a new maintainer will be found, no reasons
> to worry too much right now: XML is not evolving that much in the
> foreseeable future.

	Hi,
I agree with that. There are too many users of it and there is also a
volunteer to help with the maintenance already, thus a reaction of this
kind, "eeks, the long time maintainer is moving away, everybody abandon
the project" is overreaction, to say the least.
	Bye,
	zyx

P.S.: see the linked original post mentioned in the re-post you
provided for more information

Re: [Podofo-users] LibXml2 Maintainer Stepping Down - Impact on Podofo 1.x ?

[Francesco P. <ce...@gm...>]

Brief answer as I am traveling: there are no alternatives for many things
libxml2 does, especially in the C only world, and you simply can't destroy
the huge ecosystem that is built around it. Also, as far as I know, there's
are no alternative relaxng validators (which is being used recently in
PoDoFo), either in C or in C++, so I am not currently searching for an
alternative at all. My 2 cents: at some point a new maintainer will be
found, no reasons to worry too much right now: XML is not evolving that
much in the foreseeable future.

On Wed, Sep 17, 2025, 10:53 F. E. <exl...@gm...> wrote:

> Hello podofo users,
>
> recently the last maintainer of LibXml2 announced their retirement from
> the project:
>
> https://www.phoronix.com/news/Libxml2-No-Maintainer
>
> Since Podofo 1.x also uses libxml2, and using an outdating xml parsing
> library posing security concerns the longer it is used, are there any
> considerations as to whether Podofo should stick with libxml2 or switch to
> another XML library in the (near) future?
>
> Regards,
>
> F.E.
> _______________________________________________
> Podofo-users mailing list
> Pod...@li...
> https://lists.sourceforge.net/lists/listinfo/podofo-users
>

[Podofo-users] LibXml2 Maintainer Stepping Down - Impact on Podofo 1.x ?

[F. E. <exl...@gm...>]

Hello podofo users,

recently the last maintainer of LibXml2 announced their retirement from the
project:

https://www.phoronix.com/news/Libxml2-No-Maintainer

Since Podofo 1.x also uses libxml2, and using an outdating xml parsing
library posing security concerns the longer it is used, are there any
considerations as to whether Podofo should stick with libxml2 or switch to
another XML library in the (near) future?

Regards,

F.E.

[Podofo-users] test failures in master?

[Christopher C. <ccr...@ma...>]

Hi everyone,

With the current git HEAD master, I am getting test failures in the signature tests, on maca64:


$ ctest --rerun-failed --output-on-failure

Test project […]/podofo/build-maca64

    Start 139: TestSignature1

1/4 Test #139: TestSignature1 ...................***Failed    0.24 sec

Filters: TestSignature1


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

podofo-unit is a Catch v2.13.7 host application.

Run with -? for options


-------------------------------------------------------------------------------

TestSignature1

-------------------------------------------------------------------------------

[…]/podofo/test/unit/SignatureTest.cpp:26

...............................................................................


[…]/podofo/test/unit/SignatureTest.cpp:26: FAILED:

  {Unknown expression after the reported line}

due to unexpected exception with message:

  PdfErrorCode::IOError, Tried to do something unsupported to an I/O device

  like seek a non-seekable input device

  Callstack:t#0 Error Source: auxiliary/StreamDevice.cpp(857), Information:

  Error accessing file […]/podofo/test/out/

  TestSignature1.pdf


===============================================================================

test cases: 1 | 1 failed

assertions: 3 | 2 passed | 1 failed



    Start 140: TestSignature2

2/4 Test #140: TestSignature2 ...................***Failed    0.20 sec

Filters: TestSignature2


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

podofo-unit is a Catch v2.13.7 host application.

Run with -? for options


-------------------------------------------------------------------------------

TestSignature2

-------------------------------------------------------------------------------

[…]/podofo/test/unit/SignatureTest.cpp:82

...............................................................................


[…]/podofo/test/unit/SignatureTest.cpp:82: FAILED:

due to unexpected exception with message:

  PdfErrorCode::IOError, Tried to do something unsupported to an I/O device

  like seek a non-seekable input device

  Callstack:t#0 Error Source: auxiliary/StreamDevice.cpp(857), Information:

  Error accessing file […]/podofo/test/out/

  TestSignature2.pdf


===============================================================================

test cases: 1 | 1 failed

assertions: 1 | 1 failed



    Start 141: TestSignature3

3/4 Test #141: TestSignature3 ...................***Failed    0.12 sec

Filters: TestSignature3


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

podofo-unit is a Catch v2.13.7 host application.

Run with -? for options


-------------------------------------------------------------------------------

TestSignature3

-------------------------------------------------------------------------------

[…]/podofo/test/unit/SignatureTest.cpp:124

...............................................................................


[…]/podofo/test/unit/SignatureTest.cpp:124: FAILED:

due to unexpected exception with message:

  PdfErrorCode::IOError, Tried to do something unsupported to an I/O device

  like seek a non-seekable input device

  Callstack:t#0 Error Source: auxiliary/StreamDevice.cpp(857), Information:

  Error accessing file […]/podofo/test/out/

  TestSignature3.pdf


===============================================================================

test cases: 1 | 1 failed

assertions: 1 | 1 failed



    Start 142: TestSignEncryptedDoc

4/4 Test #142: TestSignEncryptedDoc .............***Failed    0.12 sec

Filters: TestSignEncryptedDoc


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

podofo-unit is a Catch v2.13.7 host application.

Run with -? for options


-------------------------------------------------------------------------------

TestSignEncryptedDoc

-------------------------------------------------------------------------------

[…]/podofo/test/unit/SignatureTest.cpp:162

...............................................................................


[…]/podofo/test/unit/SignatureTest.cpp:162: FAILED:

due to unexpected exception with message:

  PdfErrorCode::IOError, Tried to do something unsupported to an I/O device

  like seek a non-seekable input device

  Callstack:t#0 Error Source: auxiliary/StreamDevice.cpp(857), Information:

  Error accessing file […]/podofo/test/out/

  TestSignEncryptedDoc.pdf


===============================================================================

test cases: 1 | 1 failed

assertions: 1 | 1 failed




0% tests passed, 4 tests failed out of 4


Total Test time (real) =   0.73 sec


The following tests FAILED:

139 - TestSignature1 (Failed)

140 - TestSignature2 (Failed)

141 - TestSignature3 (Failed)

142 - TestSignEncryptedDoc (Failed)

Errors while running CTest


Cheers,
Christopher


The MathWorks GmbH | Friedlandstr.18 | 52064 Aachen | District Court Aachen | HRB 8082 | Managing Directors: Bertrand Dissler, Steven D. Barbo, Jeanne O’Keefe

Re: [Podofo-users] Error in CMakeLists.txt?

[Francesco P. <ce...@gm...>]

On Tue, 19 Aug 2025 at 19:14, F. E. <exl...@gm...> wrote:

> I honestly don't know what I'm doing wrong. I'm just doing the basic
> stuff: Extracting the archive to a folder and then running cmake there,
> ...
>
%CMAKE_DIR%\*cmake.exe . <---------*
>

Maybe you lack a bit of context: for developers using CMake creating the
build files "in-source" or "in-tree" is neither common nor recommended,
see[1]. This means you should really try a out-of-source build directory,
meaning you create a build directory and run cmake from there locating
CMakelists.txt, eg. :

mkdir build
cd build
cmake .. # parent directory has CMakelists.txt

Try this and I believe it should work, and try the same way with libxml2.
If this works for you then I will consider explicitly disallowing
"in-source" builds.

Regards,
Francesco

[1] "In-source builds where the source and binary directories are the same
are supported but should be avoided if possible",
https://cmake.org/cmake/help/book/mastering-cmake/chapter/Getting%20Started.html#directory-structure

Re: [Podofo-users] Error in CMakeLists.txt?

[Francesco P. <ce...@gm...>]

On Tue, 19 Aug 2025 at 15:56, F. E. <exl...@gm...> wrote:

> And added "podofo" to the one path in the middle:
> [image: grafik.png]
>
> With this change, CMake successfully created solution and project files.
>

This is not correct as I am pretty much sure this will mess up the intended
headers deployment layout. Are you not using a separate build directory
(in-source build)? This may explain the error you are seeing. In that case
I may prefer to inhibit in-tree builds, as that target_source is
convenient to use and the system doesn't give me much more
alternatives other than recreating the wanted headers layout by copying all
the headers at some location first before installing.

> When trying to build the podofo projects, I get errors
about "\libxml\xmlversion.h" not existing.

Building lixml2 works for me with cmake. Maybe again you are in a case of
in-source build and the generation of that file fails because of some
unexpected condition.

Greetings,
Francesco

[Podofo-users] Error in CMakeLists.txt?

[F. E. <exl...@gm...>]

Hello podofo users,

I'm currently trying to introduce the new podofo v1.0.1 in our build, but I
think I encoutered an error in one of the CMakeLists.txt files:

After configuring is done, CMake is complaining something about directories:
[image: grafik.png]
After that, he seems to throw errors for each source file, e.g.:
[image: grafik.png]

I checked the mentioned CMakeLists.txt:116:
[image: grafik.png]

And added "podofo" to the one path in the middle:
[image: grafik.png]

With this change, CMake successfully created solution and project files.
But I don't really have any expirience with "fixing" CMake, so I cannot
rule out mess-ups from my side. Is this really an error in the CMakeLists
file, or did I do something wrong beforehand?

Another thing I'm struggling with right know is building libxml2 "right",
which is required with podofo 1.0 now. I know it's strictly nothing of
podofos concerns, but maybe someone can give me a hint here as well:
When trying to build the podofo projects, I get errors
about "\libxml\xmlversion.h" not existing. When checking the source files,
I see there's still a xmlversion.h.in file, so I guess the header should
have been generated from the in file, but somehow it did not happen. Can
someone tell me, how this generation is triggered? I guess it's via cmake
as well, and I also used it for building libxml2 projects just fine without
error. But the in-file just does not change.

Greetings,
F.E.

Re: [Podofo-users] PoDoFo 1.0.0 and 0.10.5 released

[Dominik S. <dom...@go...>]

Hello Francesco, Dear PoDoFo-Team!

This is amazing news! Finally, PoDoFo 1.0.0 is here!

I uploaded PoDoFo 0.1 in June 2006 and almost 20 years later 1.0.0 is there
- thanks to Francesco who gladly revived the project again, modernized and
enhanced it.

It makes me really happy to see the PoDoFo story continue! Thanks to
everybody who has contributed! Keep up the good work!

Kind regards,
 Dominik

PS: I hope everybody is upgrading soon to PoDoFo 1.0.0


On Sat, May 31, 2025 at 1:03 PM Francesco Pretto <ce...@gm...> wrote:

> Dear Dominik, podofo-users,
>
> PoDoFo 1.0.0[1] and 0.10.5[2] were just released. 0.10.5 is a
> maintenance release with several critical fixes while 1.0.0 is the big
> feature release we talked about in the past 2 years and a half, so I
> recommend checking out the changelog and the huge list of API
> cleanups[3]. As a last minute addition, starting with PoDoFo 1.0 the
> CMake integration[4] has been further improved so it will be super
> easy to consume it from package managers.
>
> Few more details about the 1.0.0 release:
> - Support policy: I decided to document[5] the current state of
> affairs. That is: there's a single LTS release that is supported for
> at least 2 years. The current LTS is still 0.10.x but it will be
> switched to 1.x something later on this year. This release is
> specifically thought for Linux distributions like RHEL, Ubuntu, etc. .
> Widening of the support policy can happen with the help of more
> developers/maintainers;
> - API stability: with 1.0.0 the API is now "protected" which hopefully
> It will mean stable for most people. More details on[5];
> - Tools: legacy PoDoFo tools are still unsupported, untested and
> unmaintained and I will be vocal against packaging tools compiled with
> 1.x. If you need the last "working" tools you will still need 0.9.x.
> This policy may change in the future;
> - Licensing: licensing is still LGPL2+. MPL2 licensing effort is not
> (yet) complete;
> - Next goals: rest (a bit), podofoimpose cleanups/improvements (and
> maybe others, but no promises), MPL2 licensing, recovery mode[6].
>
> If you are still a 0.9.x user: I urge you to upgrade. As the Angry
> Video Game Nerd says "You want to cut steak with a plastic spoon? No.
> Get the knife". Do yourself a favour: get PoDoFo 1.0.
>
> Cheers,
> Francesco
>
> [1] https://github.com/podofo/podofo/releases/tag/1.0.0
> [2] https://github.com/podofo/podofo/releases/tag/0.10.5
> [3] https://github.com/podofo/podofo/blob/master/API-MIGRATION.md
> [4]
> https://github.com/podofo/podofo?tab=readme-ov-file#consume-podofo-from-package-managers-with-cmake
> [5]
> https://github.com/podofo/podofo/wiki/PoDoFo-releases-life-cycle-and-API-stability
> [6] https://github.com/podofo/podofo/issues/242
>
>
> _______________________________________________
> Podofo-users mailing list
> Pod...@li...
> https://lists.sourceforge.net/lists/listinfo/podofo-users
>

[Podofo-users] PoDoFo 1.0.0 and 0.10.5 released

[Francesco P. <ce...@gm...>]

Dear Dominik, podofo-users,

PoDoFo 1.0.0[1] and 0.10.5[2] were just released. 0.10.5 is a
maintenance release with several critical fixes while 1.0.0 is the big
feature release we talked about in the past 2 years and a half, so I
recommend checking out the changelog and the huge list of API
cleanups[3]. As a last minute addition, starting with PoDoFo 1.0 the
CMake integration[4] has been further improved so it will be super
easy to consume it from package managers.

Few more details about the 1.0.0 release:
- Support policy: I decided to document[5] the current state of
affairs. That is: there's a single LTS release that is supported for
at least 2 years. The current LTS is still 0.10.x but it will be
switched to 1.x something later on this year. This release is
specifically thought for Linux distributions like RHEL, Ubuntu, etc. .
Widening of the support policy can happen with the help of more
developers/maintainers;
- API stability: with 1.0.0 the API is now "protected" which hopefully
It will mean stable for most people. More details on[5];
- Tools: legacy PoDoFo tools are still unsupported, untested and
unmaintained and I will be vocal against packaging tools compiled with
1.x. If you need the last "working" tools you will still need 0.9.x.
This policy may change in the future;
- Licensing: licensing is still LGPL2+. MPL2 licensing effort is not
(yet) complete;
- Next goals: rest (a bit), podofoimpose cleanups/improvements (and
maybe others, but no promises), MPL2 licensing, recovery mode[6].

If you are still a 0.9.x user: I urge you to upgrade. As the Angry
Video Game Nerd says "You want to cut steak with a plastic spoon? No.
Get the knife". Do yourself a favour: get PoDoFo 1.0.

Cheers,
Francesco

[1] https://github.com/podofo/podofo/releases/tag/1.0.0
[2] https://github.com/podofo/podofo/releases/tag/0.10.5
[3] https://github.com/podofo/podofo/blob/master/API-MIGRATION.md
[4] https://github.com/podofo/podofo?tab=readme-ov-file#consume-podofo-from-package-managers-with-cmake
[5] https://github.com/podofo/podofo/wiki/PoDoFo-releases-life-cycle-and-API-stability
[6] https://github.com/podofo/podofo/issues/242

Re: [Podofo-users] Completed Adobe Glyph List handling and Type1/TrueType glyph selection

[Francesco P. <ce...@gm...>]

Hello podofo-users,

PoDoFo 1.0.0-rc1 has been tagged. Unless a last minute critical bug is
filled, on Tuesday evening I will probably release 1.0.

Cheers,
Francesco

On Mon, 5 May 2025 at 22:09, Francesco Pretto <ce...@gm...> wrote:

> As I should be done with PoDoFo features for now, I will resume
> preparations for the 1.0 release with remaining (trivial) tasks and bug
> fixing. Stay tuned.
>
>

Re: [Podofo-users] Loading pdfs with large number of trailers / updates causes stack overflow

[Francesco P. <ce...@gm...>]

On Mon, 3 Mar 2025 at 16:59, F. E. <exl...@gm...> wrote:

> we recently had another issue with podofo crashing while parsing a pdf.
> The crashing pdf had 130 updates, but not with trailers this time, but xref
> streams.
>
>
Fixed in
https://github.com/podofo/podofo/commit/f83c1c2c91dd378db0ce5629cc36bbf460e75ecd
I also added a test case.

Cheers,
Francesco