On 2021-01-14, Ulrich Lauther wrote:
> On Thu, Jan 14, 2021 at 06:01:33AM +, Dorai Sitaram via wrote:
>> I'm used to single-spacing by now, given its ubiquity, but surely the
>> Germans carry their disdain for typographic breathing space a little too
>> far? As in the posted article,
On Thu, Jan 14, 2021 at 06:01:33AM +, Dorai Sitaram via wrote:
> I'm used to single-spacing by now, given its ubiquity, but surely the
> Germans carry their disdain for typographic breathing space a little too far?
> As in the posted article, paragraphs are difficult to visually separate,
I'm used to single-spacing by now, given its ubiquity, but surely the Germans
carry their disdain for typographic breathing space a little too far? As in the
posted article, paragraphs are difficult to visually separate, lacking as they
do both leading horizontal indentation and vertical
On Thu, 7 Jan 2021, John A. wrote:
Make lines short, and break lines at natural places, such as after
commas and semicolons, rather than randomly.
I've been an avid sentence-line-breaker before, but I've now started to
apply Kernigan's method, and it is very liberating, and much easier to
Karthik Suresh (2020-12-20) dixit:
[...] Start each sentence on a new line.
Make lines short, and break lines at natural places, such as after
commas and semicolons, rather than randomly. Since most people change
documents by rewriting phrases and adding, deleting and rearranging
sentences,
Hi, Doug!
At 2020-12-22T09:33:20-0500, M Douglas McIlroy wrote:
> The words about double spacing quoted below can be misread as
> unconditional advice. I suggest replacing "In" with "In this case".
>
> Also so much mention of AT strikes me as clutter. At least the first
> instance would better
On 12/22/20, Peter Schaffter wrote:
> So, yes, it's worth re-working the info .ss entry. Perhaps begin
> with something like: "Change the size of the space between words
> and sentences. The space between sentences is derived by adding
> WORD_SPACE_SIZE and SENTENCE_SPACE_SIZE. Thus '.ss 12 0'
On Tue, Dec 22, 2020, John Gardner wrote:
> I condemn two spaces, period.
Having gotten bitten by the who-says-what-where bug concerning
double-spaced sentences, I re-read my own documentation for the .SS
macro in mom. Seems to me I covered all the bases:
"Typeset copy should never have two
On Tue, Dec 22, 2020, Dave Kemper wrote:
> It seemed a minor thing before, but now that it's tripped up the
> author of possibly the most elaborate macro package published in
> the roff language's 50-year history, I wonder if that's worth
> revisiting.
Being said author, I can confirm that yes, I
On Tue, 22 Dec 2020 16:21:35 +1100
"G. Branden Robinson" wrote:
> If a second argument is never given to the 'ss' request, GNU
> 'troff' separates sentences as AT 'troff' does.
I think "never" is a long time. Would this be better?
If a second argument is not provided to the
The words about double spacing quoted below can be misread as unconditional
advice. I suggest replacing "In" with "In this case".
Also so much mention of AT strikes me as clutter. At least the first
instance would better be dropped.
"If a second argument is never given to the 'ss' request, GNU
>
> It was neither the only, first, last, or most vituperous critique of Two
> Spaces: There has been a rising tide of condemnation of the practice in the
> media, as shown by Googling "two spaces after period".
>
I condemn two spaces, period.
Worst\. Indentation style\. Ever.
On Tue, 22 Dec
On 12/21/20, G. Branden Robinson wrote:
> I thought you and I worked to fix this earlier this year?
We did do some work in this section, but I don't recall addressing
this terminology in particular. At the time, it seemed pretty small
potatoes.
Taken as a whole, I believe the section is
At 2020-12-21T17:07:10-0600, Dave Kemper wrote:
> On 12/20/20, Peter Schaffter wrote:
> > Perhaps I should have been more verbose and written: According
> > to the info(1) manual, initially both the WORD_SPACE_SIZE and
> > SENTENCE_SPACE_SIZE are 12; since this prevents SS from being larger
> >
> According to the info(1) manual, initially both the WORD_SPACE_SIZE and
> SENTENCE_SPACE_SIZE are 12; since this prevents SS from being larger
> than WS, it effectively disables sentence spacing
A careful reading reveals that the second argument of .ss is *extra*
spacing, so
the default
On Tue, Dec 22, 2020, Tadziu Hoffmann wrote:
> For those who have not read it yet: the original
>
> http://www.heracliteanriver.com/?p=324
>
> has unfortunately vanished, but I have saved a copy:
>
> http://www.usm.uni-muenchen.de/~hoffmann/roff/tmp/typographyspacing.pdf
Thank you! I
> [...] at least it felt like I was being individually targeted,
> so I promptly wilted. I mean of course the famous
>
> https://slate.com/technology/2011/01/two-spaces-after-a-period-why-you-should-never-ever-do-it.html
For those who have not read it yet: the original
On 12/20/20, Peter Schaffter wrote:
> Perhaps I should have been more verbose and written: According
> to the info(1) manual, initially both the WORD_SPACE_SIZE and
> SENTENCE_SPACE_SIZE are 12; since this prevents SS from being larger
> than WS, it effectively disables sentence spacing.
On Sun, Dec 20, 2020, Dorai Sitaram via wrote:
> I'm not completely sure it's true for all modern applications,
> but I hope you're right that it doesn't hurt in general to
> explicitly type two spaces after a sentence. As a dinosaur,
> that's what I used to do, but trained myself out of it
On Sat, Dec 19, 2020, Dave Kemper wrote:
> I think you're confusing starting every sentence on its own line with
> using newlines nowhere *except* between sentences.
You are right. My distaste for hitting return instead of space
after a period clouded my reading of the advice. :)
> >
> I'm not completely sure it's true for all modern applications, but I
> hope you're right that it doesn't hurt in general to explicitly type
> two spaces after a sentence. As a dinosaur, that's what I used to
> do, but trained myself out of it after reading a high-profile tirade
> scolding me
I'm not completely sure it's true for all modern applications, but I hope
you're right that it doesn't hurt in general to explicitly type two spaces
after a sentence. As a dinosaur, that's what I used to do, but trained myself
out of it after reading a high-profile tirade scolding me (at least
On Sat, 19 Dec 2020, Karthik Suresh wrote:
First, when you do the purely mechanical operations of typing, type
so subsequent editing will be easy. Start each sentence on a new line.
Make lines short, and break lines at natural places, such as after
commas and semicolons, rather than
On 19/12/2020 22:36, James K. Lowden wrote:
On Sat, 19 Dec 2020 20:18:19 +
Karthik Suresh wrote:
I think it's also the advice Brian Kernighan gives about breaking
at natural phrase points in the text as we tend to edit a phrase at a
time.
I hadn't heard that. Do you know where you
On Sat, 19 Dec 2020 20:18:19 +
Karthik Suresh wrote:
> I think it's also the advice Brian Kernighan gives about breaking
> at natural phrase points in the text as we tend to edit a phrase at a
> time.
I hadn't heard that. Do you know where you read it?
A had a college professor who
On 12/19/20, Peter Schaffter wrote:
> On Sat, Dec 19, 2020, Ulrich Lauther wrote:
>> In my opinion it is good style to start every sentence on a new
>> source line.
>
> A piece of advice I have been happily ignoring since sometime back
> in the 90s.
...
> This is the the first paragraph of _Bleak
On 12/19/20, Dorai Sitaram wrote:
> groff pretty much forces one to use two spaces after sentence-ending
> punctuation, unless it's at the end of a source line. Is there a way to
> avoid this, so that the space is uniform regardless of whether the ending
> punctuation occurs mid- or end-line?
In my opinion it is good style to start every sentence on a new
source line.
A piece of advice I have been happily ignoring since sometime back
in the 90s. Certain kinds of texts (scientific, technical) and the
ways they are to be used (e.g. one off, or formatted for multiple media
types
I've been using a simple solution successfully for years.
In my own macros I wrote and use, I include the troff/groff provision
for specifying the end-of-sentence ratio
as follows: " .ss 12 20"
End-of-sentence identified by two space characters creates a space equal
to normal space times
Ha! Glad I'm not the only one who is driven up the wall by newlines at the end
of every sentence. I've heard this policy touted so many times by folk who are
obviously expert (even those who don't troff), and I have no doubt at all it
works for them.
I just can't read or edit it to save my
On Sat, Dec 19, 2020, Ulrich Lauther wrote:
> On Sat, Dec 19, 2020 at 10:27:01AM +, Dorai Sitaram wrote:
> > groff pretty much forces one to use two spaces after
> > sentence-ending punctuation, unless it's at the end of a source
> > line.
>
> In my opinion it is good style to start every
Maybe you can look at the . ss request
Which sets interword spacing as first argument and the second argument as
sentence space
Kind regards
Wim Stockman
Op za 19 dec. 2020 13:36 schreef Oliver Corff :
> Hi Dorai,
>
> the point behind the end-of-source-line rule is simple, and is hidden in
>
Hi Dorai,
the point behind the end-of-source-line rule is simple, and is hidden in
many introductory chapters of textbooks on troff and groff: You are not
forced (and even less encouraged) to preempt any formatting in your
input text. None of your efforts with regard to line length, intended
On Sat, 19 Dec 2020, Ulrich Lauther wrote:
On Sat, Dec 19, 2020 at 10:27:01AM +, Dorai Sitaram wrote:
groff pretty much forces one to use two spaces after sentence-ending
punctuation, unless it's at the end of a source line.
In my opinion it is good style to start every sentence on a
On Sat, Dec 19, 2020 at 10:27:01AM +, Dorai Sitaram wrote:
> groff pretty much forces one to use two spaces after sentence-ending
> punctuation, unless it's at the end of a source line.
In my opinion it is good style to start every sentence on a new source line.
This is helpful for editing
groff pretty much forces one to use two spaces after sentence-ending
punctuation, unless it's at the end of a source line. Is there a way to avoid
this, so that the space is uniform regardless of whether the ending punctuation
occurs mid- or end-line? (I could resign myself to always type 2
36 matches
Mail list logo
