>> Attached are two patches that fix both issues. Note that the bug
>> with no hyphenation in `@t` is at least 20 years old...
>
> And here's a better fix for the `@t` issue.
Aaand a hopefully final version that takes care of nesting.
Werner
>From c49decc31ff2c4b97b08b01d1ad9125b3b7b2ec0
When using the js-info reader, the location bar displays these URLs for nodes:
https://domterm.org/Wire-byte-protocol.html (if http/https)
file:///home/bothner/DomTerm/web/index.html#Wire-byte-protocol (if file:)
These are also what you get if you right-click a link and select "Copy link".
(T
> Attached are two patches that fix both issues. Note that the bug with
> no hyphenation in `@t` is at least 20 years old...
And here's a better fix for the `@t` issue.
Werner
>From 7753a129ddafbc5ccdae62bb130620883764a526 Mon Sep 17 00:00:00 2001
From: Werner Lemberg
Date: Thu, 15 Dec 20
> As can be seen in the attached output, there is no hyphen in the
> split word. I consider this a bug, since there is zero reason for
> such a surprising (and undocumented) behaviour.
>
> BTW, you get exactly the same output if you replace `@code` with `@t`
> – and *this* is definitely a bug :-
That makes sense regarding keeping the two set of compilation flags separate. I
was expecting that `--with-libinlt-prefix=` would handle libintl needs in the
XS subpackage as well, but using the `PERL_EXT_CPPFLAGS` accomplished this in
https://github.com/spack/spack/pull/34507, so thank you for
