[MOM[ unexpected behaviour when using blockquotes with two columns
Dear all, I'm preparing an article using mom with a two column layout. When a blockquote continues on the right column it makes an extra indent. See the attached files. I don't know how to fix this. Kind regards, Hans Blockquote.groff Description: Binary data Makefile Description: Binary data Blockquote.pdf Description: Adobe PDF document
Re: [MOM[ unexpected behaviour when using blockquotes with two columns
Dear Peter, Thanks for the fast reply. It worked! Two small remarks: 1. The current release link redirects to the older version: https://www.schaffter.ca/mom/mom-2.6.tar.gz 2. In groff_mom there's a link to the local html manual (/usr/share/doc/groff-1.23.0/html/mom/toc.html), but most recent version of Groff on Arch Linux doesn't include the html pages, at least not where the points to. Kind regards, Hans > > Op ,Thu Nov 16 2023 06:25:17 GMT+0100 (Central European Standard Time), > schreef Peter Schaffter : -- Oorspronkelijk > bericht -- > > On Wed, Nov 15, 2023, hbeze...@kliksafe.nl via wrote: > > I'm preparing an > article using mom with a two column layout. When > > a blockquote continues > on the right column it makes an extra > > indent. > > I've fixed the bug and > pushed the changes to the git repo. You can > download a tarball of the > fixed version (2.6_a) from the mom website: > > > https://www.schaffter.ca/mom/mom-05.html#most-recent-release > > -- > Peter > Schaffter > https://www.schaffter.ca > > >
Use of sed in PDFPIC macro with OpenBSD
Dear members, I've switched to OpenBSD recently and noticed unexpected behaviour of the PDFPIC macro: There's no vertical space reserved. The culprit seems to be the use of '\n' in the line where sed is used (line 89): . sy pdfinfo @$1 | \ grep "Page *size" | \ sed -e 's/Page *size: *\\([[:digit:].]*\\) *x *\\([[:digit:].]*\\).*$/\ .nr pdf-wid (p;\\1)\\n\ .nr pdf-ht (p;\\2)/' \ > /tmp/pdfpic\n[$$] This results in a single line in /tmp/pdfpic\n[$$]: .nr pdf-wid (p;\\)n.nr pdf-ht (p;\\2) and therefor only pdf-wid gets set. >From what I understand is that posix sed requires a real linebreak in the sed >command to create a linebreak, but I assume that '.sy' sends all output >without any linebreaks. I've noticed a suggestion in the "Problems with .PDFPIC caused by pdfinfo" thread to use awk instead of sed. I'm not familiar enough with sed or awk to give a one line fix, but I'll be happy to open a bug report for this. But before doing so, I would like to get some advice. Thanks in advance. Kind regards, Hans
Re: Use of sed in PDFPIC macro with OpenBSD
I'll post the patch in the bug report.
Hans
>
>
>
>
>
> Op Wed Dec 08 2021 22:34:24 GMT+0100 (Central European Standard Time)
> schreef Dave Kemper :
>
> -- Oorspronkelijk bericht --
>
>
>
>
>
> On 12/7/21, Hans Bezemer wrote:
> > Changed the
> appropriate lines into:
> > . sy pdfinfo @$1 | \
> > awk '/^Page size:/
> {print ".nr pdf-wid (p;"$3")"; \
> > print ".nr pdf-ht (p;"$5")"}' \
> >>
> /tmp/pdfpic\n[$$]
> >
> > This seems to work fine.
> > I've attached a patch
> file.
>
> If this is portable (I don't know awk at all), it would also fix
> bug
> #58206 (http://savannah.gnu.org/bugs/?58206), since it eliminates the
> grep that is causing that problem. Might be worth posting your patch
> in
> that bug report.
>
>
>
Setting up repository for user macrosets
Dear all, For a while I've been thinking of creating a github public repository with user macrosets for groff. Per macroset I could make a folder containing the macroset, a snippet / example and a README(.md) file with some background on the macroset and a info on how to use the macroset and how to build the snippet. Macrosets could either be extensions on the mm, ms, mom macrosets (or others) or standalone macrosets. I think it could be helpful for other users to be able to see if a specific macroset is available before writing one on their own. Personally I find it inspiring to see what others have come up with to solve a specific problem. I can check if the macrosets produces the expected output before pushing to the repo. Would that be a good idea? Kind regards, Hans
Re: Setting up repository for user macrosets
Thanks for the replies so far. I'll setup a repo this week and add as much as possible. Feel free to add more. Kind regards, Hans > > > > > > Op Mon May 30 2022 18:40:17 GMT+0200 (Central European Summer Time) > schreef Thomas Dupond : > > -- Oorspronkelijk bericht -- > > > > > > "hbeze...@kliksafe.nl" via wrote: > > > Dear all, > > > > For a > while I've been thinking of creating a github public repository > > with > user macrosets for groff. > > > > Per macroset I could make a folder > containing the macroset, a snippet > > / example and a README(.md) file with > some background on the macroset > > and a info on how to use the macroset > and how to build the snippet. > > I maintain a list of useful groff tricks at > https://froude.eu/groff and > you can find a handful of macrosets here: > https://froude.eu/groff/examples/macro-sets.html > > You should add them to > your repository! > > > Macrosets could either be extensions on the mm, ms, > mom macrosets (or > > others) or standalone macrosets. > > > > I think it could > be helpful for other users to be able to see if a > > specific macroset is > available before writing one on their own. > > > > Personally I find it > inspiring to see what others have come up with to > > solve a specific > problem. > > > > I can check if the macrosets produces the expected output > before > > pushing to the repo. > > > > Would that be a good idea? > > > > Kind > regards, > > > > Hans > > -- > Regards, > Thomas > >
Re: Setting up repository for user macrosets
The repo is created: https://github.com/Allfifthstuning/awesome-groff-user-macrosets.git Although still empty I'll add macrosets slowly but steady. Hans > > > > > > Op Mon May 30 2022 19:36:58 GMT+0200 (Central European Summer Time) > schreef hbeze...@kliksafe.nl via : > > -- Oorspronkelijk bericht -- > > > > > > Thanks for the replies so far. > > I'll setup a repo this week and add as > much as possible. > > Feel free to add more. > > Kind regards, > > Hans > > > > > > > > > > > > > Op Mon May 30 2022 18:40:17 GMT+0200 (Central European Summer Time) > > > schreef Thomas Dupond : > > > > -- Oorspronkelijk > bericht -- > > > > > > > > > > > > "hbeze...@kliksafe.nl" via > wrote: > > > > > Dear all, > > > > > > For a > > while I've been > thinking of creating a github public repository > > > with > > user macrosets > for groff. > > > > > > Per macroset I could make a folder > > containing the > macroset, a snippet > > > / example and a README(.md) file with > > some > background on the macroset > > > and a info on how to use the macroset > > and > how to build the snippet. > > > > I maintain a list of useful groff tricks at > > https://froude.eu/groff and > > you can find a handful of macrosets here: > > https://froude.eu/groff/examples/macro-sets.html > > > > You should add > them to > > your repository! > > > > > Macrosets could either be extensions on > the mm, ms, > > mom macrosets (or > > > others) or standalone macrosets. > > > > > > I think it could > > be helpful for other users to be able to see if a > > > > specific macroset is > > available before writing one on their own. > > > > > > > Personally I find it > > inspiring to see what others have come up with to > > > solve a specific > > problem. > > > > > > I can check if the macrosets > produces the expected output > > before > > > pushing to the repo. > > > > > > > Would that be a good idea? > > > > > > Kind > > regards, > > > > > > Hans > > > > -- > > Regards, > > Thomas > > > > > >
Re: APA Format
With the tar attached this time. Hans > > > > > > Op Mon Oct 10 2022 20:17:23 GMT+0200 (Central European Summer Time) > schreef : > > -- Oorspronkelijk bericht -- > > > > > > Hi Aaron, > > Refer doesn't support APA-style referencing out of the box. > IMHO there's a need for some macrosets which would allow APA or > Chigaco-style > referencing along with groff_ms (7) and groff_mm (7) macro > packages. > > I've gave it a try a while ago. > If you put all the attached > files in the same folder and create a `build' > subfolder, you should get a > very simple (and far from perfect!) example, when > running make. > > The > apa.tmac macro package uses awk (1) to create the right format for the > authors. > Also I use '%t' to tell apa.tmac if the entry is a book or > article. > Per type you can create the right formatting. > > As said it is far > from perfect, so maybe more experienced users could give advise > on what > would be the best way to move from here. > > Cheers, > > Hans > ~@ > ~/Documents/Groff/ReferTest/ApaGroff.tar > > Ralph Corderoy > wrote: > > > Hi Aaron, > > > > > refer -PS -e -p > ./references.ref arb.tr | groff -ms -T pdf > output.pdf > > > > > > The > references seem "close" to APA format but there are still issues > > > with > the formatting. > > > > Here's what I have from what you've said so far. > > > > > $ cat references.ref > > %K congress108-narcoterrorism > > %Q ONE > HUNDRED EIGHTH CONGRESS > > %T "NARCO-TERRORISM: INTERNATIONAL DRUG > TRAFFICKING AND TERRORISM--A DANGEROUS MIX" > > %O > https://www.govinfo.gov/\%content/\%pkg/CHRG-108shrg90052/\%html/CHRG-108shrg90052.htm > > %D May 20, 2003 > > %L Senate Hearing > > $ > > $ cat arb.tr > > > .na > > The drug > > .[ > > congress108-narcoterrorism > > .] > > > hearing. > > $ > > $ refer -PS -e -p references.ref arb.tr | nroff -ms > -Tutf8 | cat -s > > > > The drug (ONE HUNDRED EIGHTH CONGRESS, 2003) > hearing. > > > > References > > > > ONE HUNDRED EIGHTH CONGRESS, 2003. > > > ONE HUNDRED EIGHTH CONGRESS, "NARCO‐TERRORISM: INTERNA‐ > > TIONAL DRUG > TRAFFICKING AND TERRORISM‐‐A DANGEROUS MIX" > > (May 20, 2003). > https://www.govinfo.gov/content/‐ > > > pkg/CHRG‐108shrg90052/html/CHRG‐108shrg90052.htm. > > > > $ > > > > It would > if you could detail how the above differs from what you'd like > > as APA's > style could be unknown to many of us on the list. > > > > -- > > Cheers, > Ralph. > > > ApaGroff.tar Description: Unix tar archive
