| LinkPages Method | ||
|
||
|
Convert external links to internal links wherever possible.
|
Syntax
|
[C#]
|
Params
|
Notes
|
This method scans the entire document converting external links to internal links wherever possible. As an alternative you can restrict the scope of the conversion by using the LinkDestinations method. By default, links in rendered HTML are preserved as is. This means that links in a web page link to external URLs. When you click on them, a browser window will be launched and the original target of the link displayed. In some situations, you may wish to resolve links within the document so that they take you between pages in the PDF rather than launching an external browser window. For example, you might add a number of web pages which contain links to each other. Rather than linking to the pages on the original web site, you might like to resolve the links so that they point at the pages as they now appear in the PDF. Similarly, if you use named destinations (HTML fragments) with links within the document, you will may wish to use this method to convert them from external links to internal ones. If you do this you will probably want to set the AddIDs and AddNames properties to true to ensure that this type of fragment destination is tracked.
|
Example
|
This example shows how to import an HTML page which uses named destinations. We first create a Doc object and inset the edges a little so that the HTML will appear in the middle of the page. We assign the appropriate HTML options so that links will be rendered live.
using var doc = new Doc();
doc.Rect.Inset(18, 18);
doc.HtmlOptions.AddLinks = true;
We add the pages to the document.
int id = doc.AddImageUrl("http://www.websupergoo.com/support.htm");
while (true) {
if (!doc.Chainable(id))
break;
doc.Page = doc.AddPage();
id = doc.AddImageToChain(id);
}
The URL we've referenced makes extensive use of named destinations. We want these named destination links to take us between pages on the PDF rather than taking us to the original URL. After adding the pages, we can flatten them. We can't do this until after the pages have been added because flattening will invalidate our previous ID and break the chain.
doc.HtmlOptions.LinkPages();
for (int i = 1; i <= doc.PageCount; i++) {
doc.PageNumber = i;
doc.Flatten();
}
Finally, we save.
doc.Save("linkpages.pdf");
We get the following output. The links work – where possible – within the PDF.
Also see example code in: XHtmlOptions UseScript Property.
|
