> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/pdf-converter-for-notes/troubleshooting/general-issues/document-links-not-working.md). # Document links not working If the document links in the PDF files are not working properly after performing an export from Notes, first check if a required javascript file is found in the Javascripts folder (for Adobe Reader DC). The javascript file is called swpdfc.js, while the Javascripts folder is typically located in C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\Javascripts If the file is not found, it will need to be copied to the Javascripts folder manually. Contact SWING support team in order to get a copy of the file. If the javascript file is found in the Javascripts folder, you will also need to check Adobe Reader's security settings. In Adobe Reader DC, Go to Edit > Preferences and on the Security (Enhanced) tab set the settings as shown in the below screenshot: ![](https://3331713008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MlCAurE6RSGoCmtmAET%2Fuploads%2FUwWv1EzvnQnjkJRpSkyi%2FSecurity%20enhanced%20settings.png?alt=media\&token=d121a019-7009-4455-8ca7-5c6a30bf7107) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.swingsoftware.com/pdf-converter-for-notes/troubleshooting/general-issues/document-links-not-working.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.