ccornell - OpenOffice.org wrote:
BTW:
3) Should internal Wiki links be to pages in this doc, or to the Wiki
page?
Wiki links... this is one I've thought a bit about. I guess it depends
on how much post-processing we want to do on these documents, and what
reader type we want to target for these documents. Adjusting the links
takes time - and in something like the 1800+ page Developer's Guide, it
becomes a huge job.
By default, the rendered document links point to a specific
dated/versioned Wiki page. I started changing these to point instead to
the current wiki page, but this involved quite a bit of work to fix...
so I stopped and left them as they are.
(I could be off base on this, but this is what I was thinking yesterday
as I was working on the Basic Guide...) Since this document is designed
to be read offline - printed or read in an offline reader, there is not
much point in linking to external websites/pages. I would suggest that
we simply remove all hyperlinks. Treat this as a document to be
printed. This simplifies the post processing... a LOT. Ctrl+M on the
links to remove them, and we're done. If someone wants to follow all
the links to other web pages, he/she should be reading from the Wiki.
All up for discussion of course :-) This export process is still early
stages, and no specific steps have been outlined or nailed down (we
should/could start a Wiki page up for the procedure and provide a
template).
Quick take:
There would seem to be at least four possibilities for Wiki links:
1) to dated page
2) to current page [better]
3) to anchor in document [what I was thinking of]
4) to footnote with displayed hyperlink [for printing]
5) open a new Writer window, showing the newly-converted Wiki page
[well, I can dream, can't I?]
The nice part is that most of these can be done by a post-processing
routine in Basic. I am still straining my brain, trying to find a good
way, from the UI point of view, to do both (2) and (3) at the same spot.
Do the anchor points survive the conversion process? (I.e., can (3) be
done at all? Button call to embedded macro, with link texts as parameters?)
On reading the doc vs. reading the Wiki, I find reading the doc, in
Writer, much more convenient, and I doubt I am alone in this. (Having a
scrollable TOC only one click away, in the Navigator, is wonderful. So
is the page flow. A Wiki is great for quick look-ups, but for reading an
entire document? PITA.) Hence, I would like to see the links preserved
in the .odt form, especially the external links (mostly to the API).
If you would like code to deal with all (or some) of the links, I'll
need a couple of pointers to existing raw refs as input, plus what they
should look like as output. The finding and transforming should be
fairly easy. /tj/
--
T. J. Frazier
Melbourne, FL
(TJFrazier on OO.o)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@documentation.openoffice.org
For additional commands, e-mail: dev-h...@documentation.openoffice.org
