[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[6722] ending and not ending a sentence documentation
From: |
Gavin D. Smith |
Subject: |
[6722] ending and not ending a sentence documentation |
Date: |
Sat, 24 Oct 2015 17:23:43 +0000 |
Revision: 6722
http://svn.sv.gnu.org/viewvc/?view=rev&root=texinfo&revision=6722
Author: gavin
Date: 2015-10-24 17:23:42 +0000 (Sat, 24 Oct 2015)
Log Message:
-----------
ending and not ending a sentence documentation
Modified Paths:
--------------
trunk/ChangeLog
trunk/doc/texinfo.texi
Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog 2015-10-23 12:46:37 UTC (rev 6721)
+++ trunk/ChangeLog 2015-10-24 17:23:42 UTC (rev 6722)
@@ -1,3 +1,16 @@
+2015-10-24 Gavin Smith <address@hidden>
+
+ * doc/texinfo.texi (Not Ending a Sentence): Remove example of
+ incorrect input to make it easy to spot the correct input. Add
+ '@findex :'. Remove mention of typing on a typewriter. Change
+ an "or" to a comma. Be more explicit about which case is which
+ for when the extra space is wanted. Remove words "after a
+ period" when we mentioned earlier in the sentence other
+ punctuation marks than the period. Use a numbered list of
+ situations where @: should be used. Move mention of HTML and
+ DocBook output to end of node. Mention a trick to remember
+ whether we are forcing an end of sentence or suppressing one.
+
2015-10-23 Gavin Smith <address@hidden>
* doc/texinfo.texi (Indexing Commands): Update to mention
Modified: trunk/doc/texinfo.texi
===================================================================
--- trunk/doc/texinfo.texi 2015-10-23 12:46:37 UTC (rev 6721)
+++ trunk/doc/texinfo.texi 2015-10-24 17:23:42 UTC (rev 6722)
@@ -9847,62 +9847,62 @@
@cindex Sentence non-ending punctuation
@cindex Periods, inserting
@cindex Spacing, in the middle of sentences
-Depending on whether a period or exclamation point or question mark is
-inside or at the end of a sentence, slightly less or more space is
-inserted after a period in a typeset manual. Since it is not always
-possible to determine automatically when a period ends a sentence,
-special commands are needed in some circumstances. Usually, Texinfo
-can guess how to handle periods, so you do not need to use the special
-commands; you just enter a period as you would if you were using a
-typewriter: put two spaces after the period, question mark, or
-exclamation mark that ends a sentence.
+When a period, exclamation point or question mark is
+at the end of a sentence, slightly more space is
+inserted after it in a typeset manual.
@findex <colon> @r{(suppress end-of-sentence space)}
address@hidden :
+Usually, Texinfo can determine automatically when a period ends a
+sentence. However, special commands are needed in some circumstances.
Use the @code{@@:} command after a period, question mark, exclamation
-mark, or colon that should not be followed by extra space. For
-example, use @code{@@:} after periods that end (lowercase)
-abbreviations which are not at the ends of sentences.
+mark or colon that should not be followed by extra space. This is
+necessary in the following situations:
-Also, when a parenthetical remark in the middle of a sentence (like
-this one!)@: ends with a period, exclamation point, or question mark,
address@hidden
address@hidden After a period that ends a lowercase abbreviation which is not
at
+the end of a sentences.
+
address@hidden When a parenthetical remark in the middle of a sentence (like
+this one!)@: ends with a period, exclamation point or question mark,
@code{@@:} should be used after the right parenthesis. Similarly for
right brackets and right quotes (both single and double).
address@hidden enumerate
-For example,
+For example:
@example
-foo vs.@@: bar (or?)@@: baz
-foo vs. bar (or?) baz
address@hidden vs.@@: bar (or?)@@: baz},
@end example
@noindent
address@hidden
-produces
address@hidden ifnottex
address@hidden
-produces the following. If you look carefully at this printed output,
-you will see a bit of extraneous space after the @samp{vs.}@: and
address@hidden(or?)}@: in the second line.
address@hidden iftex
+The first line below shows the output, and for comparison, the second
+line shows the spacing when the @samp{@@:} commands were not used.
@quotation
foo vs.@: bar (or?)@: address@hidden
foo vs. bar (or?) baz
@end quotation
address@hidden
address@hidden@@:} has no effect on the HTML or Docbook output.
address@hidden
+If you look carefully, you will see a bit of extraneous space after the
address@hidden@: and @samp{(or?)}@:.
address@hidden iftex
-Do not put braces after @code{@@:} (or any non-alphabetic command).
+It may help you to remember what @code{@@:} does by imagining that it
+stands for an invisible lower-case character that stops a word ending in
+a period.
A few Texinfo commands force normal interword spacing, so that you
don't have to insert @code{@@:} where you otherwise would. These are
the code-like highlighting commands, @code{@@var}, @code{@@abbr}, and
@code{@@acronym} (@pxref{Useful Highlighting}). For example, in
address@hidden@@address@hidden address@hidden the period is not considered the
end of a
address@hidden@@address@hidden address@hidden the period is not considered to
be the end of a
sentence, and no extra space is inserted.
address@hidden@@:} has no effect on the HTML or Docbook output.
+
@node Ending a Sentence
@subsection Ending a Sentence
@@ -9953,7 +9953,11 @@
The meanings of @code{@@:} and @code{@@.}, etc.@: in Texinfo are
designed to work well with the Emacs sentence motion commands
-(@pxref{Sentences,,, emacs, The GNU Emacs Manual}).
+(@pxref{Sentences,,, emacs, The GNU Emacs Manual}). It may help to
+imagine that the @samp{@@} in @samp{@@.}, etc., is an invisible
+lower-case letter `a' which makes an upper-case letter before it
+immaterial for the purposes of deciding whether the period ends the
+sentence.
A few Texinfo commands are not considered as being an abbreviation,
even though they may end with a capital letter when expanded, so that
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [6722] ending and not ending a sentence documentation,
Gavin D. Smith <=