Hi list,
is there an easy way to place a picture ?
The design (a4 long):
two on top of each other with 4 and 3 columns. The "empty" column should
be filled with a piucture. i tried with .PSPIC and \X:import
but causing havoc the to page onlY
basicly it should look like this. 2 tables and X mar
o place the picture.
Then import name is abibild.eps then the bounding box and the scaling
factor.
re,
walter
Someone how knows macros may use this to place logos in headers ?
(Ted Harding) wrote:
On 14-Nov-05 walter harms wrote:
Hi list,
is there an easy way to place a picture ?
The design (a4 lo
hi,
is the usage of gs an option ?
it has program called ps2epsi.
re,
walter
Michail Vidiassov wrote:
Dear All,
can somebody, please, provide me with a working set of commands
to make a EPS file with groff?
Yes, I did read the FM, but the commands mentioned there did not work
for me.
Do th
if libicons works while iconv() produces wrong results would it be the
better way to use libiconv in general ? (until iconv() problems are fixed ?)
just my 2 cents,
walter
Bruno Haible wrote:
Alexander E. Patrakov wrote:
The answer "patch
glibc so that iconv transliterates the bullet to '
Hi Werner,
i have noticed the problem also (mostly fixing the problem by adding T{
to every line. a max width sepcifierer would be helpfull.
(forcing a wrap ?)
re,
walter
Werner LEMBERG wrote:
I would like to know, if there is a standard column width, when I use
the .TS macro?
Yes. If t
asume we create a datasheet from a database entry.
normaly you have line of "right" lenght (meaning they do not spoil the
layout). So your document is nice untill someonly realy uses the max
size in the database.
A simple version (read you know there is a large line) can be found at
/proc/cpu
hi people,
i get a bunch of spam since a few days via this list.
Am i the only one or have some more people seen spam also ?
re,
wh
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
if the page is not to large you can simply use postscript to rescale.
like 0.9 0.9 scale
of cause this works best if you have a table that fills the whole page.
re,
wh
ps: of cause it works also the other way around. if the table fits
nearly a page but leave some ugly gaps use 1.1 1.1 scale to
hi all,
iff i remember correctly you may use '\"tep (t for tbl e for eqn p for pic etc)
in the first line to invoke the various precompilers.
re,
wh
Clarke Echols wrote:
>
> ABSOLUTELY NO LINES, other than genuine troff/groff comment lines
> should appear in a man page file before the .TH lin
Larry Kollar wrote:
>
> John Poltorak wrote:
>
>> Can anyone explain what the differences are between groff and TeX and
>> which, if either would be most suitable for producing a magazine?
>
> They're both typesetters that use plain text files with embedded markup
> to produce output. Both use
hi all,
http://citeseer.ist.psu.edu/wolfman89flo.html
was helpful to me.
You can download the description: cs.technion.ac.il/pub/mi...flo.doc.ps.Z
(upper right corner)
somebody should rescue the document before it get lost forever.
Btw: homepage of Mr. Berry: http://se.uwaterloo.ca/~dberry/
per
hi list,
i have a warning that i do not understand.
the tbl below give a warning: grotty:tab:7: character above first line discarded
(using: groff -t -Tascii tab). Any idea why ?
.TS
tab(|);
l s s s
c c c c.
UEBERSCHRIFT
a|b|c|d
a|b|c|d
a|b|c|d
.TE
i use groff 1.18.1 from suse 10.0
re,
walter
I am sure it is harmless but as usual this happens if you try to
show one something
re,
wh
Werner LEMBERG wrote:
>> i have a warning that i do not understand. the tbl below give a
>> warning: grotty:tab:7: character above first line discarded (using:
>> groff -t -Tascii tab). Any idea wh
if the packages become part of 'groff' why not add a 'make docs'
and generate them on request ?
and other option is adding this to a 'make check' so it can double
as output test for the compiled system.
providing dcos in roff only is bad because people that start using groff
may have no idea how
seems a common misidentification:
see:
http://forums.clamwin.com/viewtopic.php?p=2783&sid=c054dd63729c567c31558a0b7700bab7
Werner LEMBERG wrote:
>> groff-1.18.1.4.tar.gz: Exploit.Linux.Gv FOUND
>> groff-1.19.2.tar.gz: Exploit.Linux.Gv FOUND
>
> Hmm. A tar.gz file should be harmless -- it does ne
Ralph Corderoy wrote:
> Hi Larry,
>
>> Groff was barfing with a "too many open files" error, which I worked around
>> by doing "ulimit -n 768" first. I ended up with over 640 HTML files. I'm not
>> sure why all every output file has to be open at once, though.
>
>
> $
>
> What status clo
hi list,
as author of several man pages i can say something about the "other" side.
When you read the current manuals (i admit that is some time ago) they ask
the authors to keep the file simple. Using the .TH, .BR, .I macros
means that the authors need to learn a few basic format stuff and that's
Eric S. Raymond wrote:
> walter harms <[EMAIL PROTECTED]>:
>> Stuff like tbl,eqn,... is discouraged (somebody mentioned it before) to keep
>> thinks simple.
>
> Discouraging TBL is the wrong advice to give nowadays. It used to make sense,
> back before the .\&
maybe you can add this as a little howto to the wiki and/or groff docu ?
re,
wh
Gaius Mulley wrote:
> Hi Ted,
>
> many thanks for the pointers - have found the chess postscript adobe
> fonts!
>
> Gaius
>
>
>
>
hi Larry,
i thing chris has a more basic problem
the last time i need .TS H i needed also the -ms macroset.
tbl alone did not help (yes, it was an older version)
i used: groff -t -ms -Tps my.tbl
(shorten version of cause in real it is:
cat <> According to page 6 of the document "tbl - A program
Am 19.08.2016 13:06, schrieb Steffen Nurpmeso:
> "James K. Lowden" wrote:
>
> |http://boredzo.org/blog/archives/2016-08-15/colorized-man-pages-understood-a\
> |nd-customized
> |
> |https://news.ycombinator.com/item?id=12296000
> |
> |It's a little far afield, but some here might be intere
Am 18.02.2017 19:07, schrieb James K. Lowden:
> On Sat, 18 Feb 2017 03:28:03 +
> Colin Watson wrote:
>
>> This version is much shorter and easier to understand than the
>> shell/awk version: we don't have to worry about convincing ls to
>> produce output that we can parse, and we don't have
Am 30.03.2017 17:02, schrieb Ingo Schwarze:
> Hi Ralph,
>
> Ralph Corderoy wrote on Thu, Mar 30, 2017 at 02:31:24PM +0100:
>
>> Research Unix Editions 8, 9, and 10 will no longer have copyright
>> asserted over them.
>
> While that vaguely resembles the wording of the original announcement,
>
> John Gardner hat am 14. Februar 2019 um 14:20
> geschrieben:
>
>
> > but there's also no great urgency to remove them, IMO
>
> Agreed. Personally, I think this is a non-issue.
>
> If Groff still uses backticks to support the (pre-POSIX) ancient Bourne
> Shell for Solaris 9-10, then we may
Hello list,
while looking at the xorg man pages there came
a question what this .ny0 may mean (i shorted that of cause):
.ny0
.TH XtAppNextEvent __libmansuffix__ __xorgversion__ "XT FUNCTIONS"
.SH NAME
.
I could not find this in the groff manual. It seems to do nothing.
Any ideas ?
r
ny0 to be macro ny with argument 0 .
> Mike
>
>
There is no macro definition .de ny.
I guess that is a left over from ancient times.
I wanted to make sure there is no .ny0 definition inside *roff
that i was missing.
re,
wh
&g
> Ralph Corderoy hat am 25. März 2019 um 11:29
> geschrieben:
>
>
> Hi Walter,
>
> > .ny0
> > .TH XtAppNextEvent __libmansuffix__ __xorgversion__ "XT FUNCTIONS"
> > .SH NAME
>
> Given .ny0 seems to be limited to the libx11 man pages here so
> https://www.x.org/wiki/ might be a starting poin
Am 25.03.2019 20:30, schrieb Ingo Schwarze:
> Hi Walter,
>
> Walter Harms wrote on Sun, Mar 24, 2019 at 07:16:07PM +0100:
>
>> while looking at the xorg man pages there came
>> a question what this .ny0 may mean
>> I could not find this in the groff manual. I
Hello list,
the groff_man page is listing some useful macros i did not notice sofar.
.EE/.EX and \*(lq,\*(rq
Are these save to use or are they a groff special ?
re,
wh
Am 08.08.2019 17:16, schrieb John Gardner:
> I've noticed that grog(1) will suggest options for preprocessors
> irrespective of whether they're even available on the user's system. Some
> aren't part of Groff, like grap(1). Others are excluded from certain base
> installations — Ubuntu Server, f
If that does not work try (assuming bash):
export GROFF_ENCODING=utf8
groff_pipeline
rationale:
doing
GROFF_ENCODING=utf8 groff_pipeline
is setting GROFF_ENCODING for the first element only, if anything later in the
pipe needs that also it is lost. Using export means that subshell also have
this
you can use recode to convert between latin1 and unicode 8
re,
wh
zoon wrote:
> Heinz, I changed my linux-Suse to ISO-8859-1 (the latin-1 coding)
> and IT WORKS FINE!
> Thanks, Thomas
>> Original Message
>> From: [EMAIL PROTECTED]
>> To: groff@gnu.org
>> Subject: Re: [Groff] Umlaut
>
> Am 21.09.2007 um 20:32 schrieb Axel Kielhorn:
>
>> Hi!
>>
>> I'm currently adding a section about further literature to my short
>> guide.
>> While reading the man-pages I stumbled over a few things:
>>
>> groff_char.man the Latin-1 (ISO-8859-1) code.
>>
>> groff.man (7) linkt to http://cm.bel
just a notice,
several years ago (1987 ?) a problem with theses backtics where noticed and
$( .. ) was introduced to replace them. before you start to replace every
backtic it may more resonable to replace it with $( .. )
re,
wh
Michael Kerrisk wrote:
> On Tue, Jun 17, 2008 at 8:52 AM, Werner
Werner LEMBERG wrote:
>> several years ago (1987 ?) a problem with theses backtics where
>> noticed and $( .. ) was introduced to replace them. before you start
>> to replace every backtic it may more resonable to replace it with $(
>> .. )
>
> But this is not relevant to the general problem of
may be Miklos can send the eqn output ?
re,
wh
Werner LEMBERG schrieb:
>> I searched the archives and found Robert's problems with eqn, but
>> nothing about the list of bad groff binaries on Macs.
>
> Ah, then my memory has tricked me. It's apparently only eqn which
> causes problems.
>
>
>
hi Clarke,
in case you sill have connections to HP. it would be nice if you could
convince them to publish that manuals on the internet.
re,
wh
Clarke Echols schrieb:
> I wrote an extensive tutorial on sed back about 1987 or so. It's part
> of HP's HP-UX User Guide series: "Text Editors and P
(Ted Harding) schrieb:
> On 14-Nov-08 12:03:58, Mike Bianchi wrote:
>> On Fri, Nov 14, 2008 at 08:58:50AM +0100, Werner LEMBERG wrote:
I ``troff'' a simple file, hello.mm whose content is:
.\" hello.mm
Hello World!
with the command line:
$ /usr/local/bin/gr
Anton Shepelev schrieb:
> Hello, Ralph
>
>> I don't know -me so can't answer on your specific problem. But have you
>> tried making the page length very long instead of trying to remove the
>> inter-page
>
> Yes, that was the first thing I did. Although I works, the "functinality"
> of this me
put a line break and
>> setting the page length to the _current_ page length.
>> .br
>> .pl \\n[nl]u
>
> Thanks for pointing out the real nroff way of doing it!
>
> Walter Harms:
>> hi Anton,
>> can you please post the groff version and th
Chris Schaller schrieb:
> Jan,
>
> encountered this one, too. What's your fileencoding in vim (:set
> fileencoding?). You might want to try to set it either to utf-8 or
> latin-1. Latter worked for me despite having encoding set to utf-8. So
> you are experiencing a vim configuration issue here.
Chris Schaller schrieb:
> Nope. Is this considered a bug? It's just about proper vim settings.
>
> - Chris
>
> On Thu, Apr 9, 2009 at 9:25 AM, walter harms wrote:
>>
>> Chris Schaller schrieb:
>>> Jan,
>>>
>>> encountered this one,
Efraim Yawitz schrieb:
> On Wed, Jun 17, 2009 at 7:01 PM, bousch ster wrote:
>>It seems grops and grohtml are not working for me on Windows Vista even
> with
>>UAC disabled.
>>
>>this command: groff -p hello.pic > hello.ps
>>results in: grops:4:fatal error: fdopen: Invalid
> argu
Ralph Corderoy schrieb:
> Hi Boudewijn,
>
>> I just tried StraceNT, here is part of the output generated when grops
>> encounters 'x init'
>>
>> [T5140] CreateFileA(34f818, c000, 3, 22fcd0, ...) = 104
>
> Based on WINE, CreateFileA is almost the same as CreateFileW which is
>
> HANDLE
KX-P1123 is a Matrixprinter. with ghostscript you can only use a "default" mode.
Adding the correct sequences to groff will give the opportunity to have the
right
sequences in the output.
re,
wh
Efraim Yawitz schrieb:
> I would like to understand what is the advantage of a custom groff driver
Tail Kinker schrieb:
> By default, tbl leaves tables on the left. You can also specify
> centered. It follows, therefore, that you should be able to define a
> right-aligned (relative to column) table. Anyone have a quick and dirty
> macro for this?
>
>
does r not work for you ?
re,
wh
Werner LEMBERG schrieb:
>>> I consider the groff mailing as a kind of archive which collects
>>> useful tips regarding the troff suite. Your tar bundle is part of
>>> that bundle.
>> I appreciate that. But I don't think that it would inspire people to
>> write directly to the archive.
>
> Well,
Mike Bianchi schrieb:
> On Thu, Feb 04, 2010 at 10:11:59PM +0100, Werner LEMBERG wrote:
>>> No macro, register, or string name within standard macro
>>> packages will ever end in * . Thus all user created names
>>> that end in * will never collide with any within the standard
>>>
hi,
i was playing with man pages and found by chance that empty lines before .TH
seems to confuse groff.
./"
./"
./"
.TH The header
works fine (no warnings what so ever) but has am empty page in front and
changes in page numbering are
ignored.
./"
./"
./"
.TH The header
But
Werner LEMBERG schrieb:
>> i was playing with man pages and found by chance that empty lines
>> before .TH seems to confuse groff.
>
> `Confuse'? I don't think so.
>
>>
>> ./"
>>
>> ./"
>>
>> ./"
>> .TH The header
>>
>>
>>
>>
>> works fine (no warnings what so ever) but has am empty pag
hi list,
I run into a problem that left me confused.
I wanted to use \_ to draw a line in a table.
My test programm looks like that:
.TS
tab(|);
l l l.
Geraet| Seriennummer | Bemerkung
_
xx |1 |\_
xx |1 |\
Am 13.01.2011 12:02, schrieb Tadziu Hoffmann:
>
>> I run into a problem that left me confused.
>> I wanted to use \_ to draw a line in a table.
>
> Can you check for trailing spaces? I get the underscore instead
> of a sequence of dashes if the cell contains more than just "\_".
> Or are you u
Hi list,
After printing my document i found that \_ does not do what i expected.
the line is to high more like - than _.
After reading the UTP book again i got the inpression that \$_ will do
what i want but that resulted in "bad argument name `_'"
Then i tried \R_ what is very near what i would
It is very nice,
but it look strange when you use:
\*_|\*_
I also changed from .1 to .3 (what looks in my context better).
re,
wh
Am 14.01.2011 10:44, schrieb Tadziu Hoffmann:
>
>> After printing my document i found that \_ does not do what i
>> expected. the line is to high more like - tha
This works fine but it is not a future proof solution :)
what takes me wonder is the question what went wrong with \$_ ?
and can some one make the \*_ solution more flexable so it will fill
the whole column automaticly ?
(i have changed the 6c every time this works for me but may be not for other
Am 14.01.2011 20:29, schrieb Tadziu Hoffmann:
>
>> This works fine but it is not a future proof solution :)
>
> Hmmm. Why not?
>
>
>> what takes me wonder is the question what went wrong with \$_ ?
>
> I don't know where the "\$_" comes from. It's not in the tbl
> manpage, nor in the origi
Hello List,
i have found an oddity with tbl and large fonts.
i got the request to make the fonts larger to inprove readability.
i added the \s16 and found that the width seems to scale but not
the hight of the table. Is this intended ?
mean while i will try to use the postscript scale operator to
Am 18.01.2011 20:02, schrieb Deri James:
> On Tuesday 18 Jan 2011 17:51:22 walter harms wrote:
>> Hello List,
>> i have found an oddity with tbl and large fonts.
>> i got the request to make the fonts larger to inprove readability.
>> i added the \s16 and found that t
Am 19.01.2011 16:34, schrieb Tadziu Hoffmann:
>
>>> .ps 16
>
>> I have tried but the result is not realy different. The
>> postscript files differ only in two lines. (i admit i have
>> no idea why). And that do not affect the box size.
>
> The important part was also changing the linespacing,
Hi list,
i have a programm that generate nroff output that is intended to be printed.
that works fine.
Problems occur when i want to see the page as latin1 then it will be rendered
into 2 pages. Since i pipe the output into xmessage i do not care about page
length.
Is there any fancy trick i can
Am 28.02.2011 20:58, schrieb Anton Shepelev:
> Walter Harms asked:
>
>> Is there any fancy trick i can use to convince
>> groff not to page break ?
>
> Yes. In addition to Clarke Echols's advice, you can
> make this behaviour more manageable using end-o
Am 01.03.2011 12:28, schrieb Ralph Corderoy:
> Hi Walter,
>
> Anton Shepelev wrote:
>> Walter Harms:
>>> thx for the hint, but how does setting the page lenght affect the
>>> printed output ? the main point is to print the document, showing
>>> it
Am 02.03.2011 10:53, schrieb Werner LEMBERG:
>> (NTL: it would be a nice extension for grotty to have a switch like
>> "papersize" )
>
> Uh, oh, a TTY has no length by its very definition. A physical paper
> size is completely meaningless for terminals, and the logical paper
> size is given by
Am 02.03.2011 11:38, schrieb Werner LEMBERG:
>
>> A switch that let grotty ignore a given page size inside a document.
>
> .rn pl pl-orig
> .de pl
> . pl-orig i
> ..
>
>> And the rationale is exactly what you said: paper sizes and screen
>> sizes do not mix properly; so it may be useful t
Am 02.03.2011 17:32, schrieb Anton Shepelev:
> Walter Harms
>
>> i have added .pl i and it works so far but now
>> i see ^h^h^h^h in front of my table. I can fix
>> that with "cut -b5-" or tr -d "\b" but i am con-
>> fused.
>> (i
The most easy way IMHO is to create a postscript file
and include that.
re,
wh
Am 08.08.2011 00:41, schrieb steve.gnuli...@gmail.com:
> Hi,
>
> Thanks everyone. Just i would to get the groff man's from some Gnu/Linux
> utilities and convert to a unified LaTex file. The purpose is as 'appendix'
Am 16.11.2011 09:43, schrieb Ingo Schwarze:
> Hi,
>
> do you hold any opinion on this one?
>
> Thanks,
> Ingo
>
> - Forwarded message from Ingo Schwarze -
>
> From: Ingo Schwarze
> Date: Tue, 1 Nov 2011 19:43:27 +0100
> To: groff@gnu.org
> Subject: [Groff] let man print volume hea
Am 16.11.2011 12:40, schrieb Ingo Schwarze:
> Hi Walter,
>
>> Basicly it seems ok for me, ntl some (non roff note).
>> * Sun Release 4.0Why ?
>
> That's a comment, and my patch doesn't touch it.
> I guess whoever put it there wanted to provide an example
> how the fourth argument might
Am 16.11.2011 15:38, schrieb walter harms:
>
>
> Am 16.11.2011 12:40, schrieb Ingo Schwarze:
>> Hi Walter,
>>
>>> Basicly it seems ok for me, ntl some (non roff note).
>>> * Sun Release 4.0Why ?
>>
>> That's a comment, and my
Am 11.03.2012 01:03, schrieb James K. Lowden:
> Like everyone else, I normally use nroff and man(1) to view manpages.
> Sometimes I whimsically use xman or tkman.
>
> It occurs to me that I'm using a bitmapped display on a 3,300 MHz
> processor with quite a few fonts installed. I could benefi
hi list,
i run into a problem that may be solved by others already.
I show a groff file as latin1, that worked fine. i had some ^H but that where
filtered by "tr"
no problem. But i added some boldface to the text and i got something like that
N^HNi^Hic^Hch^Hht^Ht.
No real surprise i know that "c
Am 24.07.2012 18:16, schrieb Denis M. Wilson:
> Hello all
>
> On Tue, 24 Jul 2012 16:50:09 +0200
> walter harms wrote:
>
>> hi list,
>> i run into a problem that may be solved by others already.
>>
>> I show a groff file as latin1, that worked fine. i ha
Am 26.07.2012 14:17, schrieb Werner LEMBERG:
Pass on options to grotty; the following removes all backspaces:
groff -ww -Tlatin1 -P-c -P-b -P-o -P-u
>>> Works fine for me. A nice extension for grotty would be a switch
>>> for pure/plain that disables all bold, underlines etc.
Hi list,
i found a minor issue within the man macros.
Most likely this is a know behaver but i found no mention of it.
As documented you can escape "\" by using "\\" or "\e\".
This went wrong in a man page. Please try the striped down example:
.TH test 3 test
.SH test
.B "\en"
.B "\\n"
with "man
Am 04.10.2012 15:41, schrieb Werner LEMBERG:
>
>> As documented you can escape "\" by using "\\" or "\e\".
>
> To which documentation are you referring?
Unix Text Processing p.377
i guess it is also mentioned in the man/info pages related to groff.
>
>> This went wrong in a man page. Please
Am 25.01.2013 00:52, schrieb Colin Watson:
> On Thu, Jan 24, 2013 at 11:54:43PM +0100, Bernd Warken wrote:
>> This mail goes to the Debian admins. I think that's mostly
>> Colin Watson.
>
> Exclusively me; I have no co-maintainers of the groff package at
> present. That said, the General Resolu
Am 01.02.2013 01:39, schrieb Bernd Warken:
> I have a man-page with a table that is 3 pages long. It works when
> I split it in 3 parts and call .TS/.TE for each.
>
> I would prefer to use hdtbl. You mention in groff_hdtbl(7) a
> macro that can go over several pages, but that works only in ms.
Could you write a short howto for that (e.g. using spanish as example) ?
That would be helpful for everyone adding a new language.
re
wh
Am 21.08.2014 01:50, schrieb Yves Cloutier:
> I have created hyphen.es and es.tmac and all seems to work!
>
> I exactly wasn't sure what I had to put in es.
78 matches
Mail list logo
