The sources of the Free Pascal compiler, RTL, packages and utilities. See https://www.freepascal.org/ for more info.
Go to file
2005-03-13 10:04:52 +00:00
compiler * fixed FieldAddress for 64 bit and CPUs requiring proper alignment 2005-03-13 08:34:58 +00:00
demo + First demo for macos toolbox 2005-02-22 22:17:32 +00:00
docs + Many updates and missing identifiers 2005-03-13 00:31:54 +00:00
fcl + Patch from Jesus reyes to fix brush style order 2005-03-10 20:02:28 +00:00
fv * fix matchmask 2005-03-07 16:59:42 +00:00
ide * fixed string Temporarily exit to DOS 2005-03-12 13:48:58 +00:00
install fix url in start menu 2005-03-09 23:57:33 +00:00
installer * util_s_os2.zip 2005-03-06 18:00:07 +00:00
packages * ctypes patch from Nikolay Nikolov 2005-03-13 09:34:08 +00:00
rtl * move draft 2005-03-13 10:04:52 +00:00
tests no message 2005-03-11 21:52:15 +00:00
utils + Fixed subsection/section writing 2005-03-10 20:32:16 +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.