Discussion:
`findhyph' documentation issues
(too old to reply)
Werner LEMBERG
2018-04-04 17:22:34 UTC
Permalink
Raw Message
[svn r46739 (from Feb. 25th)]

Two buglets.

(1) If you say

texdoc findhyph ,

a README file gets displayed which starts with

findhyph -- Perl program which finds all words hyphenated by TeX
in a document; see findhyph.pdf or findhyph.1 for
details

Please change this to display `findhyph.man1.pdf' instead.

(2) The file `findhyph.man1.pdf' is incorrectly created. The man file
`findhyph.1' is in UTF8 encoding (since it contains some Czech
characters), while the conversion apparently assumes latin1. To
get correct formatting you need

groff -K utf8 -Tps -man -ww findhyph.1 \
| ps2pdf - findhyph.pdf


Werner
Werner LEMBERG
2018-04-04 17:30:39 UTC
Permalink
Raw Message
Post by Werner LEMBERG
groff -K utf8 -Tps -man -ww findhyph.1 \
| ps2pdf - findhyph.pdf
This can be simplified to

groff -K utf8 -man findhyph.1 \
| ps2pdf - findhyph.pdf

since `-ww' only emits warnings, and `-Tps' is the default output
device.


Werner
Karl Berry
2018-04-05 22:47:18 UTC
Permalink
Raw Message
Hi Werner,

Please change this to display `findhyph.man1.pdf' instead.

Ok.

groff -K utf8

Thanks, but whatever is happening, it apparently doesn't know about the
\v{r} character in Pavel Striz (that's Str\v{r}\'\i\v{z})'s name on line
170 of the source:

man1/findhyph.1:170: warning: can't find special character `u0072_030C'

And indeed, the \v{r} is missing from the output.

The exact command I'm running, following what we do for other man pages
but adding the -K utf8, is:
groff -K utf8 -man -t -rS11 man1/findhyph.1
This is with groff 1.22.2 as installed on CentOS 7[.2.1511].

Anything to be done, or should I just commit with the missing character?
I guess it's better to have all the other characters in there correctly.
--thanks, karl.
Werner LEMBERG
2018-04-06 06:15:53 UTC
Permalink
Raw Message
Post by Karl Berry
And indeed, the \v{r} is missing from the output.
This is with groff 1.22.2 as installed on CentOS 7[.2.1511].
OK. Your CentOS installation apparently doesn't set up the URW
PostScript fonts (as used by ghostscript) for groff; instead, it
simply uses the TR files coming with groff, providing only the most
basic sets of original Adobe metric files.

Given that my openSuSE box handles this fine I suggest that you file a
CentOS bug report :-)

I'll send you privately an archive with the URW stuff (metric and PFA
files), taken from my openSUSE distribution. Please move them to a
directory `/foo/bar', set the environment variable

GROFF_FONT_PATH=/foo/bar

and retry (note that the subdirectory `devps' must stay).


Werner
Werner LEMBERG
2018-04-06 06:41:00 UTC
Permalink
Raw Message
Post by Werner LEMBERG
OK. Your CentOS installation apparently doesn't set up the URW
PostScript fonts (as used by ghostscript) for groff; instead, it
simply uses the TR files coming with groff,
s/TR/metrics/.


Werner

Loading...