From: ng0 Date: Wed, 6 Sep 2017 08:14:19 +0000 (+0000) Subject: doc: gnunet-c-tutorial: comment the included images/pdfs for now. X-Git-Tag: gnunet-0.11.0rc0~120 X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=0e0e6e3594655a92532f32c46bf2abf5a5d4c0c2;p=oweals%2Fgnunet.git doc: gnunet-c-tutorial: comment the included images/pdfs for now. --- diff --git a/doc/gnunet-c-tutorial.texi b/doc/gnunet-c-tutorial.texi index 880364444..3b3e90e4f 100644 --- a/doc/gnunet-c-tutorial.texi +++ b/doc/gnunet-c-tutorial.texi @@ -218,25 +218,25 @@ higher layers of GNUnet on top of the lower ones. Each layer expands or extends the functionality of the service below (for instance, to build a mesh on top of a DHT). See figure ~\ref{fig:interaction} for an illustration of this approach. -\begin{figure}[!h] - \begin{center} -% \begin{subfigure} - \begin{subfigure}[b]{0.3\textwidth} - \centering - \includegraphics[width=\textwidth]{figs/Service.pdf} - \caption{Service with API and network protocol} - \label{fig:service} - \end{subfigure} - ~~~~~~~~~~ - \begin{subfigure}[b]{0.3\textwidth} - \centering - \includegraphics[width=\textwidth]{figs/System.pdf} - \caption{Service interaction} - \label{fig:interaction} - \end{subfigure} - \end{center} - \caption{GNUnet's layered system architecture} -\end{figure} +@c \begin{figure}[!h] +@c \begin{center} +@c % \begin{subfigure} +@c \begin{subfigure}[b]{0.3\textwidth} +@c \centering +@c \includegraphics[width=\textwidth]{figs/Service.pdf} +@c \caption{Service with API and network protocol} +@c \label{fig:service} +@c \end{subfigure} +@c ~~~~~~~~~~ +@c \begin{subfigure}[b]{0.3\textwidth} +@c \centering +@c \includegraphics[width=\textwidth]{figs/System.pdf} +@c \caption{Service interaction} +@c \label{fig:interaction} +@c \end{subfigure} +@c \end{center} +@c \caption{GNUnet's layered system architecture} +@c \end{figure} The main service implementation runs as a standalone process in the operating system and the client code runs as part of the client program, so crashes of a