From 775612e6c92af28f9c176d1cfe76107215f113f6 Mon Sep 17 00:00:00 2001 From: Tim van der Meij Date: Fri, 8 Mar 2019 00:06:46 +0100 Subject: [PATCH] Update links --- Debugging-PDF.js.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Debugging-PDF.js.md b/Debugging-PDF.js.md index f86d866..8915951 100644 --- a/Debugging-PDF.js.md +++ b/Debugging-PDF.js.md @@ -34,7 +34,7 @@ The font inspector allows you to view what fonts are used within page. It also a The stepper tool makes it easy for you to step through the drawing commands one at a time and hopefully find where a possible issue is coming from. It is also useful for learning how a PDF document is structured and the order of its operations. To walk through the drawing commands you must add a break point, refresh the page and then use the keys `s` to step one command at a time or `c` to continue until the next breakpoint (line that is checked). ## PDF Object Browser -Inspect the internal object structure and view raw values of a PDF document using http://brendandahl.github.io/pdf.js.utils/browser. +Inspect the internal object structure and view raw values of a PDF document using https://brendandahl.github.io/pdf.js.utils/browser. ## Debugging Font Issues To get a problematic font out of a PDF document, download it first using the font inspector mentioned above. @@ -69,5 +69,5 @@ The Adobe Font Development Kit includes the above `ttx` program and several othe `tx` can also be used to dump information from the font, see `tx -dump -h` for more information. **Other Font Tools** -* [FontForge](http://fontforge.sourceforge.net/) -* [Microsoft Font Validator](http://www.microsoft.com/typography/FontValidator.mspx) \ No newline at end of file +* [FontForge](https://fontforge.github.io) +* [Microsoft Font Validator](https://github.com/Microsoft/Font-Validator) \ No newline at end of file