You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@pdfbox.apache.org by Gili Tzabari <co...@gmail.com> on 2023/11/07 23:15:50 UTC
PDF 2.0, PDF/A-4 support
Hi,
I noticed that PDFBox 3.0 was recently released, but I can't tell what
the status/roadmap is for PDF 2.0 and PDF/A-4 support.
Can someone in the know please let me know where we stand?
Thanks,
Gili
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
RE: PDF 2.0, PDF/A-4 support
Posted by Peter Wyatt <pe...@gmail.com>.
The version of a PDF file does not mandate the features it must contain.
If you have a PDF 2.0 file with PDF 2.0 specific features then yes, you will have to use PDF/A-4 if preservation of those features is important, since PDF/A-4 files must always have a "%PDF-2.x" header.
But PDF 2.0 files may not have any PDF 2.0 features (it may only contain simple content compatible with PDF 1.1!) so you could theoretically "back-convert" to PDF 1.x and then use PDF/A-2 or PDF/A-3 (or even PDF/A-1) depending on the file and your needs. Both PDF/A-2 and PDF/A-3 for example must have headers "%PDF-1.x" for x=0...7. Of course software needs to know how to do this correctly!
Please also note that ISO 19005-4:2020 PDF/A-4 is currently undergoing a dated revision update at ISO.
> -----Original Message-----
> From: Gili Tzabari <co...@gmail.com>
> Sent: Friday, November 10, 2023 12:55 PM
> To: users@pdfbox.apache.org
> Subject: Re: PDF 2.0, PDF/A-4 support
>
> I am no PDF expert, so please bear with me :)
>
> If I understand you correctly, dropping preflight means that you're
> dropping PDF verification. And you're saying that VeraPDF provides PDF
> verification so nothing is really lost.
>
> The only part I didn't understand was:
>
> > You can create PDF/A-4 files like you can create PDF/A-1b files.
>
> Doesn't PDF/A-4 files require PDF 2.0 support? Don't they have a
> different file structure than PDF/A-1b files?
>
> Thank you,
> Gili
>
> On 2023-11-08 11:34, Tilman Hausherr wrote:
> > We don't have roadmaps. If you need a PDF 2.0 feature, tell us which
> > one and why. PDF/A-4 isn't a topic because preflight isn't developed
> > further. Use VeraPDF instead. You can create PDF/A-4 files like you
> > can create PDF/A-1b files.
> >
> > Tilman
> >
> > On 08.11.2023 00:15, Gili Tzabari wrote:
> >> Hi,
> >>
> >> I noticed that PDFBox 3.0 was recently released, but I can't tell
> >> what the status/roadmap is for PDF 2.0 and PDF/A-4 support.
> >>
> >> Can someone in the know please let me know where we stand?
> >>
> >> Thanks,
> >> Gili
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> >> For additional commands, e-mail: users-help@pdfbox.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> > For additional commands, e-mail: users-help@pdfbox.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: users-help@pdfbox.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
Re: PDF 2.0, PDF/A-4 support
Posted by Gili Tzabari <co...@gmail.com>.
I am no PDF expert, so please bear with me :)
If I understand you correctly, dropping preflight means that you're
dropping PDF verification. And you're saying that VeraPDF provides PDF
verification so nothing is really lost.
The only part I didn't understand was:
> You can create PDF/A-4 files like you can create PDF/A-1b files.
Doesn't PDF/A-4 files require PDF 2.0 support? Don't they have a
different file structure than PDF/A-1b files?
Thank you,
Gili
On 2023-11-08 11:34, Tilman Hausherr wrote:
> We don't have roadmaps. If you need a PDF 2.0 feature, tell us which
> one and why. PDF/A-4 isn't a topic because preflight isn't developed
> further. Use VeraPDF instead. You can create PDF/A-4 files like you
> can create PDF/A-1b files.
>
> Tilman
>
> On 08.11.2023 00:15, Gili Tzabari wrote:
>> Hi,
>>
>> I noticed that PDFBox 3.0 was recently released, but I can't tell
>> what the status/roadmap is for PDF 2.0 and PDF/A-4 support.
>>
>> Can someone in the know please let me know where we stand?
>>
>> Thanks,
>> Gili
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
>> For additional commands, e-mail: users-help@pdfbox.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: users-help@pdfbox.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
RE: PDF 2.0, PDF/A-4 support
Posted by Peter Wyatt <pe...@gmail.com>.
That's still a great start!
And not a problem for OutputIntents until PDFBox starts doing compliant rendering of PDF/X or PDF/A, as "general purpose" PDF 2.0 does not mandate their support.
Thanks.
> -----Original Message-----
> From: Tilman Hausherr <TH...@t-online.de>
> Sent: Friday, November 10, 2023 5:17 AM
> To: users@pdfbox.apache.org
> Subject: Re: PDF 2.0, PDF/A-4 support
>
> Hi Peter,
>
> That's a lot... I'll create issues for some of these topics. The
> negative dash phase thing has been fixed in the latest release :
> https://issues.apache.org/jira/browse/PDFBOX-5636
>
> Things that might be possible:
> - UTF-8
> - Encryption
> - Colorburn / Colordodge
>
> The fill & stroke problem is a problem with Java itself, because it
> doesn't offer a combined fill & stroke.
>
> OutputIntents - we don't support these at all, so we'd have to start
> supporting it.
>
> Tilman
>
> On 09.11.2023 02:28, Peter Wyatt wrote:
> > I would think supporting the following PDF 2.0 features are highly relevant, given that other implementations
> are already generating PDF 2.0 files today (see https://pdfa.org/supporting-pdf20/):
> >
> > * UTF-8 support for user-visible strings, such as bookmarks (outlines), OCG layer names, certain annot fields,
> etc. Missing support results in the ugly display or extraction of "mojibake" for the UTF-8 BoMs. See
> https://pdfa.org/understanding-utf-8-in-pdf-2-0. Note that this does NOT impact content streams or text
> extraction (unless you also combine with Logical Structure)!
> >
> > * the latest encryption (AES-GCM 256 bit), dig-sig, hash algorithms, and Unicode password support which is FAR
> more up-to-date and secure than all legacy crypto. 3rd parties are already generating such files which will
> otherwise be unreadable/unprocessable by PDFBox. I don't know what crypto library PDFBox uses, but all the new
> algorithms are standard modern crypto algorithms. Unicode passwords also follow the latest ICU (not knowing what
> you use internally) but be careful so legacy files continue to work.
> >
> > * if high-quality semantic content extraction is important, then updating for PDF 2.0 standard structure types,
> although this is likely to be a larger dev effort.
> >
> >
> > If you want to address rendering issues, then:
> >
> > * PLEASE PLEASE PLEASE fix your incorrect rendering of "fill and stroke" in the presence of transparency! See
> https://github.com/pdf-association/pdf-differences/blob/main/Atomic-Fill%2BStroke/README.md
> >
> > * making sure you using the correct blend mode formulae for ColorBurn and ColorDodge (from 2009 - I have not
> checked your implementation): https://github.com/pdf-association/pdf-differences/tree/main/ColorBurn-ColorDodge
> >
> > * ensuring negative dash phase is correct (previously unstated as what to do) - see https://github.com/pdf-
> association/pdf-differences/tree/main/Negative-DashPhase
> >
> > * page-based OutputIntents. Already in use, especially in print-centric workflows where page merging and
> imposition across PDFs is now far easier to do. Implementation update to select a page-based OutputIntent ahead
> of the document-level OutputIntent should be relatively easy.
> >
> > * the use of transparency and blend mode of an annotations appearance stream when rendered onto a page (not
> _within_ the annot).
> >
> >
> > Obviously there are other PDF 2.0 features but these would be my go-to short list for starting to address the
> most obvious visible differences.
> > See also https://pdfa.org/how-to-get-started-with-pdf-2-0/ since reporting a simple PDF version is unlikely to
> withstand the test of time...
> >
> >
> > Of course I am also biased 😊 - and I'm not a Java expert!
> >
> >
> >> -----Original Message-----
> >> From: Tilman Hausherr <TH...@t-online.de>
> >> Sent: Thursday, November 9, 2023 3:35 AM
> >> To: users@pdfbox.apache.org
> >> Subject: Re: PDF 2.0, PDF/A-4 support
> >>
> >> We don't have roadmaps. If you need a PDF 2.0 feature, tell us which one
> >> and why. PDF/A-4 isn't a topic because preflight isn't developed
> >> further. Use VeraPDF instead. You can create PDF/A-4 files like you can
> >> create PDF/A-1b files.
> >>
> >> Tilman
> >>
> >> On 08.11.2023 00:15, Gili Tzabari wrote:
> >>> Hi,
> >>>
> >>> I noticed that PDFBox 3.0 was recently released, but I can't tell what
> >>> the status/roadmap is for PDF 2.0 and PDF/A-4 support.
> >>>
> >>> Can someone in the know please let me know where we stand?
> >>>
> >>> Thanks,
> >>> Gili
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> >>> For additional commands, e-mail: users-help@pdfbox.apache.org
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> >> For additional commands, e-mail: users-help@pdfbox.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> > For additional commands, e-mail: users-help@pdfbox.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: users-help@pdfbox.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
Re: PDF 2.0, PDF/A-4 support
Posted by Tilman Hausherr <TH...@t-online.de>.
On 11.11.2023 07:35, Maruan Sahyoun wrote:
> Let‘s create tickets for each point and we include them in our release planning.
> WDYT
+1
Tilman
>
> Maruan
>
>> Am 11.11.2023 um 05:32 schrieb Tilman Hausherr <TH...@t-online.de>:
>>
>> It turns out that the Colorburn / Colordodge change was done 5 years ago:
>>
>> https://svn.apache.org/viewvc?view=revision&revision=1823593
>>
>> The other 2 ones definitively not. I also found the pdf20-utf8-test.pdf file from January 2022 in my directory. So much things to do...
>>
>> Tilman
>>
>>> On 09.11.2023 19:17, Tilman Hausherr wrote:
>>> Hi Peter,
>>>
>>> That's a lot... I'll create issues for some of these topics. The negative dash phase thing has been fixed in the latest release :
>>> https://issues.apache.org/jira/browse/PDFBOX-5636
>>>
>>> Things that might be possible:
>>> - UTF-8
>>> - Encryption
>>> - Colorburn / Colordodge
>>>
>>> The fill & stroke problem is a problem with Java itself, because it doesn't offer a combined fill & stroke.
>>>
>>> OutputIntents - we don't support these at all, so we'd have to start supporting it.
>>>
>>> Tilman
>>>
>>>> On 09.11.2023 02:28, Peter Wyatt wrote:
>>>> I would think supporting the following PDF 2.0 features are highly relevant, given that other implementations are already generating PDF 2.0 files today (see https://pdfa.org/supporting-pdf20/):
>>>>
>>>> * UTF-8 support for user-visible strings, such as bookmarks (outlines), OCG layer names, certain annot fields, etc. Missing support results in the ugly display or extraction of "mojibake" for the UTF-8 BoMs. See https://pdfa.org/understanding-utf-8-in-pdf-2-0. Note that this does NOT impact content streams or text extraction (unless you also combine with Logical Structure)!
>>>>
>>>> * the latest encryption (AES-GCM 256 bit), dig-sig, hash algorithms, and Unicode password support which is FAR more up-to-date and secure than all legacy crypto. 3rd parties are already generating such files which will otherwise be unreadable/unprocessable by PDFBox. I don't know what crypto library PDFBox uses, but all the new algorithms are standard modern crypto algorithms. Unicode passwords also follow the latest ICU (not knowing what you use internally) but be careful so legacy files continue to work.
>>>>
>>>> * if high-quality semantic content extraction is important, then updating for PDF 2.0 standard structure types, although this is likely to be a larger dev effort.
>>>>
>>>>
>>>> If you want to address rendering issues, then:
>>>>
>>>> * PLEASE PLEASE PLEASE fix your incorrect rendering of "fill and stroke" in the presence of transparency! See https://github.com/pdf-association/pdf-differences/blob/main/Atomic-Fill%2BStroke/README.md
>>>>
>>>> * making sure you using the correct blend mode formulae for ColorBurn and ColorDodge (from 2009 - I have not checked your implementation): https://github.com/pdf-association/pdf-differences/tree/main/ColorBurn-ColorDodge
>>>>
>>>> * ensuring negative dash phase is correct (previously unstated as what to do) - see https://github.com/pdf-association/pdf-differences/tree/main/Negative-DashPhase
>>>>
>>>> * page-based OutputIntents. Already in use, especially in print-centric workflows where page merging and imposition across PDFs is now far easier to do. Implementation update to select a page-based OutputIntent ahead of the document-level OutputIntent should be relatively easy.
>>>>
>>>> * the use of transparency and blend mode of an annotations appearance stream when rendered onto a page (not _within_ the annot).
>>>>
>>>>
>>>> Obviously there are other PDF 2.0 features but these would be my go-to short list for starting to address the most obvious visible differences.
>>>> See also https://pdfa.org/how-to-get-started-with-pdf-2-0/ since reporting a simple PDF version is unlikely to withstand the test of time...
>>>>
>>>>
>>>> Of course I am also biased 😊 - and I'm not a Java expert!
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
>> For additional commands, e-mail: users-help@pdfbox.apache.org
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: users-help@pdfbox.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
Re: PDF 2.0, PDF/A-4 support
Posted by Maruan Sahyoun <sa...@fileaffairs.de>.
Let‘s create tickets for each point and we include them in our release planning.
WDYT
Maruan
> Am 11.11.2023 um 05:32 schrieb Tilman Hausherr <TH...@t-online.de>:
>
> It turns out that the Colorburn / Colordodge change was done 5 years ago:
>
> https://svn.apache.org/viewvc?view=revision&revision=1823593
>
> The other 2 ones definitively not. I also found the pdf20-utf8-test.pdf file from January 2022 in my directory. So much things to do...
>
> Tilman
>
>> On 09.11.2023 19:17, Tilman Hausherr wrote:
>> Hi Peter,
>>
>> That's a lot... I'll create issues for some of these topics. The negative dash phase thing has been fixed in the latest release :
>> https://issues.apache.org/jira/browse/PDFBOX-5636
>>
>> Things that might be possible:
>> - UTF-8
>> - Encryption
>> - Colorburn / Colordodge
>>
>> The fill & stroke problem is a problem with Java itself, because it doesn't offer a combined fill & stroke.
>>
>> OutputIntents - we don't support these at all, so we'd have to start supporting it.
>>
>> Tilman
>>
>>> On 09.11.2023 02:28, Peter Wyatt wrote:
>>> I would think supporting the following PDF 2.0 features are highly relevant, given that other implementations are already generating PDF 2.0 files today (see https://pdfa.org/supporting-pdf20/):
>>>
>>> * UTF-8 support for user-visible strings, such as bookmarks (outlines), OCG layer names, certain annot fields, etc. Missing support results in the ugly display or extraction of "mojibake" for the UTF-8 BoMs. See https://pdfa.org/understanding-utf-8-in-pdf-2-0. Note that this does NOT impact content streams or text extraction (unless you also combine with Logical Structure)!
>>>
>>> * the latest encryption (AES-GCM 256 bit), dig-sig, hash algorithms, and Unicode password support which is FAR more up-to-date and secure than all legacy crypto. 3rd parties are already generating such files which will otherwise be unreadable/unprocessable by PDFBox. I don't know what crypto library PDFBox uses, but all the new algorithms are standard modern crypto algorithms. Unicode passwords also follow the latest ICU (not knowing what you use internally) but be careful so legacy files continue to work.
>>>
>>> * if high-quality semantic content extraction is important, then updating for PDF 2.0 standard structure types, although this is likely to be a larger dev effort.
>>>
>>>
>>> If you want to address rendering issues, then:
>>>
>>> * PLEASE PLEASE PLEASE fix your incorrect rendering of "fill and stroke" in the presence of transparency! See https://github.com/pdf-association/pdf-differences/blob/main/Atomic-Fill%2BStroke/README.md
>>>
>>> * making sure you using the correct blend mode formulae for ColorBurn and ColorDodge (from 2009 - I have not checked your implementation): https://github.com/pdf-association/pdf-differences/tree/main/ColorBurn-ColorDodge
>>>
>>> * ensuring negative dash phase is correct (previously unstated as what to do) - see https://github.com/pdf-association/pdf-differences/tree/main/Negative-DashPhase
>>>
>>> * page-based OutputIntents. Already in use, especially in print-centric workflows where page merging and imposition across PDFs is now far easier to do. Implementation update to select a page-based OutputIntent ahead of the document-level OutputIntent should be relatively easy.
>>>
>>> * the use of transparency and blend mode of an annotations appearance stream when rendered onto a page (not _within_ the annot).
>>>
>>>
>>> Obviously there are other PDF 2.0 features but these would be my go-to short list for starting to address the most obvious visible differences.
>>> See also https://pdfa.org/how-to-get-started-with-pdf-2-0/ since reporting a simple PDF version is unlikely to withstand the test of time...
>>>
>>>
>>> Of course I am also biased 😊 - and I'm not a Java expert!
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: users-help@pdfbox.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
Re: PDF 2.0, PDF/A-4 support
Posted by Tilman Hausherr <TH...@t-online.de>.
It turns out that the Colorburn / Colordodge change was done 5 years ago:
https://svn.apache.org/viewvc?view=revision&revision=1823593
The other 2 ones definitively not. I also found the pdf20-utf8-test.pdf
file from January 2022 in my directory. So much things to do...
Tilman
On 09.11.2023 19:17, Tilman Hausherr wrote:
> Hi Peter,
>
> That's a lot... I'll create issues for some of these topics. The
> negative dash phase thing has been fixed in the latest release :
> https://issues.apache.org/jira/browse/PDFBOX-5636
>
> Things that might be possible:
> - UTF-8
> - Encryption
> - Colorburn / Colordodge
>
> The fill & stroke problem is a problem with Java itself, because it
> doesn't offer a combined fill & stroke.
>
> OutputIntents - we don't support these at all, so we'd have to start
> supporting it.
>
> Tilman
>
> On 09.11.2023 02:28, Peter Wyatt wrote:
>> I would think supporting the following PDF 2.0 features are highly
>> relevant, given that other implementations are already generating PDF
>> 2.0 files today (see https://pdfa.org/supporting-pdf20/):
>>
>> * UTF-8 support for user-visible strings, such as bookmarks
>> (outlines), OCG layer names, certain annot fields, etc. Missing
>> support results in the ugly display or extraction of "mojibake" for
>> the UTF-8 BoMs. See https://pdfa.org/understanding-utf-8-in-pdf-2-0.
>> Note that this does NOT impact content streams or text extraction
>> (unless you also combine with Logical Structure)!
>>
>> * the latest encryption (AES-GCM 256 bit), dig-sig, hash algorithms,
>> and Unicode password support which is FAR more up-to-date and secure
>> than all legacy crypto. 3rd parties are already generating such files
>> which will otherwise be unreadable/unprocessable by PDFBox. I don't
>> know what crypto library PDFBox uses, but all the new algorithms are
>> standard modern crypto algorithms. Unicode passwords also follow the
>> latest ICU (not knowing what you use internally) but be careful so
>> legacy files continue to work.
>>
>> * if high-quality semantic content extraction is important, then
>> updating for PDF 2.0 standard structure types, although this is
>> likely to be a larger dev effort.
>>
>>
>> If you want to address rendering issues, then:
>>
>> * PLEASE PLEASE PLEASE fix your incorrect rendering of "fill and
>> stroke" in the presence of transparency! See
>> https://github.com/pdf-association/pdf-differences/blob/main/Atomic-Fill%2BStroke/README.md
>>
>> * making sure you using the correct blend mode formulae for ColorBurn
>> and ColorDodge (from 2009 - I have not checked your implementation):
>> https://github.com/pdf-association/pdf-differences/tree/main/ColorBurn-ColorDodge
>>
>> * ensuring negative dash phase is correct (previously unstated as
>> what to do) - see
>> https://github.com/pdf-association/pdf-differences/tree/main/Negative-DashPhase
>>
>> * page-based OutputIntents. Already in use, especially in
>> print-centric workflows where page merging and imposition across PDFs
>> is now far easier to do. Implementation update to select a page-based
>> OutputIntent ahead of the document-level OutputIntent should be
>> relatively easy.
>>
>> * the use of transparency and blend mode of an annotations appearance
>> stream when rendered onto a page (not _within_ the annot).
>>
>>
>> Obviously there are other PDF 2.0 features but these would be my
>> go-to short list for starting to address the most obvious visible
>> differences.
>> See also https://pdfa.org/how-to-get-started-with-pdf-2-0/ since
>> reporting a simple PDF version is unlikely to withstand the test of
>> time...
>>
>>
>> Of course I am also biased 😊 - and I'm not a Java expert!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
Re: PDF 2.0, PDF/A-4 support
Posted by Tilman Hausherr <TH...@t-online.de>.
Hi Peter,
That's a lot... I'll create issues for some of these topics. The
negative dash phase thing has been fixed in the latest release :
https://issues.apache.org/jira/browse/PDFBOX-5636
Things that might be possible:
- UTF-8
- Encryption
- Colorburn / Colordodge
The fill & stroke problem is a problem with Java itself, because it
doesn't offer a combined fill & stroke.
OutputIntents - we don't support these at all, so we'd have to start
supporting it.
Tilman
On 09.11.2023 02:28, Peter Wyatt wrote:
> I would think supporting the following PDF 2.0 features are highly relevant, given that other implementations are already generating PDF 2.0 files today (see https://pdfa.org/supporting-pdf20/):
>
> * UTF-8 support for user-visible strings, such as bookmarks (outlines), OCG layer names, certain annot fields, etc. Missing support results in the ugly display or extraction of "mojibake" for the UTF-8 BoMs. See https://pdfa.org/understanding-utf-8-in-pdf-2-0. Note that this does NOT impact content streams or text extraction (unless you also combine with Logical Structure)!
>
> * the latest encryption (AES-GCM 256 bit), dig-sig, hash algorithms, and Unicode password support which is FAR more up-to-date and secure than all legacy crypto. 3rd parties are already generating such files which will otherwise be unreadable/unprocessable by PDFBox. I don't know what crypto library PDFBox uses, but all the new algorithms are standard modern crypto algorithms. Unicode passwords also follow the latest ICU (not knowing what you use internally) but be careful so legacy files continue to work.
>
> * if high-quality semantic content extraction is important, then updating for PDF 2.0 standard structure types, although this is likely to be a larger dev effort.
>
>
> If you want to address rendering issues, then:
>
> * PLEASE PLEASE PLEASE fix your incorrect rendering of "fill and stroke" in the presence of transparency! See https://github.com/pdf-association/pdf-differences/blob/main/Atomic-Fill%2BStroke/README.md
>
> * making sure you using the correct blend mode formulae for ColorBurn and ColorDodge (from 2009 - I have not checked your implementation): https://github.com/pdf-association/pdf-differences/tree/main/ColorBurn-ColorDodge
>
> * ensuring negative dash phase is correct (previously unstated as what to do) - see https://github.com/pdf-association/pdf-differences/tree/main/Negative-DashPhase
>
> * page-based OutputIntents. Already in use, especially in print-centric workflows where page merging and imposition across PDFs is now far easier to do. Implementation update to select a page-based OutputIntent ahead of the document-level OutputIntent should be relatively easy.
>
> * the use of transparency and blend mode of an annotations appearance stream when rendered onto a page (not _within_ the annot).
>
>
> Obviously there are other PDF 2.0 features but these would be my go-to short list for starting to address the most obvious visible differences.
> See also https://pdfa.org/how-to-get-started-with-pdf-2-0/ since reporting a simple PDF version is unlikely to withstand the test of time...
>
>
> Of course I am also biased 😊 - and I'm not a Java expert!
>
>
>> -----Original Message-----
>> From: Tilman Hausherr <TH...@t-online.de>
>> Sent: Thursday, November 9, 2023 3:35 AM
>> To: users@pdfbox.apache.org
>> Subject: Re: PDF 2.0, PDF/A-4 support
>>
>> We don't have roadmaps. If you need a PDF 2.0 feature, tell us which one
>> and why. PDF/A-4 isn't a topic because preflight isn't developed
>> further. Use VeraPDF instead. You can create PDF/A-4 files like you can
>> create PDF/A-1b files.
>>
>> Tilman
>>
>> On 08.11.2023 00:15, Gili Tzabari wrote:
>>> Hi,
>>>
>>> I noticed that PDFBox 3.0 was recently released, but I can't tell what
>>> the status/roadmap is for PDF 2.0 and PDF/A-4 support.
>>>
>>> Can someone in the know please let me know where we stand?
>>>
>>> Thanks,
>>> Gili
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
>>> For additional commands, e-mail: users-help@pdfbox.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
>> For additional commands, e-mail: users-help@pdfbox.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: users-help@pdfbox.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
Re: PDF 2.0, PDF/A-4 support
Posted by Tilman Hausherr <TH...@t-online.de>.
On 09.11.2023 03:39, John Lussmyer wrote:
> On 11/8/2023 5:28 PM, Peter Wyatt wrote:
>> I would think supporting the following PDF 2.0 features are highly
>> relevant, given that other implementations are already generating PDF
>> 2.0 files today (seehttps://pdfa.org/supporting-pdf20/)
>
> A bunch of useful suggestions elided..
>
> What I REALLY REALLY need is support for Overprint and Knockout when
> Rendering to an image. I run into too many PDF's that are
> unrecognizable when generating an image due to this.
>
I doubt that will happen soon... it is very tricky. Watch this video to
understand why:
https://www.youtube.com/watch?v=TiqDqd-1pwU&t=7s
Tilman
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
Re: PDF 2.0, PDF/A-4 support
Posted by John Lussmyer <Co...@CasaDelGato.Com>.
On 11/8/2023 5:28 PM, Peter Wyatt wrote:
> I would think supporting the following PDF 2.0 features are highly relevant, given that other implementations are already generating PDF 2.0 files today (seehttps://pdfa.org/supporting-pdf20/)
A bunch of useful suggestions elided..
What I REALLY REALLY need is support for Overprint and Knockout when
Rendering to an image. I run into too many PDF's that are unrecognizable
when generating an image due to this.
RE: PDF 2.0, PDF/A-4 support
Posted by Peter Wyatt <pe...@gmail.com>.
I would think supporting the following PDF 2.0 features are highly relevant, given that other implementations are already generating PDF 2.0 files today (see https://pdfa.org/supporting-pdf20/):
* UTF-8 support for user-visible strings, such as bookmarks (outlines), OCG layer names, certain annot fields, etc. Missing support results in the ugly display or extraction of "mojibake" for the UTF-8 BoMs. See https://pdfa.org/understanding-utf-8-in-pdf-2-0. Note that this does NOT impact content streams or text extraction (unless you also combine with Logical Structure)!
* the latest encryption (AES-GCM 256 bit), dig-sig, hash algorithms, and Unicode password support which is FAR more up-to-date and secure than all legacy crypto. 3rd parties are already generating such files which will otherwise be unreadable/unprocessable by PDFBox. I don't know what crypto library PDFBox uses, but all the new algorithms are standard modern crypto algorithms. Unicode passwords also follow the latest ICU (not knowing what you use internally) but be careful so legacy files continue to work.
* if high-quality semantic content extraction is important, then updating for PDF 2.0 standard structure types, although this is likely to be a larger dev effort.
If you want to address rendering issues, then:
* PLEASE PLEASE PLEASE fix your incorrect rendering of "fill and stroke" in the presence of transparency! See https://github.com/pdf-association/pdf-differences/blob/main/Atomic-Fill%2BStroke/README.md
* making sure you using the correct blend mode formulae for ColorBurn and ColorDodge (from 2009 - I have not checked your implementation): https://github.com/pdf-association/pdf-differences/tree/main/ColorBurn-ColorDodge
* ensuring negative dash phase is correct (previously unstated as what to do) - see https://github.com/pdf-association/pdf-differences/tree/main/Negative-DashPhase
* page-based OutputIntents. Already in use, especially in print-centric workflows where page merging and imposition across PDFs is now far easier to do. Implementation update to select a page-based OutputIntent ahead of the document-level OutputIntent should be relatively easy.
* the use of transparency and blend mode of an annotations appearance stream when rendered onto a page (not _within_ the annot).
Obviously there are other PDF 2.0 features but these would be my go-to short list for starting to address the most obvious visible differences.
See also https://pdfa.org/how-to-get-started-with-pdf-2-0/ since reporting a simple PDF version is unlikely to withstand the test of time...
Of course I am also biased 😊 - and I'm not a Java expert!
> -----Original Message-----
> From: Tilman Hausherr <TH...@t-online.de>
> Sent: Thursday, November 9, 2023 3:35 AM
> To: users@pdfbox.apache.org
> Subject: Re: PDF 2.0, PDF/A-4 support
>
> We don't have roadmaps. If you need a PDF 2.0 feature, tell us which one
> and why. PDF/A-4 isn't a topic because preflight isn't developed
> further. Use VeraPDF instead. You can create PDF/A-4 files like you can
> create PDF/A-1b files.
>
> Tilman
>
> On 08.11.2023 00:15, Gili Tzabari wrote:
> > Hi,
> >
> > I noticed that PDFBox 3.0 was recently released, but I can't tell what
> > the status/roadmap is for PDF 2.0 and PDF/A-4 support.
> >
> > Can someone in the know please let me know where we stand?
> >
> > Thanks,
> > Gili
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> > For additional commands, e-mail: users-help@pdfbox.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: users-help@pdfbox.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org
Re: PDF 2.0, PDF/A-4 support
Posted by Tilman Hausherr <TH...@t-online.de>.
We don't have roadmaps. If you need a PDF 2.0 feature, tell us which one
and why. PDF/A-4 isn't a topic because preflight isn't developed
further. Use VeraPDF instead. You can create PDF/A-4 files like you can
create PDF/A-1b files.
Tilman
On 08.11.2023 00:15, Gili Tzabari wrote:
> Hi,
>
> I noticed that PDFBox 3.0 was recently released, but I can't tell what
> the status/roadmap is for PDF 2.0 and PDF/A-4 support.
>
> Can someone in the know please let me know where we stand?
>
> Thanks,
> Gili
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
> For additional commands, e-mail: users-help@pdfbox.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: users-help@pdfbox.apache.org