[tldoc] Problems in afm2pl.1, devnag.1, dvitodvi.1, synctex.1, ttf2tfm.1

esr at thyrsus.com esr at thyrsus.com
Tue Jun 18 07:13:54 CEST 2013


This is automatically generated email about markup problems in a man
page for which you appear to be responsible.  If you are not the right
person or list, please tell me so I can correct my database.

See http://catb.org/~esr/doclifter/bugs.html for details on how and
why these patches were generated.  Feel free to email me with any
questions.  Note: These patches do not change the modification date of
any manual page.  You may wish to do that by hand.

I apologize if this message seems spammy or impersonal. The volume of
markup bugs I am tracking is over five hundred - there is no real
alternative to generating bugmail from a database and template.

--
                             Eric S. Raymond
-------------- next part --------------
Problems with ttf2tfm.1:

Use of low-level troff hackery to set special indents or breaks can't
be translated. The page will have rendering faults in HTML, and
probably also under third-party man page browsers such as Xman,
Rosetta, and the KDE help browser.  This patch eliminates .br, .ta, .ti,
.ce, .in, and \h in favor of requests like .RS/.RE that have
structural translations.

TBL markup not used where it should be.  Tables stitched together
with .ta or list requests can't be lifted to DocBook and will often
choke third-party viewers such as TKMan, XMan, Rosetta, etc.

--- ttf2tfm.1-unpatched	2013-05-25 19:52:24.668023639 -0400
+++ ttf2tfm.1	2013-05-25 19:52:24.204023647 -0400
@@ -461,18 +461,15 @@
 .B \-P
 you specify the platform ID; defined values are:
 .PP
-.in +4m
-.ta 3iC
-.I "platform	platform ID (pid)"
-.sp
-.ta 3iR
+.TS 
+l l.
+\fIplatform\fP	\fIplatform ID (pid)\fP
+_
 Apple Unicode	0
-.br
 Macintosh	1
-.br
-ISO	2
-.br
+ISO     	2
 Microsoft	3
+.TE
 .PP
 The encoding ID depends on the platform.
 For pid=0, we ignore the
@@ -481,121 +478,78 @@
 Unicode version\ 2.0.
 For pid=1, the following table lists the defined values:
 .PP
-.in +4m
-.ta 3iC
-.ti -2m
+.RS
 platform ID = 1
-.sp
-.I "script	encoding ID (eid)"
-.sp
-.ta 3iR
-Roman	0
-.br
+.RE
+.TS
+l l.
+\fIscript\fP	\fIencoding ID (eid)\fP
+_
+Roman   	0
 Japanese	1
-.br
-Chinese	2
-.br
-Korean	3
-.br
-Arabic	4
-.br
-Hebrew	5
-.br
-Greek	6
-.br
-Russian	7
-.br
+Chinese 	2
+Korean  	3
+Arabic  	4
+Hebrew  	5
+Greek   	6
+Russian 	7
 Roman Symbol	8
-.br
 Devanagari	9
-.br
 Gurmukhi	10
-.br
 Gujarati	11
-.br
-Oriya	12
-.br
-Bengali	13
-.br
-Tamil	14
-.br
-Telugu	15
-.br
-Kannada	16
-.br
+Oriya   	12
+Bengali 	13
+Tamil   	14
+Telugu  	15
+Kannada 	16
 Malayalam	17
-.br
 Sinhalese	18
-.br
-Burmese	19
-.br
-Khmer	20
-.br
-Thai	21
-.br
-Laotian	22
-.br
+Burmese  	19
+Khmer   	20
+Thai    	21
+Laotian 	22
 Georgian	23
-.br
 Armenian	24
-.br
 Maldivian	25
-.br
-Tibetan	26
-.br
+Tibetan 	26
 Mongolian	27
-.br
-Geez	28
-.br
-Slavic	29
-.br
+Geez    	28
+Slavic  	29
 Vietnamese	30
-.br
-Sindhi	31
-.br
+Sindhi  	31
 Uninterpreted	32
+.TE
 .PP
 Here are the ISO encoding IDs:
 .PP
-.in +4m
-.ta 3iC
-.ti -2m
+.RS
 platform ID = 2
-.sp
-.I "encoding	encoding ID (eid)"
-.sp
-.ta 3iR
-ASCII	0
-.br
+.RE
+.TS
+l l.
+\fIencoding\fP	\fIencoding ID (eid)\fP
+ASCII   	0
 ISO 10646	1
-.br
 ISO 8859-1	2
+.TE
 .PP
 And finally, the Microsoft encoding IDs:
 .PP
-.in +4m
-.ta 3iC
-.ti -2m
+.RS
 platform ID = 3
-.sp
-.I "encoding	encoding ID (eid)"
-.sp
-.ta 3iR
-Symbol	0
-.br
-Unicode 2.0	1
-.br
-Shift JIS	2
-.br
-GB 2312 (1980)	3
-.br
-Big 5	4
-.br
+.RE
+.TS
+l l.
+\fIencoding\fP	\fIencoding ID (eid)\fP
+Symbol          	0
+Unicode 2.0     	1
+Shift JIS       	2
+GB 2312 (1980)  	3
+Big 5           	4
 KS X 1001 (Wansung)	5
-.br
 KS X 1001 (Johab)	6
-.br
-UCS-4	10
+UCS-4           	10
+.TE
 .PP
 The program will abort if you specify an invalid platform/encoding ID
 pair.
@@ -979,58 +933,50 @@
 .B kpathsea
 version\ 3.2:
 .PP
-.in +4m
-.ta 2i
-.C \&.ttf \ and "\ .ttc	TTFONTS"
-.br
-.C "ttf2pk.cfg	TTF2PKINPUTS"
-.br
-.C "\&.map	TTF2PKINPUTS"
-.br
-.C "\&.enc	TTF2PKINPUTS, TTF2TFMINPUTS"
-.br
-.C "\&.rpl	TTF2PKINPUTS, TTF2TFMINPUTS"
-.br
-.C "\&.tfm	TFMFONTS"
-.br
-.C "\&.sfd	TTF2PKINPUTS, TTF2TFMINPUTS"
+.RS
+.TS
+l l.
+\&.ttf and .ttc	TTFONTS
+ttf2pk.cfg  	TTF2PKINPUTS
+\&.map  	TTF2PKINPUTS
+\&.enc  	TTF2PKINPUTS, TTF2TFMINPUTS
+\&.rpl  	TTF2PKINPUTS, TTF2TFMINPUTS
+\&.tfm  	TFMFONTS
+\&.sfd  	TTF2PKINPUTS, TTF2TFMINPUTS
+.TE
+.RE
+
 .PP
 And here the same for pre-3.2-versions of
 .B kpathsea:
 .PP
-.in +4m
-.ta 2i
-.C \&.ttf \ and "\ .ttc	T1FONTS"
-.br
-.C "ttf2pk.cfg	TEXCONFIG"
-.br
-.C "\&.map	TEXCONFIG"
-.br
-.C "\&.enc	TEXPSHEADERS"
-.br
-.C "\&.rpl	TEXPSHEADERS"
-.br
-.C "\&.tfm	TFMFONTS"
-.br
-.C "\&.sfd	TEXPSHEADERS"
+.RS
+.TS
+l l.
+\&.ttf and .ttc	T1FONTS
+ttf2pk.cfg	TEXCONFIG
+\&.map  	TEXCONFIG
+\&.enc  	TEXPSHEADERS
+\&.rpl  	TEXPSHEADERS
+\&.tfm  	TFMFONTS
+\&.sfd  	TEXPSHEADERS
+.TE
+.RE
 .PP
 Finally, the same for pre-3.0-versions (as used e.g. in te\*(TX\ 0.4):
 .PP
-.in +4m
-.ta 2i
-.C \&.ttf \ and "\ .ttc	DVIPSHEADERS"
-.br
-.C "ttf2pk.cfg	TEXCONFIG"
-.br
-.C "\&.map	TEXCONFIG"
-.br
-.C "\&.enc	DVIPSHEADERS"
-.br
-.C "\&.rpl	DVIPSHEADERS"
-.br
-.C "\&.tfm	TFMFONTS"
-.br
-.C "\&.sfd	DVIPSHEADERS"
+.RS
+.TS
+l l.
+\&.ttf and .ttc	DVIPSHEADERS
+ttf2pk.cfg	TEXCONFIG
+\&.map	TEXCONFIG
+\&.enc	DVIPSHEADERS
+\&.rpl	DVIPSHEADERS
+\&.tfm	TFMFONTS
+\&.sfd	DVIPSHEADERS
+.TE
+.RE
 .PP
 Please consult the info files of
 .B kpathsea
@@ -1056,8 +1002,9 @@
 .B kpathsea
 library.
 .PP
-.in +2m
+.RS
 .C "kpsewhich -progname=ttf2tfm -expand-var='$TTFONTS'"
+.RE
 .PP
 We select the program name also since it is possible to specify
 variables which are searched only for a certain program -- in our
@@ -1088,21 +1035,18 @@
 .C config.sys
 for OS/2):
 .PP
-.in +4m
-.ta 2i
-.C \&.ttf \ and "\ .ttc	TTFONTS"
-.br
-.C "ttf2pk.cfg	TTFCFG"
-.br
-.C "\&.map	TTFCFG"
-.br
-.C "\&.enc	TTFCFG"
-.br
-.C "\&.rpl	TTFCFG"
-.br
-.C "\&.tfm	TEXTFM"
-.br
-.C "\&.sfd	TTFCFG"
+.RS
+.TS
+l l.
+\&.ttf and .ttc	TTFONTS
+ttf2pk.cfg	TTFCFG
+\&.map  	TTFCFG
+\&.enc  	TTFCFG
+\&.rpl  	TTFCFG
+\&.tfm  	TEXTFM
+\&.sfd  	TTFCFG
+.TE
+.RE
 .PP
 If one of the variables isn't set, a warning message is emitted.
 The current directory will always  be searched.
-------------- next part --------------
Problems with dvitodvi.1:

.ce markup can't be structurally translated, and is likely
to cause rendering flaws in generated HTML.

--- dvitodvi.1-unpatched	2013-05-25 10:37:15.080646572 -0400
+++ dvitodvi.1	2013-05-25 10:37:14.808646577 -0400
@@ -110,18 +110,21 @@
 This section contains some sample re-arrangements. To put two pages on one
 sheet (of landscaped A3 paper), the pagespec to use is:
 .sp
-.ce
+.RS
 2:0+1(21cm,0)
+.RE
 .sp
 To reduce an A3 page to A4 size, the pagespec to use is:
 .sp
-.ce
+.RS
 700@(-.3in,-.3in)
+.RE
 .sp
 To select all of the odd pages in reverse order, use:
 .sp
-.ce
+.RS
 2:-0
+.RE
 .sp
 .SH AUTHOR
 Angus Duggan, from dviselect(1), by
-------------- next part --------------
Problems with synctex.1:

Two-digit year in .Dd macro.

--- synctex.1-unpatched	2013-05-23 17:55:52.531385988 -0400
+++ synctex.1	2013-05-23 17:56:06.563385726 -0400
@@ -1,4 +1,4 @@
-.Dd 03/13/12               \" DATE 
+.Dd 03/13/2012               \" DATE 
 .Dt synctex 1      \" Program name and manual section number 
 .Sh NAME
 .Nm synctex
-------------- next part --------------
Problems with devnag.1:

Ambiguous or invalid backslash.  This doesn't cause groff a problem.
but it confuses doclifter and may confuse older troff implementations.

--- devnag.1-unpatched	2012-07-06 10:48:31.946717382 -0400
+++ devnag.1	2012-07-06 10:49:24.874716396 -0400
@@ -7,7 +7,7 @@
 .PP
 .B devnag
 is a preprocessor that reads transliterated Devanagari input delimited by
-\dn and converts it into a form with which TeX is familiar.
+\\dn and converts it into a form with which TeX is familiar.
 .PP
 The preprocessor
 handles the details of character placement such as the alignment of
-------------- next part --------------
Problems with afm2pl.1:

Use of low-level troff hackery to set special indents or breaks can't
be translated. The page will have rendering faults in HTML, and
probably also under third-party man page browsers such as Xman,
Rosetta, and the KDE help browser.  This patch eliminates .br, .ta, .ti,
.ce, .in, and \h in favor of requests like .RS/.RE that have
structural translations.

--- afm2pl.1-unpatched	2012-06-30 21:19:50.487703768 -0400
+++ afm2pl.1	2012-06-30 21:25:17.719697649 -0400
@@ -337,29 +337,34 @@
 .PP
 Letterspacing has various side\-effects for ligkern info\&. Instead of simply applying the extra ligkern info (see previous section), the following is done:
 .sp
-.RS 4
-\h'-04' 1.\h'+02'In case of positive letterspacing, native ligatures are removed, unless the \-k option is specified\&.
-.RE
+.IP 1.
+In case of positive letterspacing, native ligatures are removed, unless the \-k option is specified\&.
 .sp
-.RS 4
-\h'-04' 2.\h'+02'Extra ligkern info is applied as usual, except that in case of positive letterspacing different defaults apply:
+.IP 2.
+Extra ligkern info is applied as usual, except that in case of positive letterspacing different defaults apply:
 \-l 0
 is quietly ignored, ligkern comments in the encoding file are ignored, and defpre\&.lig is read instead of default\&.lig\&.
-.RE
 .sp
-.RS 4
-\h'-04' 3.\h'+02'Letterspacing is applied\&. This adds a lot of kerns, and modifies existing kerns\&.
-.RE
+.IP 3.
+3.Letterspacing is applied\&. This adds a lot of kerns, and modifies existing kerns\&.
 .sp
-.RS 4
-\h'-04' 4.\h'+02'The extra ligkern info specified with \-L is applied\&. The only ligkern specs which are allowed here, are removals of kerning pairs (with the
+.IP 4
+4.The extra ligkern info specified with \-L is applied\&. The only ligkern specs which are allowed here, are removals of kerning pairs (with the
 {}
 operator)\&. Values 0 and 1 have a similar meaning as for the \-l parameter\&.
 \fIThe tfm format has room for only about 180x180 ligatures and kerning pairs\&.\fR
 This is enough for OT1 encoding, but for texnansi encoding quite a few ligkern specifications have to be removed\&. The pltotf program will remove
 \fIall\fR
-ligkern info if too many ligatures and kerns remain\&. The default lig file is defpost\&.lig\&. This file throws out kerning pairs which are unlikely to be involved in letterspacing, such as kerns involving accents or kerns with a punctuation character or right bracket at the left\&. It does not add letterspacing kerns involving boundarychars\&. Instead, fontspace is increased by twice the letterspacing\&. defpost\&.lig throws out enough kerns in case of texnansi encoding\&. With other encodings, you may have to throw out additional kerning pairs\&.
-.RE
+ligkern info if too many ligatures and kerns remain\&. The default lig
+file is defpost\&.lig\&. This file throws out kerning pairs which are
+unlikely to be involved in letterspacing, such as kerns involving
+accents or kerns with a punctuation character or right bracket at the
+left\&. It does not add letterspacing kerns involving
+boundarychars\&. Instead, fontspace is increased by twice the
+letterspacing\&. defpost\&.lig throws out enough kerns in case of
+texnansi encoding\&. With other encodings, you may have to throw out
+additional kerning pairs\&.
+
 .SH "FONT-BASED UPPER- AND LOWERCASING"
 .PP
 The distribution includes encoding vectors texnanuc\&.enc and texnanlc\&.enc which produce all\-uppercase and all\-lowercase fonts


More information about the tldoc mailing list