Hello,
by default Heirloom troff inserts a double word space if a line ends with ":".
Is this correct US English typography?
Carsten
Hello,
maybe there is a typo in "5.7 Manipulating Filling and Adjusting" section
"Register: \n[.sss]". In the sentence "Note that the \h escape produces
unbreakable space." the "h" maybe should actually be a space (in the context of
that section).
Carsten
On Wed, Nov 12, 2014, Carsten Kunze wrote:
> Hello,
>
> by default Heirloom troff inserts a double word space if a line
> ends with ":". Is this correct US English typography?
For typeset copy with proportionally-spaced fonts, no. For
monospaced fonts (terminal), yes, but only if sentences are
On Wed, 12 Nov 2014 18:08:12 +0100 (CET)
Carsten Kunze wrote:
> by default Heirloom troff inserts a double word space if a line ends
> with ":". Is this correct US English typography?
It is not incorrect. Typographical convention has varied over time and
treatment of the colon along with it.
Ralph Corderoy wrote (Fri, 07 Nov 2014 16:16:38
+):
> Hi Holger,
>
> > Due to the 'Troff User's Manual' page 24 and the man 7 groff
> > (missing a negation)
>
> What's missing?
"I" -- I was missing .. ;)
> > the statement:
> >
> > .if 'str1'str2' anything
> >
> > cannot handle regular
Hello,
imho that is really annoying since some systems which never
updated from 1.19.2 because of licensing reasons and have not yet
moved to mandoc(1) are not capable to display the manual
correctly via man(1) out of the box.
And it is completely unnecessary since it seems Werner has
designed the
Peter Schaffter wrote:
> For typeset copy with proportionally-spaced fonts, no. For
> monospaced fonts (terminal), yes, but only if sentences are
> separated by two wordspaces as well.
That is new to me. I thought that only one space is used after a colon.
So now what about the behavior of gr
"James K. Lowden" wrote:
> It is not incorrect. Typographical convention has varied over time and
> treatment of the colon along with it. So, "correct" is hard to pin
> down.
>
> I was taught 500 moons ago that a colon may be followed by one or two
> spaces depending on purpose. Examples:
Hello,
the mdoc macros display for
.Ex -std uuencode uudecode b64encode b64decode
EXIT STATUS
The uuencode, uudecode, b64encode, and b64decode utilities [...]
I think the "," before "and" is not intended.
Carsten
> That is new to me. I thought that only one space is
> used after a colon.
Why do people always think that space should exist
only in integer multiples of a basic space quantum?
How about 1.5 times the wordspace after a period that
ends a sentence, 1.2 times the wordspace after a colon?
Or some
>> That is new to me. I thought that only one space is
>> used after a colon.
>
> Why do people always think that space should exist
> only in integer multiples of a basic space quantum?
This is what people used with old typewriters.
> How about 1.5 times the wordspace after a period that ends
> the mdoc macros display for
>
> .Ex -std uuencode uudecode b64encode b64decode
>
> EXIT STATUS
> The uuencode, uudecode, b64encode, and b64decode utilities [...]
>
> I think the "," before "and" is not intended.
It is intended. There are various styles when to use a comma, and one
of t
On 11/12/2014 02:51 PM, Carsten Kunze wrote:
Hello,
the mdoc macros display for
.Ex -std uuencode uudecode b64encode b64decode
EXIT STATUS
The uuencode, uudecode, b64encode, and b64decode utilities [...]
I think the "," before "and" is not intended.
Carsten
The comma before 'and'
On 11/12/2014 03:02 PM, Werner LEMBERG wrote:
That is new to me. I thought that only one space is
used after a colon.
Why do people always think that space should exist
only in integer multiples of a basic space quantum?
This is what people used with old typewriters.
How about 1.5 time
Werner LEMBERG wrote:
> > How about 1.5 times the wordspace after a period that ends a
> > sentence, 1.2 times the wordspace after a colon? Or some other
> > fraction?
>
> groff's `.ss' command allows this.
But groff does not distinguish between an input line that ends with a word and
an inpu
On 11/12/2014 03:13 PM, Carsten Kunze wrote:
Werner LEMBERG wrote:
How about 1.5 times the wordspace after a period that ends a
sentence, 1.2 times the wordspace after a colon? Or some other
fraction?
groff's `.ss' command allows this.
But groff does not distinguish between an input lin
On 11/12/2014 03:00 PM, Werner LEMBERG wrote:
the mdoc macros display for
.Ex -std uuencode uudecode b64encode b64decode
EXIT STATUS
The uuencode, uudecode, b64encode, and b64decode utilities [...]
I think the "," before "and" is not intended.
It is intended. There are various sty
http://en.wikipedia.org/wiki/Serial_comma
-Larry Jones
-Original Message-
From: groff-bounces+lawrence.jones=siemens@gnu.org
[mailto:groff-bounces+lawrence.jones=siemens@gnu.org] On Behalf Of Carsten
Kunze
Sent: Wednesday, November 12, 2014 4:52 PM
To: groff@gnu.org
Subject: [Gr
Clarke Echols wrote:
> Only input lines that end with an end-of-sentence character
> (including colon) is treated other than as a normal single-space-
> between-words situation -- or at least that's my understanding.
Ok, .cflags 1 sets it. I didn't get it on first reading of the
documenta
On 12/11/14 21:51, Carsten Kunze wrote:
> Hello,
>
> the mdoc macros display for
>
> .Ex -std uuencode uudecode b64encode b64decode
>
> EXIT STATUS
> The uuencode, uudecode, b64encode, and b64decode utilities [...]
>
> I think the "," before "and" is not intended.
It is both intended, and
20 matches
Mail list logo
