Re: Is there a Groff showcase?
On Do 07 Dez 2023 at 21:35, Mike <898...@smartsprout.co.uk> wrote: > I was thinking of a website or web page which demonstrates the extent > of groff's capabilities. > > If there isn't anything like this, currently. Has this been considered? > > I have only just learned of groff. The manual is awesome (though tough > reading for me in places). groff does so much more than I first > imagined. > > I don't know if this aligns with the goals of the contributors, but > examples of some well-designed, finished documents might attract new > users and potential contributors. > > Forgive me for being bold, I am just thinking out loud. > > Mike You might have a look at https://www.schaffter.ca/mom/ then. Iy is for a new macroset called mom from Peter Schaffter and it is very well documented and has some demostration documents with source. 'Andreas
Re: [groff] Brian Kernighan on the evoution of eqn, pic, grap, into troff
On Sa 05 Mai 2018 at 01:15, Tadziu Hoffmann wrote: > (BTW, most Germans who use it also pronounce it wrong, > namely as in "ich" instead of as in "Bach".) What do you mean by that? The sound of the 'ch' is the same in both cases. 'Andreas ( a german native speaker :-) )
Re: Bulleted list items without ms macros?
On Mo 08 Feb 2021 at 05:25, tu...@posteo.de wrote: > from the internet I downloaded a set of macro definitions > (tmac.letter) to produce letters in the german "DIN Brief" > format. Now that sounds interesting. Where did you find that? 'Andreas
Re: Bulleted list items without ms macros?
On Mi 10 Feb 2021 at 10:49, tu...@posteo.de wrote: > you can find it here: > https://lists.gnu.org/archive/html/groff/2010-09/msg00038.html > > ...it is not compatible with the ms-macroset (or any other macroset?). > You need troff "assembler" code to change things like font size etc. Thank you. That looks very interesting. I am still a roff beginner, slowly growing into it. My google-fu was not good enough to unearth that. 'Andreas
problem with mm macros
Hello, I'm a newcomer to roff and have just begun reading the book 'UNIX Document Processing and Typesetting'. There is an example of a letter in there thay I enclose here, necause it shows the poblem: .ND "January 1, 1999" .AU "Dr. Gray Hound" .AT "Project Leader" .MT 5 .DS Our Reference: prog/001 Your Reference: xyz/100 .SP 4 Mr. William Smith Chief Advisor Consult the Consultants Penny House Graceland .DE .SP 3 Dear Mr. Smith .SP 2 .ce Recruitment of a Programmer .fi .SP 2 .P With reference to our discussion over lunch at the West Gate Club, the requirements of the programmer are as follows: .P The programmer should be conversant in all computer programming languages and be ready to develop any kind of software using different computers. The programmer must also be willing to do administrative and paperwork to get his/her pay. .P Although the requirements may seem to be unusual, I am sure that with your company's expertise in head hunting, finding a suitable person for the above-mentioned position will be a trivial matter. .P Hope to hear from you soon. .FC Sincerely yours .SG Now the problem is that groff doesn't show the author's title below the author's name. Both heirloom and neatroff do, so it is maybe a bug in groff? Also both heirloom and neatroff show name and tile in bold, whereas groff only shows the name an does not do so in bold. Maybe someone with more experience in roff can explain what goes wrong. Sincerly, Andreas Eder
Re: problem with mm macros
On Do 25 Feb 2021 at 10:40, Mike Bianchi wrote: > Andreas has found a true bug. The .AT macro does not act as advertised in > groff_mm ... > The title _does_not_ show up after the name in the signature block. > > Search /usr/share/groff/1.22.2/tmac/m.tmac (the copy I am using at present) > fgrep 'cov*at!' /usr/share/groff/1.22.2/tmac/m.tmac > and I find > .\" author(s) title stored in cov*at!x!y > . ds cov*at!\\n[cov*au]!\\n[cov*i] "\\$[\\n[cov*i]] > > which shows that cov*at!N!N is created as cov*at!1!1 > but never referenced. I think I have found another instance of that problem. If you specify the author's firm with .AF it gets stored away in cov*firm but it is not referenced or used anywhere except 0.MT, 4.MT and ms.cov. Try the following test: .TL Merger Technical Specifications .AF "ABC Corporation" .AU "Christopher Craft" .AT "President" .AS This memo details the specifications for the planned merger. .AE .MT "Merger Description and Marching Orders" As a result of our talks with XYZ corporation, we plan to go forward with the merger. This document contains the following: .BL .LI Schedule and time tables. .LI Financial statements. .LI Asset allocations. .LE .SP Please add any corrections you have, then sign the approval line indicated at the bottom of this sheet. .FC .SG .AV "John W. Doe, XYZ Corporation President" .AV "Sylvia Q. Public, XYZ Corporation CFO" .NS Everyone in the corporation. .NE It should show up in the right top of the page - or at least that is what neatroff does. Sincerely, Andreas
Re: problem with mm macros
On Do 25 Feb 2021 at 10:40, Mike Bianchi wrote: > Andreas has found a true bug. The .AT macro does not act as advertised in > groff_mm ... > The title _does_not_ show up after the name in the signature block. > > Search /usr/share/groff/1.22.2/tmac/m.tmac (the copy I am using at present) > fgrep 'cov*at!' /usr/share/groff/1.22.2/tmac/m.tmac > and I find > .\" author(s) title stored in cov*at!x!y > . ds cov*at!\\n[cov*au]!\\n[cov*i] "\\$[\\n[cov*i]] > > which shows that cov*at!N!N is created as cov*at!1!1 > but never referenced. > I think I have found the place where the title should be added: it is very probably in the let*mt-sign macro which is defined in m.tmac at line 3298. That is the place where the authors are printed. Unfortunately my roff fu is still much too weak to attempt a fix. Sincerely Andreas
Re: problem with mm macros
On Fr 26 Feb 2021 at 08:48, Robert Goulding wrote: > Actually, I now see that documents headed with .LT don't use .AU etc., but > .WA. And for the most part it works. > > But there is still a bug, with one of the four types of letters. > > Try this: > > .LT SP > .WA "John Doe" > Nowhere, > USA. > .WE > .IA "Jane Smith" > Somewhere, > UK. > .IE > .LO SJ "Letter of Introduction" > .LO SA "Dear Ms Smith" > .P > This is the text of the letter. > .FC "Yours sincerely" > .SG > > You'll find that: The subject line shows only the first word; the formal > closing is omitted completely; and the writer's name at the bottom is > followed by a trailing comma. > > If you change the first line to > .LT BL > > or one of the other types, everything is printed correctly. It seems, I have opened a can of worms here :-) Andreas
Re: problem with mm macros
On Mo 15 Mär 2021 at 06:38, Dave Kemper wrote: > On 2/25/21, Andreas Eder wrote: >> Now the problem is that groff doesn't show the author's title below the >> author's name. Both heirloom and neatroff do, so it is maybe a bug in >> groff? > > Andreas, > > Does this seem to you to be the same as the problem reported in > http://savannah.gnu.org/bugs/index.php?57034 ? Hello Dave, Yes, this seems to be the same problem. The only difference is that I didn't try nroff but groff, since I am only interested in that output format. Thank you for looking into it. Andreas -- ceterum censeo redmondinem esse delendam
Re: problem with mm macros
On Mo 15 Mär 2021 at 17:45, Tadziu Hoffmann
wrote:
> This can be fixed quickly by adding, below the line that
> prints the author's name,
>
> \\*[cov*au!\\n[let*i]!1]
>
> the following lines:
>
> .nr let*j 0 1
> .while !'\\*[cov*at!\\n[let*i]!\\n+[let*j]]'' \{\
> \\*[cov*at!\\n[let*i]!\\n[let*j]]
> .\}
>
> Since the number of titles for each author is not stored anywhere,
> this assumes that an empty value signals the end of the author's
> titles, i.e., there can be no empty author's titles (but \& works).
Thank you for fixing this, It works.
The only difference to either heirloom or neateqn output is that both
name and title are not in bold.
Wether this is impostant or not os a dofferent question.
Andreas
Re: problem with mm macros
On Mo 15 Mär 2021 at 15:00, Dave Kemper wrote: > Andreas and Robert, are the other issues you noted in this thread > manifestations of the same problem, or separate problems? I'm not at > all an mm user so don't know the expected behavior, but from the > descriptions, it sounds like at least the .LT problem Robert reported > is something different. Yes, the .LT problem is something different and the problem with .AF also. Andreas
