> > I also see in your latest patch the part
> >
> > exec > $PDF_OUTPUT
> >
> > Its obvious intention is to open the output file and redirect the later
> > '-' (stdout) to it. Does this work with every Bourne type shell?
It should work in every Korn shell derivative, including ksh, pdksh
4,5', 0.3i]: can't break line
The already suggested approaches of reducing the inter-column spacing,
reduced inter-word spacing, etc are usually the best bets, and switching
to landscape also helps if the table is on a page by itself.
--
Nick Stoughton
, followed by the state of all
the environments in the environment dictionary (if the current
environment is one of these, it is simply flagged as "CURRENT
ENVIRONMENT", and not reprinted).
I found this tremendously helpful in debugging the issue I had, and
offer a patch to implement this
you are (in doing this, I noticed I had failed to update
man/groff.man ... additional patch attached for that):
2006-09-01 Nick Stoughton <[EMAIL PROTECTED]>
Add a request, '.pev' to print environment information
(similar to .pnr and .ptr to print numbe
On Fri, 2006-09-01 at 20:10 +0200, Werner LEMBERG wrote:
> > Here you are
>
> Thanks.
>
> > (in doing this, I noticed I had failed to update
> > man/groff.man ... additional patch attached for that):
>
> Well, it's necessary to add entries to groff_diff.man, man/groff.man,
> and NEWS also. Sinc
ived it from a list I maintain) you can remove the footer
altogether.
--
Nick Stoughton Cell: 510 388 1413
USENIX Standards LiaisonFax: 510 548 5738
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
atch that is in 1.19.3 to make the promise above work ... but
it looks like I broke this on the way!
I'll try and see if I can improve on my previous patch ... you can
almost certainly work around it by adding a ".br" after your short
paragraph.
--
Nick Stoughton
>
That would be because of the missing ' on the second line:
\Z'\v'1m\\$2\v'-1m'' should be \Z'\v'1m'\\$2\v'-1m''
--
Nick Stoughton Cell: 510 388 1413
USENIX Standards LiaisonFax: 510 548 5738
On Mon, 2007-02-19 at 18:44 +, [EMAIL PROTECTED] wrote:
> Hi Folks,
>
> I have observed something strange with quoted arguments to a macro:
>
>
> .de amac
> \Z'\v'-1m'\\$1\v'1m''
> \Z'\v'1m\\$2\v'-1m''
> ..
> Here is the macro amac in operation:
> .amac "First argument" "Second argument"
>
On Mon, 2007-02-19 at 18:44 +, [EMAIL PROTECTED] wrote:
> Hi Folks,
>
> I have observed something strange with quoted arguments to a macro:
>
>
> .de amac
> \Z'\v'-1m'\\$1\v'1m''
> \Z'\v'1m\\$2\v'-1m''
> ..
> Here is the macro amac in operation:
> .amac "First argument" "Second argument"
>
Try using tr ... The character '^@' is a null byte (for tr, this is
'\000'). You can strip out all control chars by:
tr -d '[:cntrl:]' < xxx.wpd > xxx.txt
(or, in vim: gg!Gtr -d '[:cntrl:]')
This won't strip out chars with the top bit set, but read the man page!
On Tue, 2007-03-13 at 15:15 -0
On Thu, 2007-08-02 at 16:44 -0700, andlabs wrote:
> Hello. I'm working with code that amends to ms' PP. The code uses a number
> register 1t - that is the number 1 followed by lowercase t. First, is such
> an identifier legal in groff? Second, what happens if a register is not
> defined with .nr an
abstraction when I'm
dealing with the source of a document. Word does not.
So, my real question, I guess, is do you care only about the
bold/italic/font information, or do you care about the meaning (and
possible other side effects, such as indexing) behind the font?
--
Nick Stoughton <[EMAIL PROTECTED]>
USENIX
Certainly none I've ever used ...
I'd write this as
.PS
A: circle "A"
B: circle "B" at A.left
.PE
which in my mind is a lot clearer!
--
Nick Stoughton Cell: 510 388 1413
USENIX Standards LiaisonFax: 510 548 5738
On Tue, 2007-08-28 at 19:39 +0200, Axel Kielhorn wrote:
> Why is .mso de.tmac preferred over .so de (I assume the tmac should
> be
> omitted, right?) If it works with -m it should work with .so, or did
> I
> miss something?
You missed something!
.so file
will include "file" ... if the file st
On Mon, 2007-09-17 at 00:25 +0100, [EMAIL PROTECTED] wrote:
> On 16-Sep-07 22:15:55, Werner LEMBERG wrote:
> >> > I don't think classic troff mm's ":p" has ever been in groff's mm,
> >> > which has used "ft*nr" as long as I've known it (about 1990)!
> >>
> >> The obvious "solution" to that "proble
st
4,000 pages of hyperlinked PDF (thanks to Keith Marshall's pdfmark
macros) in a supserset of the mm macros (with a good amount of tbl and
eqn preprocessor). And if we had to start over again, though there are a
few TeX proponents around the committees, I am certain we would use
groff again .
If I understand your problem correctly, when we build the POSIX spec we
have a similar problem. I have a macro that I ensure is called at the
end of any run. This uses .tm to print a macro (.pn) to stderr with the
final page number which I then save to a separate file. This file is an
input to the
On Fri, 2008-11-14 at 19:38 -0500, Luke Huang wrote:
> Wow, there were so many masters of troff/groff answering my stupid
> question. Thanks a lot.
>
> You are all right, ``mm'' macro of the newest groff has *NOTHING*
> wrong. However, current version of evince does its job as well
And in a similar vein, there's the eight levels of Unix knowledge:
http://www.komputado.com/haha/unixguru.htm, of which the most advanced is:
Wizard
- Fixes bugs by patching the binaries.
- Writes his own troff macro packages.
- Writes device drivers with *cat>*.
- Can answer any ques
20 matches
Mail list logo
