Support named destinations in remote link annotations.

Previously there was a bug when parsing GoToR link annotations that had
a named destination. mupdf incorrectly attempted to resolve the
destination in the current document. Now the destination name is
present in the link objects returned to the application so it can
resolve any names for GoToR links in the remote document instead.

1 files changed, 9 insertions, 1 deletions

diff --git a/include/mupdf/fitz/link.h b/include/mupdf/fitz/link.h
index 65a77fd2..7a400851 100644
--- a/include/mupdf/fitz/link.h
+++ b/include/mupdf/fitz/link.h
@@ -47,7 +47,14 @@ enum {
 	For FZ_LINK_GOTO or FZ_LINK_GOTOR:
 
 		gotor.page: The target page number to move to (0 being the
-		first page in the document).
+		first page in the document). In the FZ_LINK_GOTOR case, the
+		page number either refers to to the file specified by
+		gotor.file_spec, or the page number is -1 suggesting that
+		the destination is given by gotor.dest.
+
+		gotor.dest: If set, the target destination name to be
+		resolved in the file specified by gotor.file_spec. Always
+		NULL in the FZ_LINK_GOTO case.
 
 		gotor.flags: A bitfield consisting of fz_link_flag_*
 		describing the validity and meaning of the different parts
@@ -97,6 +104,7 @@ struct fz_link_dest_s
 		struct
 		{
 			int page;
+			char *dest;
 			int flags;
 			fz_point lt;
 			fz_point rb;