> OK, thanks, I don't quite know what was happening before but it seems to be working right now.
> --[[Chris]]
+>> Weird. I wish I knew what happened, but as it's working now, I'm
+>> guessing some kind of user error was involved. --[[Joey]]
+
* I wish there was a mailing list, much easier for this sort of stuff than this, apart from
anything else I get to use a decent editor.
> 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 <http://xcb.freedesktop.org/ikiwiki>. 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
# ACL
-How about adding ACL? So that you can control which users are allowed
-to read, write certain pages. The moinmoin wiki has that, and it is
-something, that I think is very valuable.
-
-> ikiwiki currently has only the most rudimentary access controls: pages
-> can be locked, or unlocked and only the admin can edit locked pages. That
-> could certianly be expanded on, although it's not an area that I have an
-> overwhelming desire to work on myself right now. Patches appreciated and
-> I'll be happy to point you in the right directions.. --[[Joey]]
-
->> I'm really curious how you'd suggest implementing ACLs on reading a page.
->> It seems to me the only way you could do it is .htaccess DenyAll or something,
->> and then route all page views through ikiwiki.cgi. Am I missing something?
->> --[[Ethan]]
-
->>> Or you could just use apache or whatever and set up the access controls
->>> there. Of course, that wouldn't integrate very well with the wiki,
->>> unless perhaps you decided to use http basic authentication and the
->>> httpauth plugin for ikiwiki that integrates with that.. [[--Joey]]
-
->>>> Which would rule out openid, or other fun forms of auth. And routing all access
->>>> through the CGI sort of defeats the purpose of ikiwiki. --[[Ethan]]
+> Moved to [[todo/ACL]] --[[Joey]]
----
# Canonical feed location?
-Any way to use `inline` but point the feed links to a different feed on the
-same site? I have news in news/*, a news archive in news.mdwn, and the
-first few news items on index.mdwn, but I don't really want two separate
-feeds, one with all news and one with the latest few articles; I'd rather
-point the RSS feed links of both to the same feed. (Which one, the one
-with all news or the one with the latest news only, I don't know yet.)
-
-> Not currently. It could be implemented, or you could just turn off the
-> rss feed for the index page, and manually put in a wikilink to the news
-> page and rss feed. --[[Joey]]
-
->> That wouldn't use the same style for the RSS and Atom links, and it
->> wouldn't embed the feed link into `<head>` so that browsers can automatically
->> find it.
+Moved to [[todo/canonical_feed_location]] --[[Joey]]
----
Any plugins or support for using asciidoc or txt2tags as the wiki language and/or exporting to asciidoc or txt2tags?
+> No, but it should be quite easy to write such a plugin. The otl plugin
+> is a good example of writing a formatting plugin that uses an external
+> conversion program, like asciidoc or txt2tags. --[[Joey]]
+
----
# LaTeX support?
Any plugins or support for exporting to LaTeX?
(If not could use asciidoc or txt2tags mentioned above to generated LaTeX.)
-----
-
-# Using with RCS?
+> It's already [[been_requested|todo/latex]], although perhaps not
+> working the way you're thinking of. Noone is currently working on it.
+> --[[Joey]]
-Any examples of using co(1), ci(1) and other RCS related tools with ikiwiki?
+>> 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
----
Any examples of using ikiwiki with cvs?
+> No, although the existing svn backend could fairly esily be modified into
+> a CVS backend, by someone who doesn't mind working with CVS. --[[Joey]]
+
----
# Show differences before saving page?
It would be nice to be able to have a button to show "Differences" (or "Show Diff") when
-editing a page. Is that an option that can be enabled?
\ No newline at end of file
+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]]
+
+> Not currently. Worried about abuse? --[[Joey]]
+
+>> I didn't want it abused accidently or with malice. I was thinking that Perl's CGI.pm would handle this, but I don't see that.
+>> I read that textarea max bytes may be 500 lines or 28000 characters or 30000 characters or 64kB. It seems like it
+>> varies and I didn't test myself, because I guess it may depend on different clients and different HTTP servers.
+>> This could be checked using javascript on the client side (before submitting) and by checking size on server side (before saving). --[[JeremyReed]]
+
+>>> The absolute limit varies by browser. If there are web servers that
+>>> also limit it, I don't know of them. --[[Joey]]
+
+----
+
+# Disable sub-discussion pages?
+
+Moved to [[bugs]] -- [[Joey]]
+
+----
+
+# wiki\_file\_regexp and RCS ,v files
+
+I have RCS ,v files in my source directory. But get many "skipping bad filename" warnings.
+
+Also I don't see wiki\_file\_regexp documented. Because it is used with $config{wiki\_file\_regexp} I assume it can be set in the ikiwiki.setup.
+I added a comma to it in my IkiWiki.pm in the defaultconfig(). But that was wrong (so I reverted back), because then the ,v files were copied to my www tree.
+
+What is the correct way to include ,v RCS revision files in my source tree without receiving the "bad" messages and without copying over to www tree?
+
+-- [[JeremyReed]]
+
+> Add the ,v to the $config{wiki_file_prune_regexps} array. This is how we
+> skip equivilant files from other revision control systems too.
+> --[[Joey]]]
+
+----
+
+# Textile Plugin
+
+It was trivial, but I put together a plugin that uses the Textile markup
+language, which I find to be the most superior of the various options for
+that sort of thing. Where or how do I submit it for inclusion?
+
+> You can post it to [[plugins/contrib]]. --[[Joey]]
+
+>> Thanks. I tried using the "Add new post" form there, but apparently made a [mess of things somehow](http://ikiwiki.kitenet.net/contrib/textile___40__third-party_plugin__41__.html). Sorry about that.
+
+How does one go about making a markup language added by means of a plugin, the default markup language. In other words, I would like the index page to be written in Textile. If I include a index.txtl (where txtl is the extension I have assigned to be handled by the textile plugin), ikiwiki will ignore it and make a new index.mdwn.
\ No newline at end of file