Many thanks ! Bert Gunter's answer is of course correct. The maintainer
suggests Stackoverflow or commercial advice - which is worrying as I have
some further questions concerning lists in [officer} - but first I'll do
some more research !
On Thu, Apr 9, 2020 at 5:12 PM Jeff Newmiller <jdnew...@dcn.davis.ca.us>
wrote:
> Rmarkdown is my first choice as well... but the options available there
> for controlling PDF output via LaTeX macros are incredibly powerful, while
> the options available for controlling Word output from Rmarkdown are
> extremely limited by comparison. ReporteRs and officeR provide considerably
> more fine-grained control over Word formatting and layout than Rmarkdown
> supports, so for meshing R output into an existing Word-based workflow
> without lots of manual tweaking there is no comparison.
>
> On April 8, 2020 10:12:36 PM PDT, cpolw...@chemo.org.uk wrote:
> >DocX is quite a complex file..it's actually a zip file which contains
> >an XML file describing the text and sub folders with other content such
> >as images.
> >
> >
> >The description of need is a little vague - but may be the way it is
> >described. Rmarkdown For instance can generate output to word.
> >ODFweave (now discontinued I think) can output to odx which can be
> >opened in word. Although it starts with a odx file and generated a new
> >version of it.
> >
> >
> >I use Rmarkdown to generate reports (mine are PDF) and if someone said
> >could I do a word document report I'd start with markdown...
> >
> >
> >
> >
> >
> >On 8 Apr 2020 18:08, 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.
> >>
> >
> > [[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.
>
--
dr hab. n. med. Jeremy Clark, prof. PUM,
Department of Clinical & Molecular Biochemistry,
Pomeranian Medical University in Szczecin; Pomorski Uniwersytet Medyczny w
Szczecinie,
Zakład Biochemii Klinicznej i Molekularnej,
ul. Powstancow Wlkp. 72, 70-111 Szczecin, Poland.
Tel. 0048 570112192; Tel. 004891 4661490; Fax. 004891 4661492
Email: jeremyclark...@gmail.com
[[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.
