Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X
Hello everyone,
PDF/UA (in ALD) is a very complex theme as it is a ISO Standard which allows "some" Document structures but "not everything". PDF/X or PDF/A never has such limitations. To find here a way is hard enough. Some of the templates evolve over years with several techniques.
There is then a mix of Showstrings, Script, Perl, JavaScript and PI's - or everything which works in the last 20 years. This causes new problems. For example, a <?> disrupt the tagging structure for a PDF/UA.
At the end you cannot find a way to a PDF/UA as you never know where the Problems come from.
To solve one Problem, the idea was that PTC offer some Samples.
Basics (Documentation and Test)
1. There is a good Documentation ... Tagged PDF Best Practice Guide: Syntax - For developers implementing ISO 14289-1 (PDF/UA) - see "pdfa.org"
2. And a good test Tool (PAC2024) to evaluate the results in 3 quality levels. I think it works for everyone if the Sample is PDF/UA Compatible. The other both Level "WCAG" and "Quality" are optional in my opinion.
Samples
I suggest Samples (as "3D" and "PDF/UA") which shows one isolated situation in one document:
The first PDF/UA has nothing more as one Headline and Text. Everything else based on this Document
- Footnotes
- TOC
- Links
- Linked TOC
- Special Characters and the use of "ActualText" with PUA Unicode Chars
- Tables
- Lists
- Images
etc ...
Why isolated?
- Some techniques are simply not allowed in any combination. We show them in a simple tagging environment and a flat structure.
- This maybe helps to understand how it works and how to integrate this in a Customer's Document
- It also helps to compare the Documentation, like the "best practice guides".
- it maybe helps to identify some unexpected bugs between ALD and the PDFLib if we put not everything into one document.
PI's or JavaScript?
I guess JavaScript is the more flexible technique, but PTC also offer the PI's. We also have the Problem that not all Customers works with JavaScript as they have old templates.
Can we force them to spend much time to transform their templates? I'm not sure in this case.
Best wishes
Frank
Hi @DATACOPYSupport
Thank you for your question.
Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.
Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.
Best regards,
Hey Frank - I'll do what I can before the next feature release towards the end of the year. Do you have any specific content you'd want this based on? Or just purely abstract?
Simon
Hi Simon,
the first concrete questions are:
- footnotes in PDF/UA
- linked TOC in PDF/UA and ...
- Special Characters and the use of "ActualText" with PUA Unicode Chars in PDF/UA.
everything else is good to know and sooner or later helpful
I prefer a simple flat Document which shows only one issue per Document (maybe in JavaScript).
This is easier to handle for everyone including PTC.
It is also maybe important to collect all the problems outside the tagging issues to help Developer to identify issues they cannot see. For example "graphic objects in Footnotes" (SPR 1608027) or a "<?>" (17705705) etc ... until the "tpdftagpreview" (SPR 1608027) is repaired in 12.3.1.0 in May 2025. But this can be collected in separate Articles.
Thanks
Frank
Hey Simon, thank you for looking after ALD, which is now for Hebrew and other RTL-texts a delight!
Works like a charm, Easy and simple. Thanks a lot.
Transfering oder translating the existing structure (tags) from *.3d into *.pdf is quite a task.
There is the document PDF_Tagging_Sampler.3d.
On page 8 there is the heading *Footnote*, but just the heading.
After a lot of tests I am still struggling with the footnotes.
Today I've got this message:
[18002] begin_item: 'Note' element requires 'id' option with non-empty value in PDF/UA
(0: "afn1__1_1"#7)
PDF creation aborted
Whatever #18002 could be.
Long story short.
It would be extremely helpful to get some real life samples before December.
Just a few snippets of code, blue code for the elderly, for footnotes/endnotes, links and alternate text.
There are some documents, but they are not as simple as the implementation and forwarding of tags from ALD into PDF should be, imho.
And it would help a lot of other users too, I guess.
After nearly memorizing the help files, some examples would be a game changer.
Thank you.
Kind Regards,
Jean