Mercurial > docs > cut
changeset 34:04a3cdadc50c
improved hyphenation and pagination
author | markus schnalke <meillo@marmaro.de> |
---|---|
date | Fri, 02 Oct 2015 07:19:08 +0200 |
parents | a1589fcfe9f4 |
children | 7662fc16cc4c |
files | cut.en.ms |
diffstat | 1 files changed, 5 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/cut.en.ms Fri Oct 02 07:01:20 2015 +0200 +++ b/cut.en.ms Fri Oct 02 07:19:08 2015 +0200 @@ -1,6 +1,6 @@ .so macros .lc_ctype en_US.utf8 -.pl -4v +.pl -3v .TL Cut out selected fields of each line of a file @@ -9,7 +9,7 @@ .. .FS 2015-05. -This text is in the public domain (CC0). +This text is part of the public domain (CC0). It is available online: .I http://marmaro.de/docs/ .FE @@ -102,7 +102,7 @@ .CE .LP (The values to the command line switches may be appended directly -to them or separated by whitespace.) +to them or separated by white\%space.) .PP The field mode is suited for simple tabular data, like the password file. Beyond that, it soon reaches its limits. The typical @@ -233,6 +233,7 @@ appeared in all relevant standards. POSIX.2 specified cut for the first time in its modern form (with \f(CW-b\fP) in 1992. +.pl -1v .SH Multi-byte support .LP @@ -246,7 +247,7 @@ Then there are implementations that have \f(CW-b\fP, but treat it as an alias for \f(CW-c\fP only. These implementations work correctly for single-byte encodings -(e.g. US-ASCII, Latin1) but for multi-byte encodings (e.g. +(e.g. US-ASCII, Latin1) but for multi-byte en\%codings (e.g. UTF-8) their \f(CW-c\fP behaves like \f(CW-b\fP (and \f(CW-n\fP is ignored). Finally, there are implementations that implement \f(CW-c\fP and \f(CW-b\fP in a POSIX-compliant