Bjoern Michaelsen wrote:
T. J. Frazier <tjfrazier <at> cfl.rr.com> writes:
I'd have fixed this myself, but do we want a better solution, with the
link in only one place?
I would prefer a link in one place too, but the links are sensible in both
locations, I think (I would like to have the needed downloads at the top of
the page), but I would also want those to identify what goes where.
If you have a good solution for this, go ahead (maybe one could just name the
requirements at the top and refer to the table below for source and destination
locations?).
My thought is to put the table itself at the top (with a brief
introduction), and let all the explanations follow, with no other
external links.
From our point of view, it makes maintenance easier and more reliable.
For the users, the table is what they're going to want to refer to,
probably over and over; having it at the top makes it easy to find. If
we tune the section headers so that they have the same names as the
table entries, then the users can use the TOC to go straight to some
individual explanation they need to look up. Or, on-page links to the
sections would be easy enough.
While I'm at it, I may move that very useful CLI-for-dummies tip up into
the first description of Cygwin.
All this is a fairly major reshuffle. If you have no major objections,
I'll do it, but your critical review (of the plan, and the result) is
very important: I've never built OO.o at all.
--
/tj/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
