X-Git-Url: https://git.ucc.asn.au/?p=ipdf%2Fsam.git;a=blobdiff_plain;f=chapters%2FBackground%2FStandards%2FPrecision.tex;h=f533b98207ca978820032e0cfc85b7ad21e5ac1a;hp=3acacbde79504b41df880e527067a4dbafe33f7e;hb=HEAD;hpb=7fe12ce195f039925222ad98b38018ad31d1b1f2

diff --git a/chapters/Background/Standards/Precision.tex b/chapters/Background/Standards/Precision.tex
index 3acacbd..f533b98 100644
--- a/chapters/Background/Standards/Precision.tex
+++ b/chapters/Background/Standards/Precision.tex
@@ -1,4 +1,4 @@
-In this section we will overview the statements made about the precision with which an object can be stored by various vector graphics and document standards.
+
 
 
 \subsection{PostScript}
@@ -19,7 +19,7 @@ coordinate system transformations to provide the best possible precision and to
 %\begin{comment}
 \subsection{Javascript}
 We include Javascript here due to its relation with the SVG, HTML5 and PDF standards.
-According to the EMCA-262 standard, ``The Number type has exactly 18437736874454810627 (that is, $2^64-^53+3$) values, 
+According to the EMCA-262 standard, ``The Number type has exactly 18437736874454810627 (that is, $2^{64}-2^{53}+3$) values, 
 representing the double-precision 64-bit format IEEE 754 values as specified in the IEEE Standard for Binary Floating-Point Arithmetic''\cite{ecma-262}. 
 The Number type does differ slightly from IEEE-754 in that there is only a single valid representation of ``Not a Number'' (NaN). The EMCA-262 does not define an ``integer'' representation.
 %\end{comment}