On 2023-09-11 20:33:27 -0700, Russ Allbery wrote:
> Yes, I understand why upstream really wants to find a way to make the
> distinction between a language hyphen and an ASCII hyphen to work. They
> are different characters in the *roff language, and in a proper
> typesetting system such as troff
Guillem Jover writes:
> On Mon, 2023-08-14 at 14:18:51 +0200, Samuel Thibault wrote:
>> Yes, we'd ideally want to fix all manpages to have everything set
>> alright. But we have to do that before the release. And if that's not
>> complete, release with the
>>
>> .char - \-
>>
>>
Hi!
[ CCed Russ for the pod2man side of this. ]
On Mon, 2023-08-14 at 14:18:51 +0200, Samuel Thibault wrote:
> I'm marking this important, and am tempted to raise it to serious...
>
> The problem at stake is that we have already a hard time making
> newcomers read manpages. If they can't even
Control: severity -1 serious
On Mon, Aug 14, 2023 at 02:18:51PM +0200, Samuel Thibault wrote:
> As in: maybe we can leave the symptom open until the freeze period, so
> that developers notice the issue and fix their bugs, and on the freeze
> period, introduce the workaround so that end users of
Colin Watson, le dim. 23 juil. 2023 09:46:51 +0100, a ecrit:
> For a campaign that would put the burden closer to the correct set of
> shoulders, I suggest agitating for the reversal of
> https://bugs.debian.org/785353
Yes. I believe we have to do that before even thinking about releasing
with
Control: severity -1 important
Hello,
I'm marking this important, and am tempted to raise it to serious...
The problem at stake is that we have already a hard time making
newcomers read manpages. If they can't even trust copying/pasting lines
from them, they will just definitely turn away, and
At 2023-07-23T09:46:51+0100, Colin Watson wrote:
> On Sat, Jul 22, 2023 at 11:54:24PM -0500, G. Branden Robinson wrote:
> > I know it's not very generous to observe that Sven either made this
> > claim without verifying it first, or had no concern for the facts
> > when making it, but it's hard to
On Sun, Jul 23, 2023 at 09:46:53AM +0100, Colin Watson wrote:
> On Sat, Jul 22, 2023 at 11:54:24PM -0500, G. Branden Robinson wrote:
> > My reasoning is this:
> [...]
> > It is only through the efforts of people in groups 2 and 4 that any
> > headway will be made on the problem. That is where the
On Sat, Jul 22, 2023 at 11:54:24PM -0500, G. Branden Robinson wrote:
> On Sun, 23 Jul 2023 00:37:43 +0100, Colin Watson wrote:
> > > [...] the upstream NEWS file [...] make[s] [no] mention of this
> > > change, or how to revert it locally.
>
> Yeah, see, that's where the hyphen-minus brigade
On 2023-07-23 00:37 +0100, Colin Watson wrote:
> On Sat, Jul 22, 2023 at 06:46:28PM +0200, Sven Joachim wrote:
>> This version of groff maps an unescaped "-" to HYPHEN rather than
>> HYPHEN-MINUS. Due to that, copying text from manpages or following
>> references in the "SEE ALSO" section is
Hi Colin,
On Sun, 23 Jul 2023 00:37:43 +0100, Colin Watson wrote:
> On Sat, Jul 22, 2023 at 06:46:28PM +0200, Sven Joachim wrote:
> > This version of groff maps an unescaped "-" to HYPHEN rather than
> > HYPHEN-MINUS. Due to that, copying text from manpages or following
> > references in the
On Sat, Jul 22, 2023 at 06:46:28PM +0200, Sven Joachim wrote:
> This version of groff maps an unescaped "-" to HYPHEN rather than
> HYPHEN-MINUS. Due to that, copying text from manpages or following
> references in the "SEE ALSO" section is rather unreliable, because many
> manpages contain a
Package: groff-base
Version: 1.23.0-2
This version of groff maps an unescaped "-" to HYPHEN rather than
HYPHEN-MINUS. Due to that, copying text from manpages or following
references in the "SEE ALSO" section is rather unreliable, because many
manpages contain a plain "-" where they should have
13 matches
Mail list logo
