The sources of the Free Pascal compiler, RTL, packages and utilities. See https://www.freepascal.org/ for more info.
Go to file
2005-05-05 11:23:51 +00:00
compiler + Patch from Christian Iversen to fix defined() macro command 2005-05-02 18:44:00 +00:00
demo + Info about macos demo 2005-04-28 18:00:15 +00:00
docs * fixes after Mac OS X ipc patches 2005-05-04 13:39:22 +00:00
fcl + Patch from Vincent Snijders to fix reading of entities 2005-05-02 13:06:51 +00:00
fv fix mouse clicks on the scrollbars 2005-04-24 21:49:23 +00:00
ide * checkmem removed 2005-04-25 08:19:10 +00:00
install revert to old cp.exe from 1.9.4 2005-05-05 11:23:51 +00:00
installer * util_s_os2.zip 2005-03-06 18:00:07 +00:00
packages + Added overloaded calls with untyped buffer for send/recv calls. As reported by zephod@skynet.be 2005-05-04 08:08:44 +00:00
rtl + Fix for Utf8ToUnicode from Lazarus bug tracker 888 2005-05-04 10:34:48 +00:00
tests new bug 2005-05-05 08:53:05 +00:00
utils + Added support for opaque types 2005-05-04 08:38:58 +00:00
Makefile * no /install/binos2/*.h necessary 2005-03-06 16:02:11 +00:00
Makefile.fpc + documented 'make all' 2005-03-08 20:47:12 +00:00

This is the README for the Free Pascal documentation.

All documentation is stored here, in LaTeX format and in fpdoc format.
it uses special style files (fpc*.sty) which are also in the directory.

do a 'make dvi' to produce the dvi format of the docs.
a 'make html' will produce the html version (using latex2html).
a 'make ps' will produce PostScript documents.
a 'make pdf' will produce PDF (Portable Document Format) documents.
a 'make txt' will produce plain text documents.

If you want to produce dos docs, you can do a 'make htm' this will convert
the .html files to .htm files (including all references), suitable for a 8:3
format.

The rest of this document is only interesting if you want to write docs.
Otherwise, you can bail out now.

THE DOCS...

Why LaTeX ? 
- because I like a printed copy of the manuals, HTML just isn't good enough 
  for this.
- I know LaTeX very well :) (mind you : html also !)
- It converts to many other formats.
- many other reasons.

In order to translate the things to HTML, I use latex2html, since it is the
most powerful and flexible, although sluggish... 

Why fpdoc ?
- Because it always creates up-to-date documentation.
- The documentation is separate from the units contrary to many other
  documentation tools which require comments in the sources, which makes
  the source unreadable.
- It's written in FPC.



Then how to proceed ?
If you just want to write general latex docs, just use fpc.sty. 
fpc.sty.doc describes what fpc.sty does. (one day I'll integrate them using
the doc package, but I need some time for it)

If you want to document units, use fpdoc. It is documented fairly complete,
and you can have a look at the many .xml units for examples on how to use
it.

Happy TeXing,

Michael.