T. J. Frazier wrote:
Jean Hollis Weber wrote:
I'm in the process of putting the Impress Guide on the OOo wiki...
Jean,
Could you take a minute and describe the process you're using? Clayton
told me about "Export to MediaWiki". It wasn't useful for my little wiki
page, but it sounds ideal for the kind of posting you're doing. In fact,
it should make a good page, somewhere under Help: Editing :-)
The Export doesn't seem to be documented anywhere, either, unless I've
missed something in the WG.
Short answer:
With the .ODT file open in OOo, go to File > Export and choose "Mediawiki"
under File Format, then click Export. This produces a file (with extension
.txt) that has wiki markup in it. Basically, that's it.
Then copy and paste the result into the wiki page, add the necessary template
links at top and bottom of each page for navigation and copyright info, save
the page, and lastly manually upload any pictures.
Longer answer:
Of course there's at least one "gotcha" -- which I probably should write a wee
bit about in the Writer Guide and perhaps a longer how-to for the wiki.
Depending on the layout complexity of the ODT file (and proper use of
Headings), and how any figures have been inserted and captioned, the resulting
.txt file may need little cleanup or it may need quite a lot. The user guide
files we've been producing need cleanup, but most of it is fairly easily done
with search-and-replace. (An example of cleanup is changing the "Tips" and
"Notes" from the tables used for their layout in our chapters into the style
used for the Docs wiki.) The one thing that appears to have to be done
manually is inserting filenames for any pictures.
BTW, I get the pictures by unzipping the .ODT and extracting the Pictures
folder, but if I had the pix already in separate files (eg screen captures), I
could skip that step.
Also BTW, I break up the user guide chapters into several pages, so I have to
also create a wiki TOC for each chapter as well as a TOC for each book. I
don't know of any way to automate this, though there may be one.
This is just one of many procedures I should write up, and perhaps then
someone else would show me a better or faster way to do some of it. :-)
--Jean
