Re: [Groff] Wrapping Text Arond Figures and Captions

2013-01-23 Thread Frank Jahnke
Thanks, Ralph. On Wed, 2013-01-23 at 22:22 +, Ralph Corderoy wrote: > That thread is split over two months in the archives. > > http://lists.gnu.org/archive/html/groff/2009-03/msg00042.html > http://lists.gnu.org/archive/html/groff/2009-04/msg2.html > FWIW, here's how LaTeX doe

Re: [Groff] new man-page groff-filenames.7 (filename extensions for roff files)

2013-01-23 Thread James K. Lowden
On Wed, 23 Jan 2013 10:47:46 +0100 (CET) Werner LEMBERG wrote: > > I could also use this documentation as part of groffer. Reliable > > filename extensions would be very nice for grog and groffer. > > Besides man pages, there aren't reliable extensions AFAIK. My gut > feeling is that groffer s

Re: [Groff] Wrapping Text Arond Figures and Captions

2013-01-23 Thread Ralph Corderoy
Hi, Frank Jahnke wrote: > The most recent discussion on this topic was in March 2009, and on the > 27th Werner Lemberg posted a macro that gets much of the way there. That thread is split over two months in the archives. http://lists.gnu.org/archive/html/groff/2009-03/msg00042.html http:

[Groff] Wrapping Text Arond Figures and Captions

2013-01-23 Thread Frank Jahnke
I would like to revisit a topic that has come up from time to time over the years but really has not been solved. That is wrapping text around figures and their captions. I write and submit a lot of proposals that unfortunately have severe page limits. Using PSPIC for the figure and caption in a

Re: [Groff] new groff-filenames.7 (roff filename extensions)

2013-01-23 Thread Bernd Warken
I added the actual version of groff_filenames.man. It would be possible to split the man-page in 2 parts: - a classical part that goes to roff.7 - the new groff part should go to groff.7 Then another short declaration should go to groff_diff.7 and groff.1. With that split, no new man-page is nec

Re: [Groff] new groff-filenames.7 (roff filename extensions)

2013-01-23 Thread Pierre-Jean
Ralph Corderoy wrote: > > Since I've got a lot of refer files, I've added a text/x-refer mime > > type in my system. It recognizes the file if it has the extension .ref > > or if it begins by a %. > > Does that clash with PostScript recognition at all? PostScript files > often starting with a %

[Groff] Unix Text Processing - PDF Bookmarks

2013-01-23 Thread Deri James
I have now completed the patch to the Unix Text Professing book to add pdf bookmarks to it. The results can be downloaded here:- The attached patch can be applied to the existing UTP source by doing:- patch -p1 <../patch-utp-1.0-v3.diff rm -rf index #

Re: [Groff] new groff-filenames.7 (roff filename extensions)

2013-01-23 Thread Ralph Corderoy
Hi Pierre-Jean, > Since I've got a lot of refer files, I've added a text/x-refer mime > type in my system. It recognizes the file if it has the extension .ref > or if it begins by a %. Does that clash with PostScript recognition at all? PostScript files often starting with a % as it's the commen

Re: [Groff] new man-page groff-filenames.7 (filename extensions for roff files)

2013-01-23 Thread Ralph Corderoy
Hi Werner, > Besides man pages, there aren't reliable extensions AFAIK. My gut > feeling is that groffer should use the `file' and/or the `grog' > program to properly detect the contents of an input file. man(1) needs certain extensions, that's not groff's business and man's man pages already de

Re: [Groff] new groff-filenames.7 (roff filename extensions)

2013-01-23 Thread Pierre-Jean
Hello troffers, "Bernd Warken" wrote: > the filename extensions for files using the roff language are not > documented. As there are many of these, a kind of standard should be > implemented. I propose the following description as a man-page > "groff-filenames.7"0. It should go to groff/man/

Re: [Groff] new man-page groff-filenames.7 (filename extensions for roff files)

2013-01-23 Thread Werner LEMBERG
>> I'm not sure there's enough here to justify a new man page. > > If you do not want a new man-page I can do it as a contrib-project. I think Keith wonders whether it is useful to have a *separate* man page, or whether it is better to integrate the information into the existing man pages. >> >