in message <[EMAIL PROTECTED]>, wrote Dan Espen thusly... > > > - Possibility to have a printable version of the documentation. > > I.e., a ps and/or pdf FVWM book. > > I'd add, the ability to include images. Some of the documentation > talks about visual effects, but there are no illustrations in our > documentation.
(la)tex --> dvi (-->), ps, pdf > going to straight html. There were objections so it never > happened, but I'm still not convinced that man pages are > necessary. i suppose man pages could become pure reference instead of being both reference & explanation of things. then, man pages could point to appropriate places to look for details. something like xv(1) but not as extreme. that way, those who need explanations could be better served, while keeping man pages light & to the point foe those who are familiar w/ fvwm syntax. > However the .sgml is really hard to read. > The markup gets in the way. > I don't know if I'd like trying to edit the sgml with emacs or vi. > > The little POD that I've seen looked better. But I don't think > POD allows for images either. POD is easy almost like plain text. it, of course doesn't have facilities to include images. of course. how about LaTeX (or TeX) then? - parv -- -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
