-\subsection{Scientific Computation Packages}
-
-The document and the code that produces it are one and the same.
-
-\begin{itemize}
- \item Numerical computation packages such as Mathematica and Maple use arbitrary precision floats
- \begin{itemize}
- \item Mathematica is not open source which is an issue when publishing scientific research (because people who do not fork out money for Mathematica cannot verify results)
- \item What about Maple? \cite{HFP} and \cite{fousse2007mpfr} both mention it being buggy.
- \item Octave and Matlab use fixed precision doubles
- \end{itemize}
- \item IPython is pretty cool guys
-\end{itemize}
-
-\section{Precision in Modern Document Formats}
-
-We briefly summarise the requirements of the standards discussed so far in regards to the precision of mathematical operations:
-\begin{itemize}
- \item {\bf PostScript} predates the IEEE-754 standard and originally specified a floating point representation with ? bits of exponent and ? bits of mantissa. Version ? of the PostScript standard changed to specify IEEE-754 binary32 ``single precision'' floats.
- \item {\bf PDF} has also specified IEEE-754 binary32 since version ?. Importantly, the standard states that this is a \emph{maximum} precision; documents created with higher precision would not be viewable in Adobe Reader.
- \item {\bf SVG} specifies a minimum of IEEE-754 binary32 but recommends more bits be used internally
- \item {\bf Javascript} uses binary32 floats for all operations, and does not distinguish between integers and floats.
- \item {\bf Python} uses binary64 floats
- \item {\bf Matlab} uses binary64 floats
- \item {\bf Mathematica} uses some kind of terrifying symbolic / arbitrary float combination
- \item {\bf Maple} is similar but by many accounts horribly broken
-
-\end{itemize}
+Hayes describes PDF as ``... essentially 'flattened' PostScript; it’s what’s left when you remove all the procedures and loops in a program, replacing them with sequences of simple drawing commands.''\cite{hayes2012pixels}. Consultation of the PDF 1.7 standard shows that this statement does not a give a complete picture --- despite being based on the Adobe PostScript model of a document as a series of ``pages'' to be printed by executing sequential instructions, from version 1.5 the PDF standard began to borrow some ideas from the Document Object Model. For example, interactive elements such as forms may be included as XHTML objects and styled using CSS. ``Actions'' are objects used to modify the data structure dynamically. In particular, it is possible to include Javascript Actions. Adobe defines the API for Javascript actions seperately to the PDF standard\cite{js_3d_pdf}. There is some evidence in the literature of attempts to exploit these features, with mixed success\cite{barnes2013embedding, hayes2012pixels}.
+
+%\subsection{Scientific Computation Packages}
+
+
+\section{Precision required by Document Formats}