Mailing lists / fpc-devel / 2007-09
8 messages · 5 people · –
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Hi,
Having just installed the FPC 2.2 html documentation I have found a few problems already.
* The FCL documentation is included, but there is no link to in in the fpdocs-2.2.0/fpctoc.html file.
* The FCL has documentation for the IniFiles unit as show in the Online Help, but the IniFiles documentation is missing from the 2.2 downloaded help.
I'll report more and I find them...
Regard,
- Graeme -
4 more missing units from the FCL documentation. Available Online but not in the downloaded HTML help.
The missing units are:
* Blowfish
* CustApp
* simpleipc
* syncobjs
Regards,
- Graeme -
Dear Graeme,
I finally managed to set up tex4ht properly. Make html then produced correct html docs. It seems that a make pdf or ps is needed first. So,could it be the sequence of the build script?
All the best - Michael Schindler
Quite possible, probably it needs a couple of extra runs. I will have a look at it.
Michael.
Hi,
As I said, I had some problems to get tex4ht running. After contacting the maintainer he pointed me to a new version of tex4ht, which ran out of the box. However, the new version produced screwed up links.
I have to check, whether it is a question of the tex4ht version or my previous suspicion that the result depends on the sequence of make command (make pdf, make ps, make html).
All the best - Michael
Hi,
I had another go testing different versions of tex4ht. All of them except one (the one I used originally and fairly old one) produced wrong links. At least the sequence of make (ps, pdf, html ,...) can be excluded as source of the problem. Maybe the logs and protocols give a hint to where the problem is.
Best wishes - Michael Schindler
I once wrong a sed script that
was fixing the wrong links after
tex4ht was called.
I don't know if Michael committed this
into the fpcdocs svn repository,
but he can probably comment on that?
Pierre Muller
I did not, and I do not expect to do so; I am more than fed up with the HTML problems, they have been giving problems since day 1.
As far as I'm concerned, the next releases will contain PDF docs only for the manuals. I don't have the time (nor wish) to keep looking for solutions. All the patchwork is just that: patchwork, and there's no guarantee that it will not break on a next release.
Michael.