On Thursday, 20 October 2005 at 15:07:32 -0400, Zvezdan Petkovic wrote:
> On Wed, Oct 19, 2005 at 10:51:45PM -0600, D. E. Evans wrote:
>> groff is now a major component in a majority (I would think) of
>> UNIX systems, and UNIX variants. It is used for online manuals,
>> and print manuals; it is u
On Thursday, 20 October 2005 at 15:37:12 -0600, Clarke Echols wrote:
>
> I'd like to create the equivalent of a PowerPoint presentation using
> PDF or other reasonable display. It would be nice to be able to use
> the entire screen instead of a window, like PowerPoint does. It has
> to run on Win
Ted Harding's post on the above topic a few days ago was great.
Not only did I learn about how to print a page background (something that I
occasionally wanted to do but didn't know how), but his several examples of
embedding Postscript code in a groff document has shown me new ways to use
gro
On Friday, 21 October 2005 at 13:26:33 +0530, Manas Laha wrote:
> Ted Harding's post on the above topic a few days ago was great.
Seconded.
> Not only did I learn about how to print a page background (something
> that I occasionally wanted to do but didn't know how), but his
> several examples of
> Thanks for the pdf. I had a look at the previous version a while ago
> but a China tour rudely interrupted my studies of it :-)
你講中文嗎?
> Certainly I would like to see a groff manual written in groff, with
> plenty of colour and graphics.
I envision that the best route is to extend the UTP for
On 21-Oct-05 Manas Laha wrote:
> Ted Harding's post on the above topic a few days ago was great.
>
> Not only did I learn about how to print a page background (something
> that I occasionally wanted to do but didn't know how), but his several
> examples of embedding Postscript code in a groff docu
Job Opening!!!
Hi dear,
Can i please have your attention for a moment?
This electronic message transmission contains information that is
confidential or privileged.If you are not the intended recipient, be
aware that any disclosure,copying, distribution or the using of
Job Opening!!!
Hi dear,
Can i please have your attention for a moment?
This electronic message transmission contains information that is
confidential or privileged.If you are not the intended recipient, be
aware that any disclosure,copying, distribution or the using of
On Fri, Oct 21, 2005 at 10:15:57AM +0300, Greg 'groggy' Lehey wrote:
> The real reason for this reply is: how do you *display* PDF slide
> sets? I currently use acroread, which renders well, but it's pretty
> slow (it can take a second to change to a complicated page, even with
> a 3 GHz CPU).
> > Keith, maybe you've sent this as a private mail to David ...
>
> Not intentionally. Looks like I hit "Reply" instead of
> "Reply-to-All", forgetting that groff list mailings don't set the
> "Reply-to" header appropriately :-( Could this be altered, as say,
> the SourceForge mail lists do?
Mh
> > > I'd be happy to submit patches once it's converted to roff but I
> > > just can't bring myself to submit documentation fixes to roff
> > > docs written in texinfo.
> >
> > Sorry, this won't happen for various reasons.
>
> I know you've told me before but it must not have been a very
> satisfy
On Fri, Oct 21, 2005 at 09:31:05PM +0200, Werner LEMBERG wrote:
> > > > I'd be happy to submit patches once it's converted to roff but I
> > > > just can't bring myself to submit documentation fixes to roff
> > > > docs written in texinfo.
> > >
> > > Sorry, this won't happen for various reasons.
>
On 22/10/2005, at 6:00 AM, Larry McVoy wrote:
I'm not sure how you are going to get more roff users when the first
thing
they see is the project not using its own product. A documentation
tool
where the documentation for it is written in a different tool? Come
on,
nobody is going to say "
On Fri, Oct 21, 2005 at 10:23:25AM +0300, Greg 'groggy' Lehey wrote:
> On Thursday, 20 October 2005 at 15:07:32 -0400, Zvezdan Petkovic wrote:
> > Take a look at O'Reilly books (colophon section). Until recently
> > they all were converted from format X into groff and printed.
>
> Has this change
Things I dislike about /software/groff:
1. The image is too large (horizontally). What about keeping
only the GNU head and printing press? (The title is already
prominently displayed below it.)
2. Should it be GNU roff (or runoff), not GNU Troff? Ditroff would
probably be more appropriate if s
"D. E. Evans" wrote:
>
> Things I dislike about /software/groff:
>
> 1. The image is too large (horizontally). What about keeping
> only the GNU head and printing press? (The title is already
> prominently displayed below it.)
Agreed. The text could be split onto two lines, the second
indente
> 1. The image is too large (horizontally). What about keeping
> only the GNU head and printing press? (The title is already
> prominently displayed below it.)
Agreed. The text could be split onto two lines, the second
indented from the first.
Since there is already a title disp
On Sat, Oct 22, 2005 at 09:10:39AM +1000, Miklos Somogyi wrote:
>
> On 22/10/2005, at 6:00 AM, Larry McVoy wrote:
> >
> >I'm not sure how you are going to get more roff users when the first
> >thing
> >they see is the project not using its own product. A documentation
> >tool
> >where the docum
Thanks to all who responded to my question about building a
presentation using groff instead of PowerPoint. The ideas were
very good, and I may still pursue them. As for now, I was looking
for a way to do what I needed to do using groff, going to PS or
PDF.
I discovered a way to create a backgro
19 matches
Mail list logo
