[Pasdoc-main] PasDoc 0.12.0 release next week, and decisions for PasDoc2 branch

[Michalis K. <mic...@gm...>]

1. The recent French translation patch incompatibility clearly indicate
that our last release was done too long ago :) Let's change it. I want
to make PasDoc 0.12.0 release at some point next week.

We don't have *much* new stuff since last 0.11.0 release, but we have
something (see ChangeLog file). And the real goals are to
- Make an official release with new PasDoc_Languages.pas layout (as this
is heavily used by translators) and
- Show that We're Not Dead Yet :)

2. This brings me to the topic of the PasDoc2 branch. Stuff there is
still mostly not applied. The PasDoc_Languages.pas is one of the few
exceptions that actually got applied to trunk from PasDoc2 branch...

Quick test showed that the version from the PasDoc2 branch still fails
on a lot of testcases. This was mentioned e.g. here
https://sourceforge.net/mailarchive/message.php?msg_id=4883125E.2050809%40gmail.com
, and many issues are still not fixed. Some bugs that I've seen still
present: on error_introduction_twice_anchors (not detcted dupl anchors),
ok_abstract_sealed (esp. Range check error, and maybe "Warning:
unhandled section..." is also wrong), ok_back_comment (Range check
error), ok_vorbisfile. See the above mail for details, and run the test
suite (see tests/README) for more.

Even the autodoc fails (cd source/autodoc; make), with
- Such content, "
", is not allowed directly within the tag @orderedlist
- some warnings about unresolved links
- Fatal Error: bad Add mode (PasDoc_Items.pas, line 4169)

So a quick merge PasDoc2->trunk is out of the question.

So I'm trying to merge gradually, changing something to trunk/ and
changing something in branches/PasDoc2/, to eventually make these two
branches equal at the end, and bug-free. As of now, some small changes
were applied, and some were rejected (reverted to trunk state in
branches/PasDoc2/), see SVN commit logs for reasoning.

The really large architectural stuff is not really touched yet, so the
real and big decisions are still ahead.

Help in fixing PasDoc2 branch would be helpful. Please let me do the
final merging to trunk/, but everyone feel welcome to make fixes to
PasDoc2 branch to fix the issues. (Just make sure you do "svn up" often,
to synch with my own changes, as I plan to work intensively on this
within few next days.)

Ideally, autodoc and tests in tests/ subdirectory should proceed
perfectly, and then the incentive to apply the PasDoc2 branch will be
much larger.

Also, a documentation of user-visible improvements in PasDoc2 branch
would be helpful (I mean, a nice wiki page with examples, something
ready to show to users). The PasDoc2 branch supposedly includes
@groupbegin/end support, but I can't really test it since even autodoc
fails. And looking at code --- it's different than the planned usage on
http://pasdoc.sipsolutions.net/MichalisKamburelis#Support_for_groups_of_items
. So I'm not even sure if I want @groupbegin/end implemented this way,
and I don't know of other user-visible improvements from PasDoc2 branch.

I definitely want to decide before the 0.12.0 release what to do with
PasDoc2 branch. Merge what (if any) should be still merged, and
semi-officially "close" the PasDoc2 branch as a finished work. The issue
with applying PasDoc2 branch is hanging over us for ~2 years, so some
decision needs to be made, and then the new development should focus
again on trunk branch.

Michalis