fonts

paper/mappings.tex

@@ -194,6 +194,7 @@ \subsection{Exception Handling}
 
 It may be translated to \eo{}:
 
+\begin{twocols}
 \begin{ffcode}
 try
   []
@@ -207,6 +208,7 @@ \subsection{Exception Handling}
     stdout > @
       "This happens anyway"
 \end{ffcode}
+\end{twocols}
 
 Now, throwing an exception is returning an object that can't be
 dataized and handling the exception is checking for whether the

paper/semantics.tex

@@ -37,7 +37,7 @@ \subsection{Object Graph}
 which is also represented by the expression in the Eq.~\ref{eq:book}.
 The Fig.~\ref{fig:book2} represents it as a graph.
 
-\begin{figure}
+\begin{figure}[t!]
 \begin{ingraph}
   \node[object] (v0) {$\Phi$};
   \node[object] (v2) [below right=0.5cm and 1.8cm of v0] {$v_2$};
@@ -190,6 +190,7 @@ \subsection{GMI}
 The object graph at the Fig.~\ref{fig:book2} may be generated with the
 following ordered sequence of GMIs:
 
+\begin{twocols}
 \begin{ffcode}
 ADD(|$\Phi$|)
 ADD(|$v_1$|);
@@ -205,6 +206,7 @@ \subsection{GMI}
 ADD(|$d_4$|);
 BIND(|$v_4$|, |$d_4$|, |$\delta$|);
 \end{ffcode}
+\end{twocols}
 
 \subsection{Transformation Rules}
 

paper/syntax.tex

@@ -1,4 +1,4 @@
-\newcommand\sntx[1]{{\bfseries\sffamily #1}}
+\newcommand\sntx[1]{{\sffamily #1}}
 
 The Fig.~\ref{fig:bnf} demonstrates the entire syntax of \eo{} language in BNF.
 Similar to Python~\citep{lutz2013learning}, indentation in \eo{} is part of the syntax: