Differences between version 11 and predecessor to the previous major change of WlugWikiConversion.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 11 | Last edited on Monday, June 13, 2005 9:15:26 am | by JohnMcPherson | Revert |
| Older page: | version 9 | Last edited on Sunday, June 12, 2005 11:23:04 pm | by MattBrown | Revert |
@@ -4,8 +4,10 @@
!! Conversion of Wiki Content
I'm currently working on a script that was originally written by Isaac Wilcox. This does a reasonable first pass on converting the wiki markup, however there's a lot of things it doesn't do yet, mostly involving any old-style wiki markup, which is rife throughout the WLUG wiki.
+
+Maybe I need to stress this some more. __The script I have does not convert the content perfectly. It does not do most old-markup constructs at all, unless they happen to also be new-markup constructs. There are many new-markup constructs it does not understand. It is NOT finished. It is a LONG way from being finished. From the time I've spent on it so far, I would say that there is at LEAST as much time to be spent on it to get it to the point where we can bother trying to hand-fix the output, as there is in fixing/modifying the current wiki software.__
Also, having migrated the content, every page will need to be visited, and checked for validity, and resaved. This is very important! A lot of the 'special' pages within Mediawiki __only__ get updated when a page gets saved. The Backlinks and Category equivalents are obvious examples. We can let this happen "as the wiki gets used", but the fact is for the new site to work properly we will *have* to do this. We could, I suppose, write something which simulates editing then saving a page, which will address the automagic pages, but won't confirm the markup was translated completely.
I'm aware that if we aim for 100% conversion we'll probably fail, but what we're probably looking at is approximately 80% of the wiki markup being converted at the moment, and still a requirement to walk across pretty well all of the 7000 odd pages in the wiki.
@@ -32,8 +34,9 @@
!! Problems with the current wiki that we hope to address
* No (easy) security updates, as we are a fork of PhpWiki
* No ability to fix font problems across platforms due to PhpWiki nesting tags
+** I think we can do this with our current software, we just need to spend some time tweaking the theme. -- JohnMcPherson
* No ability to do any kind of layout inside pages, eg. text to the right of an image, a floating text box in a page (to move Coming Up from the sidebar to the main page)
----
