Re: [bug #57218] [PATCH] Reproducible builds support is broken and embeds timezone

Hu-hu! Ingo Schwarze wrote in <20201022-173721.sv97361.91...@savannah.gnu.org>: |Follow-up Comment #4, bug #57218 (project groff): | |I think groff should not write %%CreationDate into PostScript files it |creates. Not because of reproducible builds, which i consider a u

[bug #57876] [PATCH] groff.1.man: Minor fixes, unchanged output

Update of bug #57876 (project groff): Status:None => Fixed Assigned to:None => gbranden Open/Closed:Open => Closed Planned Release:

[bug #55091] [PATCH] stop stripping comments and spaces from installed macro packages

Update of bug #55091 (project groff): Status:None => Postponed ___ Reply to this item at: ___

[bug #55708] [PATCH] broken Makefile dependency for doc/automake.pdf on Cygwin

Update of bug #55708 (project groff): Status:None => In Progress Assigned to:None => gbranden Summary: broken Makefile dependency for doc/automake.pdf on Cygwin [PATCH] => [PATCH]

[bug #59317] [PATCH] doc/groff.texi cosmetic cleanup

Update of bug #59317 (project groff): Status: Confirmed => Fixed Open/Closed:Open => Closed Planned Release:None => 1.23.0

[groff] 02/02: doc/groff.texi: Follow up Dave's improvements.

gbranden pushed a commit to branch master in repository groff. commit 0c559f5fe149932803ea6c566fcfdccf17642c10 Author: G. Branden Robinson AuthorDate: Fri Oct 23 05:10:16 2020 +1100 doc/groff.texi: Follow up Dave's improvements. Content: * (History) Explain pronunciation of

[groff] 01/02: doc/groff.texi: Clean up.

gbranden pushed a commit to branch master in repository groff. commit 453c8af8d0f37a4d18eb91242f8159dfa04f5f92 Author: Dave Kemper AuthorDate: Thu Oct 22 22:00:07 2020 +1100 doc/groff.texi: Clean up. These are numerous changes, but they're all cosmetic: spelling, grammar,

[bug #57218] [PATCH] Reproducible builds support is broken and embeds timezone

Follow-up Comment #4, bug #57218 (project groff): I think groff should not write %%CreationDate into PostScript files it creates. Not because of reproducible builds, which i consider a useless and even detrimental feature, but because of privacy concerns. That would also solve this so-called

[bug #55335] [PATCH] preconv produces CR CR LF end-of-line on MS-Windows

Follow-up Comment #3, bug #55335 (project groff): I don't see a risk here. If i read src/include/nonposix.h correctly, SET_BINARY() is a NOOP on any sane system. So given that Eli tested it extensively on Windows, i think no further testing is needed. Any developer who understands in principle

[bug #55334] preconv fails when build with libuchardet on MS-Windows

Follow-up Comment #15, bug #55334 (project groff): Re comment #14: All makes sense to me. Branden, do you want to write the required patch to avoid guessing from the filename and instead use fseek(3) and check for errors, as i suggested? And test it? I don't really want to work on it because

Re: UTP Revisited: scoping the project

On Tue, 20 Oct 2020 21:16:45 +0200 Marc Chantreux wrote: > > I?ve not used another editor where you can pipe chunks of text *ad > > hoc* through scripts or even awk/perl one-liners. > > except ed, sam (AFAIR), and every vi clones i used. In emacs, you select the chunks of text, press M-|, and

Re: Learning troff - where to start?

Hello Johann, Johann Höchtl wrote: > Your help would be very appreciated. BTW How comes that section headings > work as a forward reference? Can I move with utmac the complete TOC to > the frontmatter without using psutils or the likes? The makefile, in the utmac/demo, runs three passes of

[bug #56694] [PATCH] troff mixes malloc / delete[]

Update of bug #56694 (project groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.23.0

[bug #57618] man/groff_char.7.man: page needs an overhaul

Follow-up Comment #12, bug #57618 (project groff): Even more fixed in e3bf6b74d60d8e536dd3a17e893312a5c82efd39. Right? :P ___ Reply to this item at:

[groff] 03/04: src/roff/troff/env.cpp: Remove straggling line.

gbranden pushed a commit to branch master in repository groff. commit 3394886519dbfecbab3892bc06946ece9211abb9 Author: G. Branden Robinson AuthorDate: Thu Oct 22 21:06:19 2020 +1100 src/roff/troff/env.cpp: Remove straggling line. Should have been part of commit

[groff] 01/04: groff_char(7): Clarify acceptable Unicode escapes.

gbranden pushed a commit to branch master in repository groff. commit e3bf6b74d60d8e536dd3a17e893312a5c82efd39 Author: G. Branden Robinson AuthorDate: Thu Oct 22 20:52:50 2020 +1100 groff_char(7): Clarify acceptable Unicode escapes. * man/groff_char.7.man (Description/Special

[groff] 02/04: Stop mixing up heap storage management strategies.

gbranden pushed a commit to branch master in repository groff. commit 06ee2524421ae607d0310204e3ddaea790af2fd6 Author: G. Branden Robinson AuthorDate: Thu Oct 22 21:03:09 2020 +1100 Stop mixing up heap storage management strategies. ...in one respect, anyway. A further audit would

[groff] 04/04: man pages: Further tweak apopos/man -k summaries.

gbranden pushed a commit to branch master in repository groff. commit 6ab8c90efc1a4962f6e4ace926a723845dd93bdf Author: G. Branden Robinson AuthorDate: Thu Oct 22 21:08:36 2020 +1100 man pages: Further tweak apopos/man -k summaries. Continues

Re: Learning troff - where to start?

Hello Johann, Johann Höchtl wrote: > .../neatroff/roff  -mu-fonts -mus para.tr | ../neatpost/pdf -pa4 > out.pdf u-fonts only contains macros shared by all fonts and does nothing by itself, you should use u-libertine or u-biolinum instead: roff -mus -mu-libertine para.tr | pdf -pa4 >

[bug #59317] [PATCH] doc/groff.texi cosmetic cleanup

Update of bug #59317 (project groff): Status:None => Confirmed Assigned to:None => gbranden ___ Reply to this item at:

Re: Learning troff - where to start?

On 21.10.20 22:21, Wim Stockman wrote: maybe you can start by reading the book. it has new life on github. https://github.com/larrykollar/Unix-Text-Processing Thank you for the link. However I am specifically asking the top-poster Pierre-Jean how he achieves the following in his