summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-12-23 08:04:07 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-12-23 08:04:07 +0000
commitba53b64fb040310cfe8fc22f668ee5c744355a92 (patch)
treeb2269b68f5f6ea07af6ff9bf3a084ef42835ff18 /doc
parentf4e3e47e12b4a1d4009024a7f3b75b8b3615142d (diff)
web commit by JeremyReed: reply to two replies
Diffstat (limited to 'doc')
-rw-r--r--doc/index/discussion.mdwn15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn
index 5b6a659c7..ff2eb98eb 100644
--- a/doc/index/discussion.mdwn
+++ b/doc/index/discussion.mdwn
@@ -172,6 +172,12 @@ Any plugins or support for exporting to LaTeX?
> working the way you're thinking of. Noone is currently working on it.
> --[[Joey]]
+>> I did some tests with using Markdown and a customized HTML::Latex and html2latex
+>> and it appears it will work for me now. (I hope to use ikiwiki for many
+>> to collaborate on a printed book that will be generated at least once per day in PDF format.)
+>>
+>> --JeremyReed
+
----
# Using with RCS?
@@ -185,6 +191,15 @@ Any examples of using co(1), ci(1) and other RCS related tools with ikiwiki?
> that supports web commits with ci, and history (parsing the rcs files by
> hand?). If you're a masochist. :-) --[[Joey]]
+>> It does have history using rlog(1) which is similar format to "cvs log".
+>> I don't think it has any possible hooks. What would happen if I call
+>> ikiwiki directly from rcs_commit? (I didn't try yet.) On that note,
+>> I don't see any way for ikiwiki to generate a single file, but I guess
+>> that doesn't matter as --refresh should be fast enough.
+>> I made a Rcs/rcs.pm plugin from Stub. I have been testing it some.
+>>
+>> --JeremyReed
+
----
# Using with CVS?