[haghish]

Yes, even if you only want to use MarkDoc, you have to learn Weaver very well, especially for merging many LaTeX or HTML files into one document and also learning the img, txt, and tbl commands.

I update my website whenever I have the time. But the help file should get you through most of the basic features.

P.S. I updated MarkDoc and your bug should be fixed. You can confirm that when you have the time. Erase MarkDoc and install it from GitHub, then rerun your code

1. ado uninstall markdoc
2. net install markdoc, force from("https://raw.githubusercontent.com/haghish/markdoc/master/")
3. rerun your code

[valérie orozco]

Thank you Haghish for your answer and for correcting the bug. I update markdoc and I have no warning anymore!
However, note that he command "net install markdoc, force from("https://raw.githubusercontent.com/haghish/markdoc/master/")" doesn't work ("unknown network protocol"). I had to download the markdoc.ado and erases manually the previous one. It is ok now.


Concerning weaver, I read the help file. I succeed in writing an example that works perfectly using the "weave merge" command to use some Stata LaTeX output (or just weave using a .tex and directly putting the esttab command).

I just wonder now in which case is it better to use MarkDoc ?
It seems for me that if we want a pdf or .tex output, Weaver is more complete.
Until now, for creating slides I use markdoc (and markdown language), for creating pdf I use rather Markdoc (with LaTeX Language) or Weaver (with special language)...

For producing pdf slides, it seems that only MarkDoc can do this, right? (and so my esttab command producing LaTeX output is not understood).

As you see, I'm quite confuse. It would be nice if only one command can produce all output (html, tex, pdf, pdf slides, docx) allowing Stata LaTeX output to be understood (as Knitr for R does).

Finally, why do you adopt different markers telling to (write/or not) (the code/the output) (e.g OFF or div) (wasn't it be possible to write in md language with weaver?).

One again, this is only comments and questions trying to help me better understand how your 2 commands work. They are, indeed, very helpful in a reproducible research approach.

[haghish]

Can you confirm that the bug you got for installing MarkDoc from GitHub is similar to this one, reported by one of the users?
http://www.statalist.org/forums/foru...t-works-on-mac


MarkDoc and Weaver are two different approaches to dynamic documents. Weaver is very active, executing commands, and MarkDoc is passive, post processing the document. You shouldn't be confused! Just pick the one you like and suits your work better. But in any case, you should read Weaver thoroughly.

[valérie orozco]

Can you confirm that the bug you got for installing MarkDoc from GitHub is similar to this one, reported by one of the users?
http://www.statalist.org/forums/foru...t-works-on-mac

Yes, it is the same :

. net install markdoc, force from("https://raw.githubusercontent.com/haghish/markdoc/master/")
unknown network protocol
https://raw.githubusercontent.com/haghish/markdoc/master/ either
  1)  is not a valid URL, or
  2)  could not be contacted, or
  3)  is not a Stata download site (has no stata.toc file).

current site is still http://fmwww.bc.edu/repec/bocode/s/
r(671);

MarkDoc and Weaver are two different approaches to dynamic documents. Weaver is very active, executing commands, and MarkDoc is passive, post processing the document. You shouldn't be confused! Just pick the one you like and suits your work better. But in any case, you should read Weaver thoroughly.

Maybe I don't use Weaver properly. Maybe when you will have time to post examples on your site, I will understand! but don't worry, for the moment markdoc does a great job for me!