Weird rendering of \*(C+

Weird rendering of \*(C+

[Ulrich Spörlein]

[-- Attachment #1: Type: text/plain, Size: 559 bytes --]

Hi folks,

FreeBSD has added pod2man'd manpages for clang(1) and tblgen(1), they
render quite similar to groff, except for \*(C+ which is completely out
of whack, please see attached snippet from the manpages.

It renders like:

DESCRIPTION
       clang is a C, Cv'-.1v'h'-1p'+h'-1p'+v'.1v'h'-1p', and Objective-C
       compiler which encompasses preprocessing, parsing, optimization, code
       generation, assembly, and linking.  Depending on which high-level mode
       setting is passed, Clang will stop before doing a full link.  While


Regards,
Uli

[-- Attachment #2: clang.1 --]
[-- Type: text/plain, Size: 5052 bytes --]

.\" $FreeBSD$
.\" Automatically generated by Pod::Man 2.22 (Pod::Simple 3.07)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" Set up some character translations and predefined strings.  \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote.  \*(C+ will
.\" give a nicer C++.  Capital omega is used to do unbreakable dashes and
.\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
.\" nothing in troff, for use with C<>.
.tr \(*W-
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
.ie n \{\
.    ds -- \(*W-
.    ds PI pi
.    if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
.    if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\"  diablo 12 pitch
.    ds L" ""
.    ds R" ""
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds -- \|\(em\|
.    ds PI \(*p
.    ds L" ``
.    ds R" ''
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.ie \nF \{\
.    de IX
.    tm Index:\\$1\t\\n%\t"\\$2"
..
.    nr % 0
.    rr F
.\}
.el \{\
.    de IX
..
.\}
.\"
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear.  Run.  Save yourself.  No user-serviceable parts.
.    \" fudge factors for nroff and troff
.if n \{\
.    ds #H 0
.    ds #V .8m
.    ds #F .3m
.    ds #[ \f1
.    ds #] \fP
.\}
.if t \{\
.    ds #H ((1u-(\\\\n(.fu%2u))*.13m)
.    ds #V .6m
.    ds #F 0
.    ds #[ \&
.    ds #] \&
.\}
.    \" simple accents for nroff and troff
.if n \{\
.    ds ' \&
.    ds ` \&
.    ds ^ \&
.    ds , \&
.    ds ~ ~
.    ds /
.\}
.if t \{\
.    ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
.    ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
.    ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
.    ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
.    ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
.    ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
.\}
.    \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
.    \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
.    \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
\{\
.    ds : e
.    ds 8 ss
.    ds o a
.    ds d- d\h'-1'\(ga
.    ds D- D\h'-1'\(hy
.    ds th \o'bp'
.    ds Th \o'LP'
.    ds ae ae
.    ds Ae AE
.\}
.rm #[ #] #H #V #F C
.\" ========================================================================
.\"
.IX Title "CLANG 1"
.TH CLANG 1 "2010-09-27" "Clang 2.8" "Clang Tools Documentation"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH "NAME"
clang \- the Clang C, C++, and Objective\-C compiler
.SH "SYNOPSIS"
.IX Header "SYNOPSIS"
\&\fBclang\fR [\fB\-c\fR|\fB\-S\fR|\fB\-E\fR] \fB\-std=\fR\fIstandard\fR \fB\-g\fR
  [\fB\-O0\fR|\fB\-O1\fR|\fB\-O2\fR|\fB\-Os\fR|\fB\-O3\fR|\fB\-O4\fR]
  \fB\-W\fR\fIwarnings...\fR \fB\-pedantic\fR
  \fB\-I\fR\fIdir...\fR \fB\-L\fR\fIdir...\fR
  \fB\-D\fR\fImacro[=defn]\fR
  \fB\-f\fR\fIfeature-option...\fR
  \fB\-m\fR\fImachine-option...\fR
  \fB\-o\fR \fIoutput-file\fR
  \fB\-stdlib=\fR\fIlibrary\fR 
  \fIinput-filenames\fR
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
\&\fBclang\fR is a C, \*(C+, and Objective-C compiler which encompasses preprocessing,
parsing, optimization, code generation, assembly, and linking.  Depending on
which high-level mode setting is passed, Clang will stop before doing a full
link.  While Clang is highly integrated, it is important to understand the
stages of compilation, to understand how to invoke it.  These stages are:
.IP "\fBDriver\fR" 4
.IX Item "Driver"
The \fBclang\fR executable is actually a small driver which controls the overall
execution of other tools such as the compiler, assembler and linker.  Typically
you do not need to interact with the driver, but you transparently use it to run
the other tools.

Re: Weird rendering of \*(C+

[Ingo Schwarze]

Hi Ulrich,

Ulrich Spoerlein wrote on Mon, Oct 04, 2010 at 10:35:48PM +0200:

> FreeBSD has added pod2man'd manpages for clang(1) and tblgen(1), they
> render quite similar to groff, except for \*(C+ which is completely out
> of whack, please see attached snippet from the manpages.
> 
> It renders like:
> 
> DESCRIPTION
>        clang is a C, Cv'-.1v'h'-1p'+h'-1p'+v'.1v'h'-1p', and Objective-C

Just update to mandoc-1.10.6, it renders:

  DESCRIPTION
    clang is a C, C++, and Objective-C compiler which encompasses
    preprocessing, parsing, optimization, code generation, assembly, and
    linking.

Kristaps has done some very nice work recently to properly ignore
those low-level roff formatting escapes required for the po2man
standard preamble, see for example

  http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/mandoc/out.c
  rev. 1.7 & 1.8

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

Re: Weird rendering of \*(C+

[Ulrich Spörlein]

On Mon, 04.10.2010 at 22:47:21 +0200, Ingo Schwarze wrote:
> Hi Ulrich,
> 
> Ulrich Spoerlein wrote on Mon, Oct 04, 2010 at 10:35:48PM +0200:
> 
> > FreeBSD has added pod2man'd manpages for clang(1) and tblgen(1), they
> > render quite similar to groff, except for \*(C+ which is completely out
> > of whack, please see attached snippet from the manpages.
> > 
> > It renders like:
> > 
> > DESCRIPTION
> >        clang is a C, Cv'-.1v'h'-1p'+h'-1p'+v'.1v'h'-1p', and Objective-C
> 
> Just update to mandoc-1.10.6, it renders:

Gah! I was using a stale binary, ie. 1.10.5

Sorry for the noise. The pages render just like groff, kudos to y'all!

Uli
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv