Hello
According to my testing, the bookmark feature broke with 25.2 and still does not work with the currently newest version 25.9 of Aspose.PDF.Drawing for .NET.
I use the following test-code to illustrate the problem:
[Fact]
public void Test()
{
var output = new Aspose.Pdf.Document();
var input = new Aspose.Pdf.Document("<path to input file>");
output.Pages.Add(input.Pages);
output.Pages.Add(input.Pages);
output.Outlines.Add(new OutlineItemCollection(output.Outlines) { Title = "Page 1", Action = new GoToAction(output.Pages[1]) });
output.Outlines.Add(new OutlineItemCollection(output.Outlines) { Title = "Page 2", Action = new GoToAction(output.Pages[2]) });
output.Save("<path to output file>");
}
The resulting PDF contains somewhat incorrectly encoded strings which look like this:
image.png (2.6 KB)
When downgrading to 25.1 it works as expected.
1 Like
@gregorbosshard
It appears you are encountering issues with bookmarks in your PDF documents after upgrading to version 25.2 of Aspose.PDF.Drawing for .NET. Your test code seems correct, but the resulting PDF contains incorrectly encoded strings, which is unexpected behavior.
Since downgrading to version 25.1 resolves the issue, it suggests that there may be a bug introduced in version 25.2 or later. I recommend checking the release notes or issue tracker for any known bugs related to bookmarks in the versions you are using.
In the meantime, consider the following workarounds:
- Use version 25.1 if feasible until the issue is addressed in a future release.
- If you must use the newer version, try simplifying the bookmark structure or testing with different document inputs to determine if the issue persists.
For further assistance, you can post your issue on the Aspose forums, where the community and support team can provide more targeted help.
If you have any additional questions, feel free to reach out!
It looks like the same issue was described a few months prior in Bookmark display issue in Adobe Acrobat Browser Extension after Aspose.PDF 25.2 Update. Sorry for double posting.
@gregorbosshard
You are right. A similar issue as PDFNET-60208 is already registered in our issue management system for investigation. We have linked the ticket ID with this forum thread as well so that you will receive a notification as soon as the ticket is resolved. We highly appreciate your patience in this regard. We are sorry for the inconvenience.