On 2022-11-26 13:56, G. Branden Robinson wrote:
A lot of the pieces are in place to make this work (Deri and I have
wrangled over gropdf's diagnostic messages in this very area, but I
think we reached consensus :D ), but it needs integration testing under
multiple scenarios.
In the meantime I
On Saturday, 26 November 2022 21:56:04 GMT G. Branden Robinson wrote:
> Deri, can you help me come up with a list of things that will break when
> running ps2pdf over a PostScript document? PDFs produced that way will
> have no CMap. What will happen to PS documents that use the SS or ZDR
> fonts
On Saturday, 26 November 2022 20:23:22 GMT G. Branden Robinson wrote:
> This is probably of most interest to Deri but I thought I'd send it to
> the list.
>
> This is kind of a follow-up to a message from July.
>
> https://lists.gnu.org/archive/html/groff/2022-07/msg00145.html
>
> I'm playing wi
"G. Branden Robinson" writes:
evince also complains. Apart from the usual handful of
Gtk-WARNING and
Gtk-CRITICAL diagnostics, because cool kids like GNOME
developers never
look at the standard error stream ("terminal window? what would
I need
that for?"), I get this.
some font thing fa
On 2022-11-26 13:19, G. Branden Robinson wrote:
I would attach scans of Tables I and II from "NROFF/TROFF User's
Manual", the version dated 1976, published with Volume 2 of the Unix
Programmer's Manual (1979)
Thanks for looking into this. It took me a trip down memory lane as I
believe I was t
"G. Branden Robinson" writes:
> For what it's worth, groff and Heirloom doctools nroff don't print
> "something else" in bold (this is true even in Heirloom's default, _not_
> groff compatibility, mode), and DWB 3.3 nroff does.
Oh, incidentally, I ran into what felt to me like a bug in groff tha
"G. Branden Robinson" writes:
> It's my lucky day! I've been meaning to buttonhole you for quite some
> time regarding my man(7) reforms and pod2man's output.
I just made another major release, so on the plus side my brain is fully
up to speed with the source, but on the minus side, I'm also a
[dropping everyone but Russ and the groff list]
Hi Russ,
It's my lucky day! I've been meaning to buttonhole you for quite some
time regarding my man(7) reforms and pod2man's output.
I had notions of trying to get you into a sort of informal summit
meeting at DebConf 20 but a lot of people got s
[dropping Paul, Alex, and tz@iana]
At 2022-11-26T22:20:23+0100, Steffen Nurpmeso wrote:
> It would be great if groff would release adjustments to grotty so
> that one could again use copy+paste also in manuals.
One can.
> And now please do not beat me onto that hyphen-minus for options, and
> th
Hi Paul!
At 2022-11-26T13:01:58-0800, Paul Eggert wrote:
> [taking t...@iana.org off the cc as this isn't particularly time zone
> relevant any more]
Fair point.
> With the same input (that is, with the last line being "Copy and paste
> me: \f(CRfoo\-bar-baz\fP." and the same commands on Ubuntu
G. Branden Robinson wrote in
<20221126035253.pli53qzgfx6tbax5@illithid>:
|At 2022-11-25T18:18:46-0800, Paul Eggert wrote:
...
|> If we did that, Groff would set a source string like "\*-\*-help" as
|> "−−help", with two instances of U+2212 MINUS SIGN instead of U+002D
|> HYPHEN-MINUS. Therefo
Hi Paul,
At 2022-11-25T18:31:02-0800, Paul Eggert wrote:
> On 2022-11-23 10:43, Paul Eggert wrote:
> > I installed that
> Further testing showed that the installed patch doesn't work with
> traditional troff, which doesn't support groff escape sequences like
> \(aq.
I think this patch goes too fa
[taking t...@iana.org off the cc as this isn't particularly time zone
relevant any more]
On 2022-11-25 19:52, G. Branden Robinson wrote:
If I prepare the following document:
$ cat EXPERIMENTS/minus-and-hyphen.man
.TH foo 1 2022-11-25 "groff test suite"
.SH Name
foo \- frobnicate a bar
.SH De
At 2022-11-25T19:50:14-0800, Paul Eggert wrote:
> On 2022-11-25 19:20, Russ Allbery wrote:
> > You have to be very careful with the combination of \f(CW and \fP on
> > Solaris 10 nroff
>
> That should be OK, as \f(CW - which is now \f(CR - is used only if
> \n(.g is nonzero, i.e., only if it's gro
This is probably of most interest to Deri but I thought I'd send it to
the list.
This is kind of a follow-up to a message from July.
https://lists.gnu.org/archive/html/groff/2022-07/msg00145.html
I'm playing with using the PostScript slanted symbol font ("SS") with
gropdf.
Here's my input docum
On Saturday, 26 November 2022 03:52:53 GMT G. Branden Robinson wrote:
> Some distributors do violence to the man.local file. But I am not a PDF
> expert; for this I'll have to turn as I often do to Deri James, who also
> wrote the gropdf output driver. Deri, what's a good way to root-cause
> the
"G. Branden Robinson" wrote:
Hi Tadziu and Branden,
Thanks for the quickfix Tadziu.
I've noted for myself to check the output of any preprocessor when trying to
understand certain behaviour.
Branden thanks for sketching out the broader issue.
Being just an enduser, it's hard for me to give any
17 matches
Mail list logo