Re: End-of-sentence spacing

On 12/21/20, G. Branden Robinson wrote: > I thought you and I worked to fix this earlier this year? We did do some work in this section, but I don't recall addressing this terminology in particular. At the time, it seemed pretty small potatoes. Taken as a whole, I believe the section is

Re: [PROPOSAL] time zones and reproducible builds (was: How to make groff use local timezone?)

Hello fellow groffers, As a consumer , archiver of pdf documents, image files and others. I'm confronted with all that goes wrong when trying to keep systemdates of file synced and keep the same as the original creation date. I've had so many issues with systemdates that or wrongly set , or a

Re: End-of-sentence spacing

At 2020-12-21T17:07:10-0600, Dave Kemper wrote: > On 12/20/20, Peter Schaffter wrote: > > Perhaps I should have been more verbose and written: According > > to the info(1) manual, initially both the WORD_SPACE_SIZE and > > SENTENCE_SPACE_SIZE are 12; since this prevents SS from being larger > >

Re: groff_mdoc(7): Add link to mandoc project.

Hi Ingo! At 2020-12-20T17:16:38+0100, Ingo Schwarze wrote: > G. Branden Robinson wrote on Sun, Dec 20, 2020 at 03:38:54AM -0500: > > commit ca0dfa5ff724eaf21a8b79f4ee825979ef3294fc > > Author: G. Branden Robinson > > AuthorDate: Sun Dec 20 14:10:09 2020 +1100 > > > > groff_mdoc(7): Add link

Re: groff_mdoc(7): Document .Lk and .Mt macros.

Hi Ingo! At 2020-12-20T17:08:22+0100, Ingo Schwarze wrote: > G. Branden Robinson wrote on Sun, Dec 20, 2020 at 03:38:54AM -0500: > > groff_mdoc(7): Document .Lk and .Mt macros. [...] > > .It Li .Lk > > -To be written. > > +Embed hyperlink. > > +. > > +. > > +.Pp > > +.Dl Usage: .Lk Ao url

Re: [mdoc]: Emit diagnostic if .Mt given no arguments.

Hi Ingo! At 2020-12-20T16:38:05+0100, Ingo Schwarze wrote: > G. Branden Robinson wrote on Sun, Dec 20, 2020 at 03:38:56AM -0500: > > * tmac/doc.tmac-u (Mt): Emit a usage diagnostic and return if > > called with no arguments. This introduces an incompatiblility > > with mandoc(1),

Re: Is .rd implemented at all?

At 2020-12-20T22:44:09-0600, Dave Kemper wrote: > On 12/20/20, G. Branden Robinson wrote: > > At 2020-12-16T20:30:33-0600, Dave Kemper wrote: > >> Ubuntu is a Debian-derived distro, and the concurrent "local timezone" > >> thread here points out Debian's proclivity to customize groff in > >>

[bug #59583] [PATCH] addftinfo.cpp: fix different declarations of "i" and "len"

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

[bug #59742] par*push-tag-env should save/restore \n[.sss] alongside \n[.ss]

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

[groff] 03/04: [tests]: Add regression test for Savannah #59742.

gbranden pushed a commit to branch master in repository groff. commit fa6742dbdf51d7af17a6fb735fca07561d3ba360 Author: G. Branden Robinson AuthorDate: Tue Dec 22 14:23:51 2020 +1100 [tests]: Add regression test for Savannah #59742. *

[groff] 04/04: [ms]: Fix inter-sentence space in paragraph tags.

gbranden pushed a commit to branch master in repository groff. commit 009a7efa98b3504003751b3556824dc8f9e49dd0 Author: Dorai Sitaram AuthorDate: Sun Dec 20 22:24:15 2020 + [ms]: Fix inter-sentence space in paragraph tags. * tmac/s.tmac (@IP): Handle inter-sentence space

[groff] 01/04: ChangeLog: Update recent entries.

gbranden pushed a commit to branch master in repository groff. commit a100d988ccdb74b0562e91185cd321a83962e081 Author: G. Branden Robinson AuthorDate: Mon Dec 21 19:48:56 2020 +1100 ChangeLog: Update recent entries. --- ChangeLog | 18 +- 1 file changed, 13 insertions(+), 5

[bug #59742] par*push-tag-env should save/restore \n[.sss] alongside \n[.ss]

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

[bug #59741] bug output Greek glyph [*D] to pdf

Update of bug #59741 (project groff): Category:Core => None Item Group:None => Incorrect behaviour Status:None => Wont Fix Assigned to:

Re: [PROPOSAL] time zones and reproducible builds (was: How to make groff use local timezone?)

At 2020-12-21T23:33:18+, Deri wrote: > On Sunday, 20 December 2020 06:10:25 GMT G. Branden Robinson wrote: > > 2. Switch output of date comments embedded by output drivers off by > > default, and add a common option to reënable them. Document this in > > NEWS. > > 3a. Add a

Re: End-of-sentence spacing

> According to the info(1) manual, initially both the WORD_SPACE_SIZE and > SENTENCE_SPACE_SIZE are 12; since this prevents SS from being larger > than WS, it effectively disables sentence spacing A careful reading reveals that the second argument of .ss is *extra* spacing, so the default

[bug #59742] par*push-tag-env should save/restore \n[.sss] alongside \n[.ss]

Update of bug #59742 (project groff): Status:None => Confirmed ___ Follow-up Comment #1: Thanks for this report. It does indeed _look_ like an oversight in the package implementation.

Re: End-of-sentence spacing

On Tue, Dec 22, 2020, Tadziu Hoffmann wrote: > For those who have not read it yet: the original > > http://www.heracliteanriver.com/?p=324 > > has unfortunately vanished, but I have saved a copy: > > http://www.usm.uni-muenchen.de/~hoffmann/roff/tmp/typographyspacing.pdf Thank you! I

Re: "mom": addition of ellipsis causes an over-strike

>> On Sun, Dec 20, 2020, Steve Ross via wrote: >> In the resulting PDF output file, the ellipsis appears on page 10, >> as expected.  However, on the same line, about six characters >> further to the right, I also see about three characters being >> over-struck, which is unexpected. >> >> I have

Re: [PROPOSAL] time zones and reproducible builds (was: How to make groff use local timezone?)

On Tuesday, 22 December 2020 00:24:15 GMT Dave Kemper wrote: > Are there cases where the timestamp within the file would differ from > the timestamp *of* the file? This typically happens when a file is > edited after it's created -- which could be common with HTML output, > but would seem to be

Re: [PROPOSAL] time zones and reproducible builds (was: How to make groff use local timezone?)

On 12/21/20, Deri wrote: > Consider the case where multiple -Z produced groff files, > produced at different times, are combined into one gropdf run. The only > sensible time to include > in the meta-data is the time the pdf was created, why lose potentially > useful information? If you need to

Re: End-of-sentence spacing

> [...] at least it felt like I was being individually targeted, > so I promptly wilted. I mean of course the famous > > https://slate.com/technology/2011/01/two-spaces-after-a-period-why-you-should-never-ever-do-it.html For those who have not read it yet: the original

Re: [PROPOSAL] time zones and reproducible builds (was: How to make groff use local timezone?)

On Sunday, 20 December 2020 06:10:25 GMT G. Branden Robinson wrote: > 2. Switch output of date comments embedded by output drivers off by > default, and add a common option to reënable them. Document this in > NEWS. > 3a. Add a device-independent output command, something like "x >

Re: End-of-sentence spacing

On 12/20/20, Peter Schaffter wrote: > Perhaps I should have been more verbose and written: According > to the info(1) manual, initially both the WORD_SPACE_SIZE and > SENTENCE_SPACE_SIZE are 12; since this prevents SS from being larger > than WS, it effectively disables sentence spacing.

Re: [PROPOSAL] time zones and reproducible builds (was: How to make groff use local timezone?)

On 12/20/20, G. Branden Robinson wrote: > Thoughts from anyone reading? I concur with all points of this plan.

[bug #59750] italic correction sometimes fails when the same glyphs are invoked with different input

Follow-up Comment #1, bug #59750 (project groff): "Elsewhere" turns out to be tmac/fallbacks.tmac , where \[u2161] and its kin are defined with .fchar, suggesting that the root problem is that .fchar and \/ aren't on speaking

[bug #59676] [PATCH] grog/subs.pl: Don't use "exists" on array values

Follow-up Comment #1, bug #59676 (project groff): [comment #0 original submission:] > 1) perlfunc(1) warns against using "exists" on array values. Yes, but in both instances of "exists" that are modified by this patch, it is being called on a hash element -- precisely what the "exists" function

[bug #59750] italic correction sometimes fails when the same glyphs are invoked with different input

URL: Summary: italic correction sometimes fails when the same glyphs are invoked with different input Project: GNU troff Submitted by: barx Submitted on: Mon 21 Dec 2020 02:06:56 PM CST

[bug #59583] [PATCH] addftinfo.cpp: fix different declarations of "i" and "len"

Update of bug #59583 (project groff): Severity: 3 - Normal => 2 - Minor Item Group:None => Warning/Suspicious behaviour Status:None => In Progress Assigned