fixed the ProR logo in print

git-svn-id: svn://svn.code.sf.net/p/rodin-b-sharp/svn/trunk/Handbook@15970 1434b563-b632-4741-aa49-43a3a8374d2e

org.rodinp.handbook.feature/latex/makros.tex

@@ -180,6 +180,12 @@
 }
 \fi
 
+\ifinprint
+\newenvironment{plugin-pror}{\begin{rodin-plugin}{bw/pror.png}{ProR Requirements}}{\end{rodin-plugin}}
+\else
+\newenvironment{plugin-pror}{\begin{rodin-plugin}{pror.png}{ProR Requirements}}{\end{rodin-plugin}}
+\fi
+
 % Marginpars are  cropped - this formats them nicely.
 \let\oldmarginpar\marginpar
 \renewcommand\marginpar[1]{\-\oldmarginpar[\raggedleft\scriptsize{#1}]

org.rodinp.handbook.feature/latex/tutorial-03.tex

@@ -33,7 +33,7 @@ We cover a few examples in this chapter that should develop your ability to answ
 
 Jean-Raymond Abrial has something to say about this in his book\footnote{\url{http://www.amazon.com/Modeling-Event-B-System-Software-Engineering/dp/0521895561}}. Some of the chapters are available in the Rodin Wiki.
 
-\begin{rodin-plugin}{pror.png}{ProR Requirements}
+\begin{plugin-pror}
 \index{requirements}
 \index{ProR Requirements Tool}
 \index{traceabililty}
@@ -48,7 +48,7 @@ Further, the traces are tracked, and if the source or the target of a trace chan
 Being able to set traces is not enough, if there is not a theory behind it to make it useful.  One such theory is based on the WRSPM reference model.  How this works in practice can be seen in \href{http://www.stups.uni-duesseldorf.de/w/Special:Publication/RMF_Mark_Book_Jastram_2013}{this paper}.
 
 Last, ProR is based on the ReqIF standard, which is supported by major industry tools for requirements management (like Rational DOORS or PTC integrity).  This eases the integration of Event-B into existing development processes.
-\end{rodin-plugin}
+\end{plugin-pror}
 
 \subsection{Project Setup}
 \label{tut_project_setup}