Hi all, Don't know if this is a known issue, but I couldn't find anything so I report anyway. When checking eg ?qr in both RStudio and the naked R IDE, the help page is rendered incorrectly. More specifically, any use of \bold{...} is printed as is, rather than interpreted as bold. Same happens on ?svd. According to the manual Writing R Extensions, this should still be recognized. When I try to use it in the help pages of my own packages, \bold{} is interpreted correctly. No idea what is going wrong and it's not that important, but I found it curious enough to report. Cheers Joris -- Joris Meys Statistical consultant Ghent University Faculty of Bioscience Engineering Department of Mathematical Modelling, Statistics and Bio-Informatics tel : +32 (0)9 264 61 79 Joris.Meys at Ugent.be ------------------------------- Disclaimer : http://helpdesk.ugent.be/e-maildisclaimer.php [[alternative HTML version deleted]]
On 23/05/2017 8:39 AM, Joris Meys wrote:> Hi all, > > Don't know if this is a known issue, but I couldn't find anything so I > report anyway. When checking eg ?qr in both RStudio and the naked R IDE, > the help page is rendered incorrectly. More specifically, any use of > \bold{...} is printed as is, rather than interpreted as bold. Same happens > on ?svd.In ?qr (and probably in ?svd), \bold is inside \eqn{}, so it is being interpreted as LaTeX markup rather than Rd markup, and since no alternative was given, is displayed as-is. If you actually wanted it to display properly in HTML and ascii, the current \eqn{\bold{Ax} = \bold{b}} would have to be written as something like \ifelse{latex}{\eqn{\bold{Ax} = \bold{b}}}{\bold{Ax} = \bold{b}} which is pretty tedious to write, and it's not the only example on that page. So I doubt if anyone will fix it.> > According to the manual Writing R Extensions, this should still be > recognized. When I try to use it in the help pages of my own packages, > \bold{} is interpreted correctly.You missed the part about \eqn. Duncan Murdoch> > No idea what is going wrong and it's not that important, but I found it > curious enough to report. > > Cheers > Joris >
Hi Duncan, that explains, thank you. If nobody finds the time to fix that, I might give it a shot myself this summer. Barbeque is overrated. Cheers Joris On Tue, May 23, 2017 at 3:10 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote:> On 23/05/2017 8:39 AM, Joris Meys wrote: > >> Hi all, >> >> Don't know if this is a known issue, but I couldn't find anything so I >> report anyway. When checking eg ?qr in both RStudio and the naked R IDE, >> the help page is rendered incorrectly. More specifically, any use of >> \bold{...} is printed as is, rather than interpreted as bold. Same happens >> on ?svd. >> > > In ?qr (and probably in ?svd), \bold is inside \eqn{}, so it is being > interpreted as LaTeX markup rather than Rd markup, and since no alternative > was given, is displayed as-is. > > If you actually wanted it to display properly in HTML and ascii, the > current \eqn{\bold{Ax} = \bold{b}} would have to be written as something > like > > \ifelse{latex}{\eqn{\bold{Ax} = \bold{b}}}{\bold{Ax} = \bold{b}} > > which is pretty tedious to write, and it's not the only example on that > page. So I doubt if anyone will fix it. > > >> According to the manual Writing R Extensions, this should still be >> recognized. When I try to use it in the help pages of my own packages, >> \bold{} is interpreted correctly. >> > > You missed the part about \eqn. > > Duncan Murdoch > > > >> No idea what is going wrong and it's not that important, but I found it >> curious enough to report. >> >> Cheers >> Joris >> >> >-- Joris Meys Statistical consultant Ghent University Faculty of Bioscience Engineering Department of Mathematical Modelling, Statistics and Bio-Informatics tel : +32 (0)9 264 61 79 Joris.Meys at Ugent.be ------------------------------- Disclaimer : http://helpdesk.ugent.be/e-maildisclaimer.php [[alternative HTML version deleted]]
Maybe Matching Threads
- help pages base R not rendered correctly?
- help pages base R not rendered correctly?
- Best practices in developing package: From a single file
- stats::line() does not produce correct Tukey line when n mod 6 is 2 or 3
- download.file does not process gz files correctly (truncates them?)