[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: manpage hyphens in zfsutils



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Robert,

disclaimer: I am not /entirely/ sure, I know what I'm saying below.

On 22.10.2011 23:10, Robert Millan wrote:
> Thanks.  It seems there are some unnecessary hunks left, e.g.:
> 
> --------------------------------------------------------------
> +\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-

Why do think so? Removing them seems to turn the - into a hyphen again
(but see below).

> Also, are you sure none of the changes is redundant?  I'm not familiar
> with groff, but if it supports verbatim blocks, then dashes might be
> preserved there without escaping?
> 

I am not (very) familiar either, however the ".nf" "verbatim" blocks
only preserve white spaces. It does not affect the character
interpretation. Have a look on my example:

.sp
This should be a dash, but actually is a hyphen: -
.sp
This is a hyphen: \(hy
.sp
This is a dash: \-
.sp
.nf
This should be a dash: -, and this too: \-
On the other hand, that's a hyphen: \(hy
.fi

Note: Debian was patched to force - to be a minus, not a hyphen as is
groffs default. Maybe many other groffs have been patched as well, at
least a test run on Fedora seems to avoid the problem as well.


FTR: Such discussions are just yet another reason why we should be using
something more modern instead.

- -- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOpeU3AAoJEMcrUe6dgPNt/NkP/08TWYuHVB+MzMlyYL1E9n7r
dYOY/lQKlY0nqe+wELgSusx7TB9qzULP8IGornzxzj4jksEiycgMVqq9qIOzTsdF
IBG3yvNgWDd3JNiOsNugEnJ/wzHbCRcHO7bil0u1T2r/aYYH17ESmyDGkSOKCGPF
7hUvWm7cypETjW5QuQhTSaX2YGr128p1+sTcfo17yDTTIKXqdjpvGU2qoC516fPD
C2xvjb2b9XtPToHVIwfJ4CYtP6Yu8wA8pD10LPrzFZlc3uTKw1gEC2w3nfVQqXEi
eF6BUmKwGw2Z6RqqGKTHgrdICGpV6/CSImFEN7u6E+a138bXOewsJYhDv+AVcKg8
Eu93t3sD2hKyqYsY2Puv39BXm1qzbsRbiPu2I8yAZJ8GtZbt3wiJFO/x7BW9jsAB
nVhV1mX1S4zNbuZHQpfZmnjFo4KinJoIxZWq66S1GjNBCxbfzUZBMRaIEW2dmLIa
+BZ8LkrZFkfI0NgiaSPlfoqNOQhqaCjI4/RSRX29dqEzHbL5GMyKJbbmH2fZ9rYb
v1MItd4Ye2k9Uf0VVrUPz7kjn6iLbrZmdVJPzJVFe5sHKKWCjNLraXgsf0MLLUJc
PR/JAiIiW5mlTMlEYph/0/dBVDiyEHM9ZOSTWF8gOONcbcYyVZ4MWtk6k8JQSRqb
bZ5sgwS7OG3uems3UFT+
=zxCt
-----END PGP SIGNATURE-----


Reply to: