On Sat, 2005-10-15 at 21:30 +0100, Buchanan, Stuart wrote:
> > > The reason to push on with using pdf as one of the
> > preferred formats is
> > > that generating a table of contents/index is
> > doable. I have seen web
> > > pages cut in half by browsers and you can't
> > guarantee the position of an
> > > image when printed.
> > >
> > > PDFs rock for printing, HTML for reading off
> > screen.
> > >
> >
> > If you want a really generic solution, use the
> > Docbook DTD
> > (SGML or XML flavour, as you prefer), and have the
> > PDF/HTML
> > built automatically from the same source. As an
> > added bonus,
> > you'll get RTF, TeX and whatnot other backends free.
>
> I made an effort to make the HTML as simple as
> possible so it would print OK, but looking at Print
> Preview on my browser, the images don't paginate
> properly - some are split over a page-break. Oh
> well...
>
> Personally, I found it much easier to write in HTML
> than to use Latex or whatever and convert to PDF.
> However, if we decide to standardize on a document
> format (not a bad idea...) or create a single manual
> I'd be happy to convert my tutorial.
>
> -Stuart
>
Stuart,
I have been making a few changes to the Install and Getting Started
manual, with some guidance from Martin Splott. While the Authoritative
document format is LaTex, building a pdf is a matter of running one
script.
I'm not sure which manual these tutorials should be in.
- Flight School
- Installation and Getting Started.
- Or a separate manual.
For now I'd suggest adding it to the Flight School as an appendix.
(Is Carl Hofer contactable as the source document isn't in a FlightGear
CVS branch). This document was written for 0.9.3.
George Patterson
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
