Current peardoc+PhD status

[Christian Weiske]

Hi all,


Just a mail to let you know the current status on peardoc+PhD:
After hacking mornings, days and nights in the previous weeks, I felt kinda burned out for peardoc in the last week and didn't really do much.

The problem I'm working on is the TOC (table of contets) generation which puts "refpurpose" instead of "refname" into the tocs, the titles and everything.
While this works good for php-doc, it's awful for peardoc. I'm basically trying to fix it for peardoc while keeping the old state for phpdoc - really hard. And I still suspect that there is a bug in mktoc.php causing all the trouble. I don't know when I will be done since it's a really daunting and boring task.

Other places that need work are
- getting the generated html to be strict XHTML
- try out the .php (pearweb) version and see if it works nicely

If you could spend some time and help out, it'd be great.

[Hannes Magnusson]

Post by Christian Weiske
Hi all,
After hacking mornings, days and nights in the previous weeks, I felt kinda burned out for peardoc in the last week and didn't really do much.

You've earned the break :)

Post by Christian Weiske
The problem I'm working on is the TOC (table of contets) generation which puts "refpurpose" instead of "refname" into the tocs, the titles and everything.
While this works good for php-doc, it's awful for peardoc. I'm basically trying to fix it for peardoc while keeping the old state for phpdoc - really hard. And I still suspect that there is a bug in mktoc.php causing all the trouble. I don't know when I will be done since it's a really daunting and boring task.

I assume you are referring to (PhD) bug#46351?
Are you fixing it in the XML or PhD? Like we discussed on IRC, it
really is a matter of interpretation of the spec, which I probably
fuckedup the first time around :)
I could probably look into fixing it for the phpdoc output, it
shouldn't be _that_ hard =)

Post by Christian Weiske
Other places that need work are
- getting the generated html to be strict XHTML

To be honest, that is mission impossible to do in the first run.
Besides, the current docs don't validate either so this shouldn't be
first priority :)


-Hannes