diff options
author | Manuel Pégourié-Gonnard <mpg@elzevir.fr> | 2008-09-04 13:56:48 +0000 |
---|---|---|
committer | Manuel Pégourié-Gonnard <mpg@elzevir.fr> | 2008-09-04 13:56:48 +0000 |
commit | 4e235bf671868db530dfcff3f83c58f3a8389307 (patch) | |
tree | 8bc8f73eeaa5dfb8f8c56a242c8027857f1ea634 /Master/texmf-dist/doc/latex/animate/animate.tex | |
parent | 9f210e2dc170483a035d6c93e4130302c8f05d6f (diff) |
animate update v2008/08/28
git-svn-id: svn://tug.org/texlive/trunk@10428 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/latex/animate/animate.tex')
-rwxr-xr-x | Master/texmf-dist/doc/latex/animate/animate.tex | 59 |
1 files changed, 7 insertions, 52 deletions
diff --git a/Master/texmf-dist/doc/latex/animate/animate.tex b/Master/texmf-dist/doc/latex/animate/animate.tex index d36c2095c6f..43c5831a321 100755 --- a/Master/texmf-dist/doc/latex/animate/animate.tex +++ b/Master/texmf-dist/doc/latex/animate/animate.tex @@ -169,14 +169,14 @@ By default, the animation is built frame by frame in the order of inclusion of t \myparagraph*{Sets of graphics files} All files of the sequence should exist and be consecutively numbered. (Exception to this rule is allowed in connection with the `\verb+every+' option, see below.) {\tt <file base\-name>} is the leftmost part of the file name that is common to all members of the sequence. \verb+<first>+ is the number of the first and \verb+<last>+ the number of the last file in the set. File names may be simply numbered, such as $0\dots99$. If there are leading zeros, make sure that all file numbers have the same number of digits, such as $0000\dots0099$. -There is no file name extension to be specified as a parameter. The possible file formats depend on whether \LaTeX{} or pdf\LaTeX{} is used. In the case of \LaTeX{}, files with the extension `eps' are searched for at first, followed by `mps' (\MP-generated Postscript) and `ps'. With pdf\LaTeX{} the searching order is: (1)~`pdf', (2)~`mps', (3)~`png', (4)~`jpg', (5)~`jpeg', (6)~`jbig2', (7)~`jb2', (8)~`jp2'\footnotemark[1], (9)~`j2k'\footnotemark[1], (10)~`jpx'\footnotemark[1]\footnotetext[1]{JPEG2000 is not yet supported by pdf\TeX.}, with output driver `\verb+dvipdfmx+': (1)~`pdf', (2)~`mps', (3)~`eps', (4)~`ps', (5)~`png', (6)~`jpg' and (7)~`jpeg' and with \XeLaTeX: (1)~`pdf', (2)~`mps', (3)~`eps', (4)~`ps', (5)~`png', (6)~`jpg', (7)~`jpeg', (8)~`tif', (9)~`tga', (10)~`sgi', (11)~`psd', (12)~`pict', (13)~`mac', (14)~`gif' and (15)~`bmp'. That is, files capable to store vector graphics are found first. Make sure that all file names have \emph{lower case} extensions. +There is no file name extension to be specified as a parameter. The possible file formats depend on the output driver being used. In the case of \LaTeX{}+\verb+dvips+, files with the extension `eps' are searched for at first, followed by `mps' (\MP-generated Postscript) and `ps'. With pdf\LaTeX{} the searching order is: (1)~`pdf', (2)~`mps', (3)~`png', (4)~`jpg', (5)~`jpeg', (6)~`jbig2', (7)~`jb2', (8)~`jp2'\footnotemark[1], (9)~`j2k'\footnotemark[1], (10)~`jpx'\footnotemark[1]\footnotetext[1]{JPEG2000 is not yet supported by pdf\TeX.} and with \XeLaTeX{} or \LaTeX{}+\verb+dvipdfmx+: (1)~`pdf', (2)~`mps', (3)~`eps', (4)~`ps', (5)~`png', (6)~`jpg', (7)~`jpeg', (8)~`bmp'. That is, files capable to store vector graphics are found first. Make sure that all file names have \emph{lower case} extensions. For example, given the sequence `frame\_5.png' through `frame\_50.png' from a possibly larger set that shall be used to build an animation running at 12 frames per second. Then, the correct inclusion command reads \begin{verbatim} \animategraphics{12}{frame_}{5}{50} \end{verbatim} -\myparagraph*{Multipage PDF/JBIG2 inclusion (pdf\LaTeX{} only)} +\myparagraph*{Multipage PDF {\rm(pdf\LaTeX, \XeLaTeX)} and JBIG2 {\rm(pdf\LaTeX)} inclusion} If the file `\verb+<file basename>+.(pdf|jbig2|jb2)' exists (again, there is no file name extension to be specified), it is taken as a multipage document where each page represents one frame of the animation. In this case, the last two arguments, \verb+<first>+ \& \verb+<last>+, are interpreted differently from above; they specify a zero-based range of pages to be included in the animation. Either or both of them may be left empty, `\verb+{}+', in which case they default to $0$ and $n-1$, where $n$ is the total number of available pages. Arguments that fall outside this range are automatically corrected to the maximum allowed number, i.\,e. $n-1$. For example, the line @@ -225,7 +225,7 @@ width=<width> height=<height> depth=<depth> \end{verbatim} -Resize the animation widget. Any valid \TeX{} dimension is accepted as a parameter. Option `\verb+depth+' specifies how far the animation widget should extend below the bottom line of the running text. If only one or two of these options are given, the remaining, unspecified dimensions are scaled to keep the aspect ratio. +Resize the animation widget. Option `\verb+depth+' specifies how far the animation widget should extend below the bottom line of the running text. If only one or two of these options are given, the remaining, unspecified dimensions are scaled to keep the aspect ratio. Any valid \TeX{} dimension is accepted as a parameter. Moreover, the length commands \verb+\width+, \verb+\height+, \verb+\depth+ and \verb+\totalheight+ may be used to refer to the original dimensions of the animation widget which correspond to the size of the first frame of the animated sequence. \begin{verbatim} scale=<factor> \end{verbatim} @@ -283,7 +283,7 @@ timeline=<timeline file> \end{verbatim} \verb+<timeline file>+ is a plain text file whose contents determines the order of appearance of the embedded material during the animation. It allows to freely rearrange, repeat and overlay the material at any point of the animation. This may greatly reduce the file size of the resulting PDF, as objects that do not change between several or all frames, such as coordinate axes or labels, can be embedded once and re-used in other frames of the animation. -If a timeline is associated with the animation, the graphics files or inline graphics embedded by \verb+\animategraphics+ and `\verb+animateinline+' no longer represent the actual frames of the animation. Rather, they are a collection of \emph{transparencies} that can be played with at will. In order to identify the transparencies within the timeline file, they are numbered in the order of their inclusion, starting at zero. +If a timeline is associated with the animation, the graphics files or inline graphics embedded by \verb+\animategraphics+ and `\verb+animateinline+' no longer represent the actual frames of the animation. Rather, they are a collection of \emph{transparencies} that can be played with at will. However, it is now up to the author's responsability to construct a timeline that makes use of all those transparencies and to put them into a sensible order. In order to identify the transparencies within the timeline file, they are numbered in the order of their inclusion, starting at zero. Each line of the timeline file that is not blank and which does not begin with a comment (`\verb+%+') specifies \emph{one} frame of the animation. There may be more transparencies than animation frames and vice-versa. A frame specification consists of three, colon-(\verb+:+)-separated fields: \begin{verbatim} @@ -322,7 +322,7 @@ and \normalsize In the first example, transparency No. 0 appears in the foreground throughout the animation; it will never be obscured by other transparencies' content. In the second example it is put to the background, because it is the first transparency specification in the file, and stays there for the rest of the animation. -When designing the timeline, care should be taken not to include a transparency more than once into the \emph{same} animation frame. Besides the useless redundancy, this may slow down the animation speed in the Reader, because the graphical objects of a multiply included transparency have to be rendered unnecessarily often at the same time. `animate' is smart enough to detect multiple inclusion and issues a warning message along with the transparency ID and the frame number if it occurs. Also, `animate' finds and lists transparencies that have never been used in an animation timeline. This may help to avoid dead code in the final PDF. Here is an example of a poorly designed timeline: +When designing the timeline, care should be taken not to include a transparency more than once into the \emph{same} animation frame. Besides the useless redundancy, this may slow down the animation speed in the Reader, because the graphical objects of a multiply included transparency have to be rendered unnecessarily often at the same time. `animate' is smart enough to detect multiple inclusion and issues a warning message along with the transparency ID and the frame number if it occurs. Here is an example of a poorly designed timeline: \small \begin{verbatim} ::0 @@ -335,6 +335,7 @@ When designing the timeline, care should be taken not to include a transparency ... \end{verbatim} \normalsize +Also, `animate' finds and lists transparencies that have never been used in an animation timeline. This may help to avoid dead code in the final PDF. \myparagraph*{Grouping objects into layers using `{\tt;}'} The stack-like concept of animations, where transparencies are always put on top such that they overprint the content of previously deposited transparencies, can be inconvenient in certain situations. For example, it might be desirable to allow for changing the background image in the middle of an animation without affecting objects that are located in the foreground. For this purpose, transparency specifications can be grouped into \emph{layers} using the semicolon (\verb+;+) as a separator instead of the comma. This is best illustrated by an example: @@ -571,57 +572,12 @@ Fig.~\ref{fig:torus} is an inline graphics example adapted from \cite{gilg05}. \quad{\tt epsffit -c <llx> <lly> <urx> <ury> infile.eps outfile.eps} -{\tt <llx> <lly> <urx> <ury>} are the bounding box coordinates of the target document. They can be determined using Ghostscript. For a document called `document.ps' the command line is +{\tt <llx> <lly> <urx> <ury>} are the bounding box coordinates of the target document. They can be determined using Ghostscript. For a document named `document.ps' the command line is \quad{\tt gs -dNOPAUSE -q -dBATCH -sDEVICE=bbox document.ps} Note that the name of the Ghostscript executable may vary between operating systems (e.\,g. `{\tt gswin32c.exe}' on Win/DOS). -% \item The command {\tt\string\multido} and its relatives from package `multido' as well as {\tt\string\foreach} from the `pgf/TikZ' package do not work \emph{if their loop body} contains {\tt\string\newframe}. Instead, use {\tt\string\whiledo} from package `if\/then' if you wish to construct loops around parameterized {\tt pspicture}\emph{s} or {\tt tikzpicture}\emph{s}. (There is no need to load `if\/then' explicitly; it has already been loaded by `animate'.) A counter must be declared to keep track of the number of iterations. Further variables that take fixed point decimals to be used within the loop body can be defined and incremented by means of the commands \verb+\FPset+ and \verb+\FPeval+ from package `fp'. Note that {\tt\string\multido} and {\tt\string\foreach} \emph{can} safely be used \emph{within} the code of the frames. For example: -%\small -%\begin{verbatim} -% -%%parameterized `tikzpicture' -%\newcommand{\PicWithParam}[1]{% -% \begin{tikzpicture}% -% ... -% ... code making use of parameter #1, -% ... \multido & \foreach _can_ be used here! -% ... -% \end{tikzpicture}% -%} -% -%\newcounter{iter} % declare loop counter -% -%\FPset{nInit}{1.0}% initial value of variable `n' -%\FPset{nIncr}{0.5}% increment of `n' -% -%\begin{animateinline}{12} -% %initialize loop counter and `n' -% \setcounter{iter}{0}% -% \FPset{n}{nInit}% -% % -% %create first frame using `\n' (Mind the backslash!) -% \PicWithParam{\n}% -% % -% \whiledo{\theiter<50}{% another 50 frames -% %start new frame -% \newframe% -% % -% %increment loop counter by 1 -% \stepcounter{iter}% -% % -% %calculate new value of `n' -% \FPeval{n}{nInit+nIncr*\theiter}% -% % -% %create frame using `\n' (Mind the backslash!) -% \PicWithParam{\n}% -% % -% } -%\end{animateinline} -%\end{verbatim} -%\normalsize -% \item Animations with complex graphics and/or many frames may cause \LaTeX{} to fail with a `\verb+TeX capacity exceeded+' error. The following steps should fix most of the memory related problems. MiK\TeX: @@ -659,7 +615,6 @@ I would like to thank Fran\c{c}ois Lafont who discovered quite a few bugs and ma \bibitem{chupin} Chupin, M.: \href{http://melusine.eu.org/syracuse/metapost/animations/chupin/?idsec=scara}{\tt http://melusine.eu.org/syracuse/metapost/animations/} \href{http://melusine.eu.org/syracuse/metapost/animations/chupin/?idsec=scara}{\tt chupin/?idsec=scara} \bibitem{gilg05} Gilg, J.: PDF-Animationen. In: \emph{Die \TeX nische Kom\"odie}, Issue 4, 2005, pp.~30--37 \bibitem{hol} Hole\v{c}ek, J.: \emph{Animations in a pdf\TeX-generated PDF}. URL: \href{http://www.fi.muni.cz/~xholecek/tex/pdfanim.xhtml}{\tt http://www.} \href{http://www.fi.muni.cz/~xholecek/tex/pdfanim.xhtml}{\tt fi.muni.cz/\textasciitilde xholecek/tex/pdfanim.xhtml} - \bibitem{hol04} Hole\v{c}ek, J. ; Sojka, P.: Animations in pdf\TeX-generated PDF. In: \emph{Lecture Notes in Computer Science}, Vol. 3130, 2004, pp.~179--191 \bibitem{movie15} \emph{The Movie15 Package}. URL: \href{http://www.ctan.org/tex-archive/macros/latex/contrib/movie15/}{\tt http://www.ctan.org/tex-archive/macros/} \href{http://www.ctan.org/tex-archive/macros/latex/contrib/movie15/}{\tt latex/contrib/movie15} \end{thebibliography} |