GNOME Bugzilla – Bug 649591
gnumeric.pdf issues
Last modified: 2011-05-07 07:57:22 UTC
I am observing a few issues with the gnumeric.pdf documentation file: 1) due to the fix of bug #649484 we now have \subsubsection*{Synopsis} \begin{verbatim}NPV(rate,value1,value2,\ldots{})\end{verbatim} So the ellipsis is correctly translated into \ldots{} but because of the verbatim environment \ldots is not translated into the correct glyph. (This could be fixed by replacing the ellipsis by 3 periods but in that case the spacing would be wrong.) 2) The formatting of argument names yields: \texttt{\emph{\small{d\-a\-t\-a\-b\-a\-s\-e}}} is a range... This makes the argument names unnecessarily small. (And do we really want to break argume nt names at any arbitrary point?)
Problem #1 also occurs in other situations: \begin{verbatim}RANDLEVY(c,\ensuremath{\alpha},\ensuremath{\beta})\end{verbatim} definitely does not create the correct appearance.
Most of this is fixed but in the description of RANDLEVY we still have "Lvy" show up since the tex file contains L\351vy with \351 being a single character.
Following the manual and setting -P latex.encoding=utf8 rather than -P latex.encoding=utf-8 handles the accent-acute-e correctly but fails with respect of the alpha, beta, etc: ------------------------------------------------------------------------------- l.38608 \texttt{\emph{\small{σ}}} : scale parameter of the Rayleigh distribu... Your command was ignored. Type I <command> <return> to replace it with another command, or <return> to continue without it. ! LaTeX Error: Command \textsigma unavailable in encoding T1. -------------------------------------------------------------------------------
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.