I should also mention that, that this accept/decline GPL is just for the Windows
installer. In
the Linux RPM, there is just a copy of the GPL in the docs directory, and IIRC an
entry was put
into the .spec file to say the licence is GPL, so that will show up in the package
manager. And
the
I'd like to suggest that the Docs link on the Web site be expanded.
Right now it takes one to the HTML version of the user manual, which
is buggy and out-of-date. There's a lot of other documentation.
I'd like to suggest that the Docs link take a visitor to a page with
links to the User Manual,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd like to suggest that the Docs link on the Web site be expanded.
Right now it takes one to the HTML version of the user manual, which is
buggy and out-of-date. There's a lot of other documentation.
I literally just unpacked
I've been pondering re-writing the User Manual, but I'd like a more
friendly primary format. I'm partial to TexInfo, which produces TeX
(and thus PS and PDF) outputs, as well as HTML and Info (which can be
loaded into Emacs for handy reference). For ILU, we used something
called TIM, which is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For ILU, we used something called TIM, which is TexInfo Macros --
basically a feeble macro front-end for TexInfo. The macros added URL
links and images, which at the time weren't in TexInfo. It looks to me as
if Texinfo 4.2 will support both.
On Fri, Oct 18, 2002, Bill Janssen wrote:
Right now it takes one to the HTML version of the user manual, which
is buggy and out-of-date.
The Viewer chapter is up-to-date ;-)
/Mike
___
plucker-dev mailing list
[EMAIL PROTECTED]
Great work! Looks very nice in Mozilla (actually, Chimera).
I particularly like the gallery.
Bill
___
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
At 06:32 PM 10/18/2002 -0400, David A. Desrosiers wrote:
I'm all for whatever can help us _EASILY_ maintain the manual as we
add features and functions to it. Also, it's important that the manual
generate validatible code, which many of the standard generation tools do
not. Maintaining
David, what is the preferred format generally? I'm not Tex or LaTex
(casing?) comfortable, but work decently well with XML and am
exceptionally comfortable with HTML.
I'm partial to SGML as a core format, others may differ.
I'm doing the Guide in HTML simply because it's universal,
One quick question. Where do I download the 1.2 source?? It isn't on
the downloads page.
A few ways, via cvs (cvs link) or the Snapshot link.
I'll pull the plucker_1_2 tag, pack it up and put it on the download
page for people who wish to download that directly instead of
10 matches
Mail list logo
