X-Git-Url: https://sipb.mit.edu/gitweb.cgi/ikiwiki.git/blobdiff_plain/2eb4621268fae9bc926b2f8474a8fabe95d45d6b..21c3f606b82ffca8c1b8fed2010f3e6167953a35:/doc/index/discussion.mdwn diff --git a/doc/index/discussion.mdwn b/doc/index/discussion.mdwn index 4f8ead729..e6ed33eec 100644 --- a/doc/index/discussion.mdwn +++ b/doc/index/discussion.mdwn @@ -72,6 +72,17 @@ easily, perl is possible (but I'm not strong in perl). > format. Another option would be writing a ikiwiki plugin to support the > TWiki format. --[[Joey]] +> Jamey Sharp and I have a set of scripts in progress to convert other wikis to ikiwiki, including history, so that we can migrate a few of our wikis. We already have support for migrating MoinMoin wikis to ikiwiki, including conversion of the entire history to Git. We used this to convert the [XCB wiki](http://xcb.freedesktop.org/wiki/) to ikiwiki; until we finalize the conversion and put the new wiki in place of the old one, you can browse the converted result at . We already plan to add support for TWiki (including history, since you can just run parsecvs on the TWiki RCS files to get Git), so that we can convert the [Portland State Aerospace Society wiki](http://psas.pdx.edu) (currently in Moin, but with much of its history in TWiki, and with many of its pages still in TWiki format using Jamey's TWiki format for MoinMoin). +> +> Our scripts convert by way of HTML, using portions of the source wiki's code to render as HTML (with some additional code to do things like translate MoinMoin's `\[[TableOfContents]]` to ikiwiki's `\[[toc ]]`), and then using a modified [[cpan HTML::WikiConverter]] to turn this into markdown and ikiwiki. This produces quite satisfactory results, apart from things that don't have any markdown equivalent and thus remain HTML, such as tables and definition lists. Conversion of the history occurs by first using another script we wrote to translate MoinMoin history to Git, then using our git-map script to map a transformation over the Git history. +> +> We will post the scripts as soon as we have them complete enough to convert our wikis. +> +> -- Josh Triplett + +>> Thanks for an excellent Xmas present, I will appreciate the additional +>> users this will help switch to ikiwiki! --[[Joey]] + ---- # OpenID @@ -161,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? @@ -174,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? @@ -192,3 +218,10 @@ editing a page. Is that an option that can be enabled? > It's doable, it could even be done by a [[todo/plugin]], I think. > --[[Joey]] + +---- + +# Max submit size? + +Any setting for limiting how many kilobytes can be submitted via the "edit" form? +-- [[JeremyReed]] \ No newline at end of file