The arguments in texidvi() are rarely used, but those in Sweave() are often very important. In #25 I mentioned changes in the official Sweave, and now I noticed the file encoding might cause problems.
Sweave() was changed so that it will no longer respect options('encoding'); instead, it takes the encoding information from either \usepackage[foo]{inputenc} or Sweave(..., encoding = 'foo'). Since pgfSweave() passes ... to texi2dvi(), it seems to be impossible to pass the encoding directly via command line, so the only way is to use \usepackage[foo]{inputenc}.
I'm not completely sure if this can bring a real problem, but I believe it is more useful to pass ... to Sweave() and more consistent with the usage of Sweave().
The arguments in
texidvi()are rarely used, but those inSweave()are often very important. In #25 I mentioned changes in the official Sweave, and now I noticed the file encoding might cause problems.Sweave()was changed so that it will no longer respectoptions('encoding'); instead, it takes the encoding information from either\usepackage[foo]{inputenc}orSweave(..., encoding = 'foo'). SincepgfSweave()passes...totexi2dvi(), it seems to be impossible to pass the encoding directly via command line, so the only way is to use\usepackage[foo]{inputenc}.I'm not completely sure if this can bring a real problem, but I believe it is more useful to pass
...toSweave()and more consistent with the usage ofSweave().