Skip to main content

The power of HTML 5 and Javascript: Rendering PDF’s in your browser

Today I was once again amazed about the power that HTML5 and Javascript can offer when I discovered PDF.js. This Javascript library is written by a couple of clever guys over at Mozilla and allows you to display PDFs inside your browser using Javascript and HTML5. The code is available for download on Github.
Benefits
The traditional approach to rendering PDFs in a browser is to use a native-code plugin, either Adobe’s own PDF Reader or other commercial renderers, or some open source alternative. From a security perspective, this enlarges the trusted code base and increases the risk of code based injection attacks. An HTML5-based implementation is completely immune to this class of problems.
If you want to see a demo of pdf.js, click on this link. There are still glitches and rendering artifacts but it already shows the potential of this library.
A quick sample
Download the latest code required from Github to start developing. Create a web page and embed the following Javascript references:
<script type="text/javascript" src="scripts/pdf.js"></script>  
<script type="text/javascript" src="scripts/metrics.js"></script>
<script type="text/javascript" src="scripts/fonts.js"></script>
<script type="text/javascript" src="scripts/glyphlist.js"></script>


Add the new <canvas> HTML5 control to the body of your page


<canvas id="pdf-canvas" style="border:1px solid black;"/>


Now you can start rendering your PDF by writing some Javascript code:
<script type="text/javascript">
'use strict';      
getPdf('myPDFFile.pdf', function getPdf(data) {
 // Instantiate PDFDoc with PDF data          
 var pdf = new PDFDoc(data);          
 var page = pdf.getPage(1);          
 var scale = 1.5;

 // Prepare canvas using PDF page dimensions          
 var canvas = document.getElementById('pdf-canvas');
 var context = canvas.getContext('2d');
 canvas.height = page.height * scale;
 canvas.width = page.width * scale;          
 
 // Render PDF page into canvas context
 page.startRendering(context);      
});  
</script>

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...