A couple more comments on the \dots problem:
1. Allowing {} after \dots is unsatisfactory, because the current
parser will render the braces, i.e. 1\dots{}10 is rendered as 1..{}10.
I'd like to have enough back-compatibility that it is possible to
rewrite a man page to work in either system.
Just one additional comment in line below:
On 11/13/2008 1:44 PM, Duncan Murdoch wrote:
On 11/13/2008 11:51 AM, Simon Urbanek wrote:
Duncan,
I had a quick look at the parsers differences and I'm worried about
points 1. and 2. (on p.6) -- does that imply that \R{} is illegal and
so is any \
On 11/13/2008 11:51 AM, Simon Urbanek wrote:
Duncan,
I had a quick look at the parsers differences and I'm worried about
points 1. and 2. (on p.6) -- does that imply that \R{} is illegal and
so is any \foo{} for any macro \foo that doesn't take any arguments?
IMHO that would be fatal (if I
I've just committed the parse_Rd() function to R-devel. This is a
parser for Rd files, described in
http://developer.r-project.org/parseRd.pdf
It is not identical to the current parser, and about a dozen of the base
man pages currently signal syntax errors. It also detected errors in 10
fil