Indeed, replacing ReporteRs functionality was the topic of this thread. I know... it can be a bit much to read an entire thread, but reading is needed if you want to avoid non-sequitur, especially when the thread was not on topic for this mailing list to begin with.
On April 15, 2020 10:33:05 AM PDT, Paul Bivand <paul.biv...@gmail.com> wrote: >However, the Reporters github page clearly says that the package has >been removed from CRAN and it has been replaced by the officer >package. > >Note that ReporteRs has been removed from CRAN the 16th of July 2018 >and is not maintained anymore. please migrate to officer. > >https://cran.r-project.org/web/packages/officer/index.html > >Paul > > >On Wed, 8 Apr 2020 at 18:22, Jeff Newmiller <jdnew...@dcn.davis.ca.us> >wrote: >> >> The OP clearly hasn't followed the excellent documentation... this is >not a maintainer problem. It is the act of printing the completed >object that puts a file on disk. >> >> However, the package author recommends in the README that help be >requested from stackoverflow, as the mailing list Posting Guidelines do >warn that contributed packages are not technically on topic in R-help. >(Simply from a practicality standpoint... there are thousands of them, >each with potentially voluminous details to distract from the R >language itself.) >> >> On April 8, 2020 10:08:09 AM PDT, Bert Gunter ><bgunter.4...@gmail.com> wrote: >> >But the OP explicitly notes that the read_docx package does *not* >write >> >files and asks whether there are *other* packages or functions that >> >provide >> >that functionality. It still seems to me that the ReporteR >maintainer >> >might >> >be the best place to go for that info, although there is certainly >no >> >assurance that he can provide it. >> > >> >Bert >> > >> >On Wed, Apr 8, 2020 at 9:56 AM Jeff Newmiller >> ><jdnew...@dcn.davis.ca.us> >> >wrote: >> > >> >> But before hassling the maintainer the OP should read the package >> >> vignettes and run some examples... read_docx does not write to any >> >files, >> >> so complaining that it doesn't will be fruitless. >> >> >> >> On April 8, 2020 9:31:41 AM PDT, Bert Gunter ><bgunter.4...@gmail.com> >> >> wrote: >> >> >This sounds like the sort of specialized question that should be >> >> >directed >> >> >to the maintainer (?maintainer) rather than to a general Help >list >> >such >> >> >as >> >> >this. >> >> > >> >> >Bert Gunter >> >> > >> >> >"The trouble with having an open mind is that people keep coming >> >along >> >> >and >> >> >sticking things into it." >> >> >-- Opus (aka Berkeley Breathed in his "Bloom County" comic strip >) >> >> > >> >> > >> >> >On Wed, Apr 8, 2020 at 9:23 AM A Biologist >> ><jeremyclark...@gmail.com> >> >> >wrote: >> >> > >> >> >> Dear All, >> >> >> >> >> >> Mac Catalina - R 3.6.3 - all up-to-date packages. >> >> >> I would like to re-create the functionality which was found in >the >> >> >package >> >> >> {ReporteRs} by creating a .docx file in a folder on my computer >> >from >> >> >within >> >> >> R - which can subsequently be used by the {officer} function >> >> >read_docx. >> >> >> The function read_docx on my system does NOT create a new >> >document, >> >> >and >> >> >> neither does the following code: >> >> >> new.word.doc=function(){ report = read_docx(path ..name.. >> >".docx")) >> >> >> return(report) } >> >> >> doc=new.word.doc() >> >> >> >> >> >> I can use {base} file.create to create a file with an extension >> >.docx >> >> >- but >> >> >> apparently this is not a .docx file - and read_docx can't read >it. >> >> >> Is there another R package or function which I can use in order >to >> >> >create >> >> >> (and then close the link to R so that it can be used by another >> >> >package) a >> >> >> .docx file ? >> >> >> >> >> >> Many thanks in advance. >> >> >> >> >> >> [[alternative HTML version deleted]] >> >> >> >> >> >> ______________________________________________ >> >> >> R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, >see >> >> >> https://stat.ethz.ch/mailman/listinfo/r-help >> >> >> PLEASE do read the posting guide >> >> >> http://www.R-project.org/posting-guide.html >> >> >> and provide commented, minimal, self-contained, reproducible >code. >> >> >> >> >> > >> >> > [[alternative HTML version deleted]] >> >> > >> >> >______________________________________________ >> >> >R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see >> >> >https://stat.ethz.ch/mailman/listinfo/r-help >> >> >PLEASE do read the posting guide >> >> >http://www.R-project.org/posting-guide.html >> >> >and provide commented, minimal, self-contained, reproducible >code. >> >> >> >> -- >> >> Sent from my phone. Please excuse my brevity. >> >> >> >> -- >> Sent from my phone. Please excuse my brevity. >> >> ______________________________________________ >> R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see >> https://stat.ethz.ch/mailman/listinfo/r-help >> PLEASE do read the posting guide >http://www.R-project.org/posting-guide.html >> and provide commented, minimal, self-contained, reproducible code. > >______________________________________________ >R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see >https://stat.ethz.ch/mailman/listinfo/r-help >PLEASE do read the posting guide >http://www.R-project.org/posting-guide.html >and provide commented, minimal, self-contained, reproducible code. -- Sent from my phone. Please excuse my brevity. ______________________________________________ R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
