The README file in the top groff source directory has some errors. The
following patch fixes these.
## patch for /README
--- README.orig 2004-11-16 13:48:49.0 +0100
+++ README 2005-05-20 18:24:45.429739616 +0200
@@ -34,6 +34,7 @@
An update of a checked out repository shou
ad snapshots (which are updated twice a
day) from
### end of patch
Bernd Warken
__
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
smime.p7s
Description: S/MIME
stead.
The existence of the file README.CVS forces that all CVS information in README
should go to README.CVS.
This email contains two patch files with the corresponding changements for
README and README.CVS as attachment.
Bernd Warken
__
Mit W
removed.
Bernd Warken
__
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
README
Description: Binary data
smime.p7s
Description: S/MIME Cryptographic Signature
The file /doc/fdl.texi contains the old version 1.1 of the FDL.
The actual version 1.2 can be get from
http://www.fsf.org/licensing/licenses/fdl.texi
Bernd Warken
__
Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min.
weltweit
hem to GPL?
Bernd Warken
__
Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min.
weltweit telefonieren! http://freephone.web.de/?mc=021201
___
Groff mailing list
Groff@gnu.org
http://lis
TF-8)
T=-Tutf8 ;;
- iso_8859_1 | *.ISO-8859-1 | *.ISO8859-1)
+ iso_8859_1 | *.ISO-8859-1 | *.ISO8859-1 | \
+ iso_8859_15 | *.ISO-8859-15 | *.ISO8859-15)
T=-Tlatin1 ;;
*.IBM-1047)
T=-Tcp1047 ;;
####
mmercial UNIX systems. If you want to have a free shell
standard you could look at
http://www.funet.fi/pub/doc/posix/p1003.2/d11.2/all
POSIX itself is not free as well, but this paper was a pre-release draft that
was openly published and is still freely available. I built groffer around
th
`false' is part of POSIX. That should be enough. You cannot use the
original Bourne style for much; it does not even have shell functions.
Bernd Warken
__
Verschicken Sie rom
In /src/devices/xditview, the Imakefile was replaced by a
Makefile. But the directory is not called by `make'. If one adds this
directory to /Makefile, only the man page is installed.
`gxditview' is not even generated.
Be
;.
The X* devices make also trouble. -TX75, -TX100, -TX75-12, and TX100-12 each
produce an error with the CVS groff, but the system groff 1.18.1 is ok. `groff
-TX100' generates the error:
groff: can't find `DESC' file
groff:fatal error: invalid device `X100'
Bernd War
on the other hand, is different and avoids the error.
That seems curious to me. `-X' is said to produce PS output, while `-Z'
generates just the intermediate output. So `-Z' should look more like `-TX*'
than `
in the gxditview viewer, but not as a text output.
Either -Z must be changed to produce again the good intermediate output without
the bad ps part or a whole lot of documentation must be changed.
Bernd Warken
_
Mit der G
image files could be complicated.
A better method might be to find a possibility to include the picture source
directly into the html output. But I do not have any idea on this.
I fixed `groffer' to always work by changing to the tempor
, unnecessary errors; these
are avoided by adding `2>/dev/null' and `|| :'.
Bernd Warken
__
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail:
As the mail program trashed the patches I include 3 files with purer patches in
the appendix.
Bernd Warken
__
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
$(INSTALL_SCRIPT) groffer $(bindir)/groffer
- $(INSTALL_SCRIPT) groffer2.sh $(libdir)/groff/groffer/groffer2.sh
+ $(INSTALL_SCRIPT) $(srcdir)/groffer2.sh \
+ $(libdir)/groff/groffer/groffer2.sh
Does it hurt if $(srcdir) is also added to `grof
.URL and .MTO use the color blue. But if colors are not active they print in
the normal font. This is not impressive.
The appended patch uses the bold font instead of blue.
Bernd Warken
__
Verschicken Sie romantische, coole und
Another patch for www.tmac. In now handles .URL and .MTO in case \\$1 is
empty. The empty <> is now omitted, just like html mode does.
The patch is appended in the file www.tmac.patch2.
Bernd Warken
_
Mit der G
ssibility to change `groff' such that it is not necessary to
redefine .TS and .TE?
Bernd Warken
__
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!
Jetzt gratis t
goes around a table in a
nice way. Maybe you could use your redefinitions in the original definitions.
I hope that I understood that right.
Bernd Warken
__
Erweitern Sie FreeMail zu einem noch leistungsstarkeren E-Mail-Postfa
Jon Snader <[EMAIL PROTECTED]> schrieb am 23.08.05 23:40:11:
>
> Perhaps a different
> macro, or a new argument to .TS to invoke the behavior is what we
> want.
That's a good idea.
Bernd Warken
__
le
for viewing in a PDF viewer. All needed `groff' options are determined and
performed automatically. If you want to see the Postscript source without a
viewer use
groffer --ps --source file_or_man_page
`groffer' is part of
With dwww you can view info files, man pages, and other documentation with a
web browser. The needed html is generated on-the-fly. Even links are created
such that you can view other man pages by clicking in a man page.
Bernd Warken
___
There is a wiki page with an article on groff:
http://en.wikipedia.org/wiki/Groff.
It is quite small. The German version
http://de.wikipedia.org/wiki/Groff
is different and much larger. Strangely enough, it comments `lbl' as supported
preprocessor.
Bernd W
d.
>
The cited original lbl shar archive is available at
ftp://ftp.uu.net/usenet/comp.sources.unix/volume6/lbl.Z
This file is the compressed version of lbl.shar in the tar file.
The site
http://www.rocketaware.com/hard/print/
shows to this l
tical as well. So the best way might be to
replace c+ or c\{1,\} by cc*
sed -e 's/^.* \([^ ][^ ]*\)$/\1/' -e '1q'
Bernd Warken
__
Verschicken Sie romantische, coole und witzige Bilder
> Von: Clarke Echols <[EMAIL PROTECTED]>
> Besides, it didn't put one cent in Bill Gates and company's pocket.
> I'm too cheap to spend big bucks just to get PowerPoint. I haven't
> checked, but perhaps there's some equivalent now available for Linux
> or Cygwin?
OpenOffice Impress can handle Po
release of "etch" since this outcome
results in the need for many developers to check documentation for unmodifiable
parts. However, much documentation may be kept in the main Debian archive even
if it is licensed under the GN
; mode has the advantage that there are some
good viewers and that it is possible to search within a
pdf file.
Good luck
Bernd Warken
__
Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach!
le line even in ps or dvi output. But as soon as you add a line that is
empty or has only spaces or a comment a whole empty page is created
in ps or dvi mode.
Bernd Warken
___
Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, onl
version because it is still in the alpha state.
Bernd Warken
__
Erweitern Sie FreeMail zu einem noch leistungsstärkeren E-Mail-Postfach!
Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131
ibution or
/src/preproc/chem because `chem' is a `pic'
preprocessor.
Bernd Warken
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
/automake? Then it just has to be regenerated.
Bernd Warken
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
with handling long [...] block constructs. Maybe someone can help me
to fix this.
The easiest way to handle chem is with groffer:
chem example | groffer
will display the example in pdf mode.
Enjoy
Bernd Warken
___
Groff mailing list
Groff@gnu.org
task to handle this output.
2) `grog' exits with an error, but no error message is written.
3) `grog' exits with an error, and an error message is written.
In each case, I can provide a patch. Please tell me which method you prefer.
Bernd Warken
__
grog with your roff files. I could not test
mm files. But the testing of ms was very weak, too.
A problem occurs if grog tests 2 or more macro packages for a
single file. This has to be tested.
Bernd Warken
___
Groff mailing list
Groff@gnu.org
runtest; \
else \
echo "WARNING: could not find \`runtest'" 1>&2; \
fi
WARNING: could not find `runtest'
###
So runtest is lacking. I do not know where to get it.
Bernd Warken
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
o provide
PostScript output for the `groff' example files because everyone can easily
generate these files. A suitable README file could be written.
Bernd Warken
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
ust want a quick peruse without the overhead of building, etc.
If they can use PostScript they must have a working computer. Moreover,
the ps-files in the examples are very disgusting. They hide the roff source
code; a ps-subdirectory would do. Maybe `html' w
. Another
> option is to merge the functionality, making pdfroff a symlink to
> roff2pdf.
You are right. I will change groffer to do this. But actually I do not
have time for it. It will take several weeks.
Bernd Warken
___
Groff
r cannot detect the comment sign \" or is not
able to
handle long variable names.
`doclifter' should be fixed to handle this correctly. I cannot detect any
necessity for a
"safe" list. I will not fall back to the old scheme of 2 letter variable names.
Bernd Warken
__
e fixed and removed from the secure list. Perhaps the remaining
troubles could be fixed as well by the time. Laziness should not prevent
this.
Good luck
Bernd Warken
___
Groff mailing list
Groff@gnu.org
http://lists.gnu.org/mailman/listinfo/groff
+This makes it possible to have eight different background
> +foreground colors; additionally, bold and italic
> attributes can be used \f[BI]at the same time\f[] (by using the BI font).
The word `and' seems to be lost.
Bernd Warken
; is removed and the file
is installated as `.[157]'.
### old-fashion concept
A similar concept with `.[157]n' was proposed and discussed in october
2014. As this concept is not as suitable, I do not propose this old proposal
again.
Bernd Warken
.
Unfortunately I do not have time during the next week or longer.
So I would be very glad, if someone could help and fix this bug,
maybe in top-source/Makefile.am.
Bernd Warken
. Help?
> > So I would be very glad, if someone could help and fix this bug,
> > maybe in top-source/Makefile.am.
Please help me for that as well. Thanx
Bernd Warken
get the final section number.
Bernd Warken
Thanx for the answers of my questions.
> Von: "Bertrand Garrigues"
> I used the Automake variables man1_MANS, man5_MANS, man7_MANS to define
> the list of man files to be installed in sections 1, 5, and 7.
>
> This is described here:
>
> https://www.gnu.org/software/automake/manual/automake.
I just published the renaming of man-pages including the section number, e.g.
groffer.man -> groffer.1.man
groffer.1.man is then transferred into groffer.n, which is installed as
groffer.1.
Make install, uninstall, clean, and distclean work as they should.
Please test.
Bernd Warken
please test? If it's OK on your side I'll commit this change.
Your patch is ingeneous, thanx. With that it will be possible to have
groff.1.man and groff.7.man on the same directory.
Please install it. But as I'm working today (Thursday) at several GIT
updates, please wait with the install to tomorrow (Friday).
Bernd Warken
glilypond,
but not yet today.
The macro was written by Peter Schaffter in 2014. So the license should
be added by the author, as well as the documentation in the man-page
man/groff_tmac.5.man should be improved..
Bernd Warken
offer --ps --ps-viewer=gv ...
By the command "groffer ..." without options, it is converted to
pdf, the better PostScript.
Bernd Warken
offer command worked without problems. The temporary
file was not deleted. even wtih several evince programs running.
Maybe your evince version is buggy.
Bernd Warken
nce would make
more sense.
Bernd Warken
short time ago.
Bernd Warken
an
Please tell me if I missed something.
Bernd Warken
groff-filenames.7
Since the evolution of roff in the 1970s, a whole bunch of file name
exte
"groff/man/groff-filenames.man".
Please tell me if I missed something.
Bernd Warken
groff-filenames.7
Since the evolution of roff in the 197
are also used by BSD without groff. Moreover it would be nice to
add the extensions to the Emacs nroff-mode.
Meanwhile groff-filenames.man is ready. I can publish it. I think this
man-page does not do any harm. But a lacking documentation is a weakness.
Imagine what would happen in Linux systems without the FHS.
I could also use this documentation as part of groffer. Reliable filename
extensions would be very nice for grog and groffer.
Bernd Warken
necessary.
Bernd Warken
groff_filenames.man
Description: Unix manual page
in the FDL.
So which license should we prefer for documentation files:
- make all documentation files into GPL
- make all documentation files into FDL
- keep the licenses of all files as they are
In any case, the file LICENSES has to be updated accordingly.
Bernd Warken
ses will come later on.
> > In any case, the file LICENSES has to be updated accordingly.
>
> Patches are welcomed :-)
First we should be clear about what has to be changed. When we use
FDL, that should be documented in the LICENSES file.
Bernd Warken
This mail goes to the Debian admins. I think that's mostly
Colin Watson.
> Von: "Bernd Warken"
>
> The groff source tree is usually licensed to GPL. That is excellent.
>
> But there are also some documents under the GNU FDL. This is regarded
> as bad by Deb
So the copyright is loaded at the end by calling these macros. That
means that the copyright at the beginning and at the end are guaranteed
to be the same.
Moreover the macro definition is not "ignored" by using .ig.
It seems necessary to have the leading .TH and .SH at the top before the
"Legalese".
I will comment the license for other files later on.
Bernd Warken
> Von: "James K. Lowden"
>
> On Thu, 24 Jan 2013 16:42:05 +0100 (CET)
> "Bernd Warken" wrote:
>
> > So which license should we prefer for documentation files:
> > - make all documentation files into GPL
> > - make all documentation files
names. So the weak
commercial roff programs should see where they are. Forget about them.
Bernd Warken
> Von: "Ralph Corderoy"
>
> > I will move all man-pages where I'm among the authors from FDL to GPL.
>
> Out of curiousity, can you do that without the other authors' explicit
> agreement?
>
> Cheers, Ralph.
Of course I will ask them privately.
Bernd Warken
27;)
> to check how they resolve this issue.
>
>
> Werner
>
>
> PS: I'll write to Karl Berry for clarification too.
I wrote to licens...@fsf.org
`coreutils' uses FDL.
Bernd Warken
.FONT CB file. CI extension . R .
This is
\f[CB]file.\f[]\f[CI]extension\f[]\f[R].\f[]
The .FONT macro is much more readable.
Maybe we could rename .FONT or .FT and add it to the man macros in an-old.tmac.
We could even extend .ft, but I do not know how to do this.
Bernd Warken
> Von: "Ingo Schwarze"
>
> Hi Bernd,
>
> Bernd Warken wrote on Fri, Jan 25, 2013 at 05:17:07PM +0100:
>
> > I will move all man-pages where I'm among the authors from FDL to GPL.
> >
> > Next I will transform all GPL man-pages into the follo
> Von: "Ingo Schwarze"
>
> Bernd Warken wrote on Sat, Jan 26, 2013 at 03:44:55PM +0100:
>
> [...]
> > Examples:
> > .FONT I text1 R text2 I text3 R text4
> > is equivalent to .IR text1 text2 text3 text4
>
> I don't particularly like the id
conservative here, more or less. If at all, this
> could be added to `an-ext.tmac', but extending the man page stuff is
> low-priority. Fixing bugs in me, mm, and ms is certainly more
> important.
an-ext.tmac would be fine.
Bernd Warken
? If possible
the header should also be written at each new page.
Bernd Warken
> Von: "walter harms"
>
> 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
:
$ { echo '.mso 'hdtbl.tmac; cat; } | sed -e 's/^[ \t]*//' | groffer -
This command waits for input, which you can provide by
marking and copying an example with the mouse.
I like hdtbl, but some more examples would be nice.
Bernd Warken
s it right:
|| |
+1*2-+-2+3*2-+
|
Bernd Warken
.
Using `groff -man -mhdtbl ...' leads to errors, even without any output.
2 `-m' parameters seem to be illegal.
> > Surely this isn't correct? Why would `-mhdtbl', on the command line,
> > not be equally effective?
>
> It would, of course. Can you provide a better formulation?
grog must be adapted.
Bernd Warken
> Von: "Tadziu Hoffmann"
>
> A good starting point are the tutorial examples in the
> old Bell Labs Computing Science Technical Report #54
> (http://cm.bell-labs.com/cm/cs/cstr/54.ps.gz).
The 54.ps.gz are broken all over the internet. But
http://troff.org/54.pdf
works.
Bernd Warken
>From troff.org:
IDEAL User's Manual. CSTR #103, C. J. Van Wyk, Bell Labs, December 1981.
http://cm.bell-labs.com/cm/cs/cstr/103.ps.gz
103.ps.gz is broken, beginning at page 5. Does anyone have another
format or knows about that?
Bernd Warken
ion, that hdtbl's .TH is overwritten by man, which doesn't
> matter hdtbl because .TH is more optional and one can do the same with
> .TD.
It does not work for my man-page.
> -- But why using man and hdtbl together?
>
I have a man-page about historical stuff. This also has a table with
5 pages.
Bernd Warken
uld do that for the other cstr ps-files
that document classical troff. Then we could use troff.org in
the groff man-pages. One cannot expect that everyone uses gs or
ps2pdf.
If it is not possible to do that, I propose to use github.com.
I'm about to create a git page about RUNOFF.
Bernd Warken
,
but also a lot of other ps-files.
Is it posssible to store the generated pdf-files under troff.org?
That would be the best place. If there will be a good position
under troff.org we would use the addresses in the groff documentation.
Bernd Warken
a British university.
Bernd Warken
ailinglist to add Lilypond
into groff:
###
[Groff] lilypond sections in groff
From: Bernd Warken
Subject:[Groff] lilypond sections in groff
Date: Mon, 12 Feb 2001 21:08:56 +0100
User-agent: Mutt/1.2.5i
Would it be hard to implement musical scores written in Lily
don't
draw the image.
So .PSPIC seems to be broken for almost all modes.
I tried to read the pspic.tmac file, but it is quite complicated.
Bernd Warken
PS: How did I get the EPS-file?
With lilypond. I used a lilypond file test.ly with the content:
## test.ly
\version "2.14.2&
> Von: Tethys
>
> "Bernd Warken" writes:
>
> >.PSPIC is documented in groff_tmac(5). It is supposed to load an EPS-file.
> >That should work in the troff modes. In tty-modes and in X-mode it is not
> >possible to show the EPS-file, so only a box wit
ld be nice. But I could not
use convert to transform between different formats.
Which options do you use?
Bernd Warken
> how little music is produced. You could try:-
>
> groff -T ps -dpaper=a3 -P-pa3 t.trf
That worked also for me, but I do not understand it completely.
Thank you
Bernd Warken
nd in `groff/contrib/lilypond'. They will not be installed
so far, but can be used from the sourcei directory.
Could you please test the files and help to complete the project which is so
far almost experimental.
Bernd Warken
/fonts/otf/emmentaler-11.otf)
> concatstrings
> (r)
> file
> .loadfont
> %%EndResource
>
> A nice side effect is that the EPS files become much smaller, but of
> course they are no longer self-contained. Again, grops understands
> this just fine, but you *must* use G
works only in groff pdf and dvi mode, not in ps.
Tty, X and html mode have errors and display only a rectangle with the
file name.
To fix that is beyond my knowledge.
I could write the groff_lilypond program only by the knowledge that many
of you gave per email. I thank you very much.
Bernd Warken
> Von: "Deri James"
>
> It may be a mis-type (ps <-> pdf). .PSPIC is definitely not supported by
> gropdf, but is by grops.
You are right, `groff -Tpdf' does not work. But I used `groffer' which still
generates a ps-file and converts it by `gs' or `ps2pdf' into `pdf'. And that
works. So there
{
c' e' g' e'
}
.lilypond stop
qwer
.lilypond start
\version "2.14.2"
{
d' fes' gis' ees'
}
.lilypond stop
861
# end
I do not understand why you do not have any problems.
Bernd Warken
> Von: "Werner LEMBERG"
>
> PS: Bernd, you should definitely have a look how lilypond-book works.
> For example, it adds a default preamble and postamble to the
> temporary .ly files so that the snippets can stay very small. It
> also uses hash sums of the snippets to avoid unnecessa
be given in the command line, including `-'
and `--'.
Bernd Warken
to better Perl style. The handling of temporary
files and directories must still be changed for security reasons.
Bernd Warken
ve you thought about adding a groff mode to lilypond-book?
No, not yet. Maybe that's not my job. I do not want to learn Python
for doing this. Our job should be to make .PSPIC work for all kinds
of groff output, not only for dvi.
Bernd Warken
should be a graphic
output instead.
I will provide more details after the next version of glilypond is
published.
Bernd Warken
For the next `glilypond' version, I need to add something to the file
/Makefile.in
I know that `automake' replaces this file, but I did not find any
`Makefile.am' that is usually used by `automake'.
So can I change the `Makefile.in' file without problems?
Bernd Warken
hub.com:RUNOFF/groffer.git
$ git clone g...@github.com:RUNOFF/RUNOFF.git
Bernd Warken
1 - 100 of 253 matches
Mail list logo
