Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
2

BUG: Named Destinations not found if strings are in a different format

New Here ,
Jul 21, 2023 Jul 21, 2023

Tested on:
Pro DC 2023.003.20244 (x86)
2020 Std. 2020.005.30467
assuming Reader has the problem, too

 

Clicking on a link Annotation with an internal Named Destination target fails to navivate if the string encodings of the "Dest" in the "Annots" array element does not match the encoding of the string "key" in the "Names" array in the document catalog. Chrome and Edge do not have this problem. Acrobat behavior does not conform to the PDF Reference.  The strings are semantically equivilent.  The Names array keys are PDF 1.2 strings, not PDF 1.1 names.

 

See attached screen shots for details of Names and Annots array.

Steps to reproduce:
- Open The Attached .pdf
- Page 1 contains 3 links, click on each
  - The link under "Unicode Text" works correctly.
  - The links under "To Page 2" and "To Page 3" do not.

This has a large impact on some of our customers, they have thousands of documents with this kind of link.

 

also reported as https://acrobat.uservoice.com/forums/590923-acrobat-for-windows-and-mac/suggestions/46966573-bug-nam...

TOPICS
PDF , Standards and accessibility
332
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
no replies

Have something to add?

Join the conversation