Erik -
On Sep 8, 2:04 pm, Erik Krause <[email protected]> wrote:
> If I understand correctly, the documentation is not yet for the upcoming
> version 4.0, is it?
My approach to the release process is
to always have a revision that passes
make distcheck
and my own test suite. Dunno whether this comes
from "Xtreme Programming" or "The Pragmatic
Programmer". Anyhow, this way we won't have a
Big Bang Release, but (hopefully) approach a
better state with each revision. Someday
somebody will yell "Stop, this is it!" and we'll
tag the revsion with "4.0".
> However, how shall we proceed with the wiki pages at
> http://wiki.panotools.org/Enfuse_reference_manual
> http://wiki.panotools.org/Enblend_reference_manual? The wiki would be a
> good possibility to cooperatively maintain the manual.
The sources of the documentation are in
the "doc" directory of the Enblend-Enfuse
project. The closeness to the code facilitates
to match the documentation with the code and I
pay great attention to the fact that they _do_
match. Accurate and comprehensive documentation
matters to me.
Moreover, some parts of the documentation are
generated directly from the configuration
information of the C++-sources. The amount of
this type of data even grows. E.g.: what is the
default verbosity level? 0 or 1, or what? A
wiki cannot mirror this. In fact the wiki's
contents could be downright wrong. Setting up
immutable pages counters the problem of false
information, though.
> However, it would
> be needed to update the pages first. If someone could provide me with a
> Diff of the older and the current version I could do this.
If you cannot translate it
automatically, you'll drown in different
versions. Promised!
> If you think it's better to maintain the manuals in TeX (which I believe
> is the native format) I would prefer to update the wiki with the final
> version. Unfortunately I don't know enough about TeX to do the Diff
> myself...
The GNU coding standards favor
documentation in Texinfo format. This is what
we use right now.
Furthermore, Texinfo is a powerful format, it
comes with fast translators to a variety of
output formats, and the sources are plain ASCII.
FYI, I would fight extremely hard against a
documentation format change.
To address the "collaboration" question: Anyone
can work on the documentation as they would work
on the code. There really is no difference.
Contributions are always welcome.
Cheers,
Chris
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---
