>> The man page says that \(bu has unicode U+2022, but nroff puts out
>> U+00b7. Is this a "bug" (... or did I once again got the
>> documentation wrong ;-)?
>
> Indeed. I see this as a bug. [...]
Yep. It is missing a clause that does the mapping for non-UTF8 TTY
devices. Fixed in git, and
> The man page says that \(bu has unicode U+2022, but nroff puts
> out U+00b7. Is this a "bug" (... or did I once again got the
> documentation wrong ;-)?
bash$ groff -Tutf8 | xxd
\(bu
000: c2b7 0a0a 0a0a 0a0a 0a0a 0a0a 0a0a 0a0a
Indeed. I see this as a bug.
I find i
Hello,
I did ask a similar question some time ago ... maybe the man page groff_char.7
is not optimal ;-)
The man page says that \(bu has unicode U+2022, but nroff puts out U+00b7. Is
this a "bug" (... or did I once again got the documentation wrong ;-)?
--Carsten
On Wednesday, June 17, 2015, Ralph Corderoy wrote:
> Hi Peng,
>
> > > I've fixed the issue with the title coming out as LS("1") by
> > > removing the quotes, so it is LS(1) now, but I don't think that's
> > > what you want.
> >
> > Right. That is not what I want. But could you create a version th
Hi Peng,
> > I've fixed the issue with the title coming out as LS("1") by
> > removing the quotes, so it is LS(1) now, but I don't think that's
> > what you want.
>
> Right. That is not what I want. But could you create a version that
> doesn't generate the title?
I'm getting a bit lost, and I'm
