Browse Source

Fix more instances of missing dashes.

Bastien Guerry 13 years ago
parent
commit
c846f024c1
1 changed files with 25 additions and 25 deletions
  1. 25 25
      doc/org.texi

+ 25 - 25
doc/org.texi

@@ -985,7 +985,7 @@ default.  If you are using an earlier version of Emacs, add this line to your
 (add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode))
 (add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode))
 @end lisp
 @end lisp
 
 
-Org mode buffers need font-lock to be turned on - this is the default in
+Org mode buffers need font-lock to be turned on: this is the default in
 Emacs@footnote{If you don't use font-lock globally, turn it on in Org buffer
 Emacs@footnote{If you don't use font-lock globally, turn it on in Org buffer
 with @code{(add-hook 'org-mode-hook 'turn-on-font-lock)}}.
 with @code{(add-hook 'org-mode-hook 'turn-on-font-lock)}}.
 
 
@@ -2686,7 +2686,7 @@ computations in Lisp:
   '(concat (substring $1 1 2) (substring $1 0 1) (substring $1 2))
   '(concat (substring $1 1 2) (substring $1 0 1) (substring $1 2))
 @r{Add columns 1 and 2, equivalent to Calc's @code{$1+$2}}
 @r{Add columns 1 and 2, equivalent to Calc's @code{$1+$2}}
   '(+ $1 $2);N
   '(+ $1 $2);N
-@r{Compute the sum of columns 1-4, like Calc's @code{vsum($1..$4)}}
+@r{Compute the sum of columns 1--4, like Calc's @code{vsum($1..$4)}}
   '(apply '+ '($1..$4));N
   '(apply '+ '($1..$4));N
 @end example
 @end example
 
 
@@ -3375,7 +3375,7 @@ buffer:
 For Org files, if there is a @samp{<<target>>} at the cursor, the link points
 For Org files, if there is a @samp{<<target>>} at the cursor, the link points
 to the target.  Otherwise it points to the current headline, which will also
 to the target.  Otherwise it points to the current headline, which will also
 be the description@footnote{If the headline contains a timestamp, it will be
 be the description@footnote{If the headline contains a timestamp, it will be
-removed from the link and result in a wrong link -- you should avoid putting
+removed from the link and result in a wrong link---you should avoid putting
 timestamp in the headline.}.
 timestamp in the headline.}.
 
 
 @vindex org-link-to-org-use-id
 @vindex org-link-to-org-use-id
@@ -5237,8 +5237,8 @@ same summary information.
 The @code{est+} summary type requires further explanation.  It is used for
 The @code{est+} summary type requires further explanation.  It is used for
 combining estimates, expressed as low-high ranges.  For example, instead
 combining estimates, expressed as low-high ranges.  For example, instead
 of estimating a particular task will take 5 days, you might estimate it as
 of estimating a particular task will take 5 days, you might estimate it as
-5-6 days if you're fairly confident you know how much work is required, or
-1-10 days if you don't really know what needs to be done.  Both ranges
+5--6 days if you're fairly confident you know how much work is required, or
+1--10 days if you don't really know what needs to be done.  Both ranges
 average at 5.5 days, but the first represents a more predictable delivery.
 average at 5.5 days, but the first represents a more predictable delivery.
 
 
 When combining a set of such estimates, simply adding the lows and highs
 When combining a set of such estimates, simply adding the lows and highs
@@ -5248,7 +5248,7 @@ from the sum.  For example, suppose you had ten tasks, each of which was
 estimated at 0.5 to 2 days of work.  Straight addition produces an estimate
 estimated at 0.5 to 2 days of work.  Straight addition produces an estimate
 of 5 to 20 days, representing what to expect if everything goes either
 of 5 to 20 days, representing what to expect if everything goes either
 extremely well or extremely poorly.  In contrast, @code{est+} estimates the
 extremely well or extremely poorly.  In contrast, @code{est+} estimates the
-full job more realistically, at 10-15 days.
+full job more realistically, at 10--15 days.
 
 
 Here is an example for a complete columns definition, along with allowed
 Here is an example for a complete columns definition, along with allowed
 values.
 values.
@@ -6540,7 +6540,7 @@ suggestion.}  for capturing new material.
 @table @kbd
 @table @kbd
 @orgcmd{C-c c,org-capture}
 @orgcmd{C-c c,org-capture}
 Call the command @code{org-capture}.  Note that this keybinding is global and
 Call the command @code{org-capture}.  Note that this keybinding is global and
-not active by default - you need to install it.  If you have templates
+not active by default: you need to install it.  If you have templates
 @cindex date tree
 @cindex date tree
 defined @pxref{Capture templates}, it will offer these templates for
 defined @pxref{Capture templates}, it will offer these templates for
 selection or use a new Org outline node as the default template.  It will
 selection or use a new Org outline node as the default template.  It will
@@ -8118,7 +8118,7 @@ February 1st, @kbd{9 w} to ISO week number 9.  When setting day, week, or
 month view, a year may be encoded in the prefix argument as well.  For
 month view, a year may be encoded in the prefix argument as well.  For
 example, @kbd{200712 w} will jump to week 12 in 2007.  If such a year
 example, @kbd{200712 w} will jump to week 12 in 2007.  If such a year
 specification has only one or two digits, it will be mapped to the interval
 specification has only one or two digits, it will be mapped to the interval
-1938-2037.  @kbd{v @key{SPC}} will reset to what is set in
+1938--2037.  @kbd{v @key{SPC}} will reset to what is set in
 @code{org-agenda-span}.
 @code{org-agenda-span}.
 @c
 @c
 @orgcmd{f,org-agenda-later}
 @orgcmd{f,org-agenda-later}
@@ -8277,7 +8277,7 @@ You can then filter for an effort by first typing an operator, one of
 @kbd{<}, @kbd{>}, and @kbd{=}, and then the one-digit index of an effort
 @kbd{<}, @kbd{>}, and @kbd{=}, and then the one-digit index of an effort
 estimate in your array of allowed values, where @kbd{0} means the 10th value.
 estimate in your array of allowed values, where @kbd{0} means the 10th value.
 The filter will then restrict to entries with effort smaller-or-equal, equal,
 The filter will then restrict to entries with effort smaller-or-equal, equal,
-or larger-or-equal than the selected value.  If the digits 0-9 are not used
+or larger-or-equal than the selected value.  If the digits 0--9 are not used
 as fast access keys to tags, you can also simply press the index digit
 as fast access keys to tags, you can also simply press the index digit
 directly without an operator.  In this case, @kbd{<} will be assumed.  For
 directly without an operator.  In this case, @kbd{<} will be assumed.  For
 application of the operator, entries without a defined effort will be treated
 application of the operator, entries without a defined effort will be treated
@@ -8335,7 +8335,7 @@ selected.
 @tsubheading{Remote editing}
 @tsubheading{Remote editing}
 @cindex remote editing, from agenda
 @cindex remote editing, from agenda
 
 
-@item 0-9
+@item 0--9
 Digit argument.
 Digit argument.
 @c
 @c
 @cindex undoing remote-editing events
 @cindex undoing remote-editing events
@@ -11149,7 +11149,7 @@ files directly, or generate the required styles using an application like
 LibreOffice.  The latter method is suitable for expert and non-expert
 LibreOffice.  The latter method is suitable for expert and non-expert
 users alike, and is described here.
 users alike, and is described here.
 
 
-@subsubsection Applying custom styles - the easy way
+@subsubsection Applying custom styles: the easy way
 
 
 @enumerate
 @enumerate
 @item
 @item
@@ -11162,8 +11162,8 @@ to ODT format.
 
 
 @item
 @item
 Open the above @file{example.odt} using LibreOffice.  Use the @file{Stylist}
 Open the above @file{example.odt} using LibreOffice.  Use the @file{Stylist}
-to locate the target styles - these typically have the @samp{Org} prefix -
-and modify those to your taste.  Save the modified file either as an
+to locate the target styles---these typically have the @samp{Org} prefix---and
+modify those to your taste.  Save the modified file either as an
 OpenDocument Text (@file{.odt}) or OpenDocument Template (@file{.ott}) file.
 OpenDocument Text (@file{.odt}) or OpenDocument Template (@file{.ott}) file.
 
 
 @item
 @item
@@ -11216,8 +11216,8 @@ with a cross-reference and sequence number of the labeled entity.
 @cindex tables, in DocBook export
 @cindex tables, in DocBook export
 
 
 Export of native Org mode tables (@pxref{Tables}) and simple @file{table.el}
 Export of native Org mode tables (@pxref{Tables}) and simple @file{table.el}
-tables is supported.  However, export of complex @file{table.el} tables -
-tables that have column or row spans - is not supported.  Such tables are
+tables is supported.  However, export of complex @file{table.el} tables---tables
+that have column or row spans---is not supported.  Such tables are
 stripped from the exported document.
 stripped from the exported document.
 
 
 By default, a table is exported with top and bottom frames and with rules
 By default, a table is exported with top and bottom frames and with rules
@@ -11349,7 +11349,7 @@ height:width ratio, do the following
 @cindex #+ATTR_ODT
 @cindex #+ATTR_ODT
 You can control the manner in which an image is anchored by setting the
 You can control the manner in which an image is anchored by setting the
 @code{:anchor} property of it's @code{#+ATTR_ODT} line.  You can specify one
 @code{:anchor} property of it's @code{#+ATTR_ODT} line.  You can specify one
-of the the following three values for the @code{:anchor} property -
+of the the following three values for the @code{:anchor} property:
 @samp{"as-char"}, @samp{"paragraph"} and @samp{"page"}.
 @samp{"as-char"}, @samp{"paragraph"} and @samp{"page"}.
 
 
 To create an image that is anchored to a page, do the following:
 To create an image that is anchored to a page, do the following:
@@ -11455,8 +11455,8 @@ or
 @node Labels and captions in ODT export, Literal examples in ODT export, Math formatting in ODT export, OpenDocument Text export
 @node Labels and captions in ODT export, Literal examples in ODT export, Math formatting in ODT export, OpenDocument Text export
 @subsection Labels and captions in ODT export
 @subsection Labels and captions in ODT export
 
 
-You can label and caption various category of objects - an inline image, a
-table, a @LaTeX{} fragment or a Math formula - using @code{#+LABEL} and
+You can label and caption various category of objects---an inline image, a
+table, a @LaTeX{} fragment or a Math formula---using @code{#+LABEL} and
 @code{#+CAPTION} lines.  @xref{Images and tables}.  ODT exporter enumerates
 @code{#+CAPTION} lines.  @xref{Images and tables}.  ODT exporter enumerates
 each labeled or captioned object of a given category separately.  As a
 each labeled or captioned object of a given category separately.  As a
 result, each such object is assigned a sequence number based on order of it's
 result, each such object is assigned a sequence number based on order of it's
@@ -11620,8 +11620,8 @@ the exporter.
 
 
 @item
 @item
 It contains @samp{<text:sequence-decl>}@dots{}@samp{</text:sequence-decl>}
 It contains @samp{<text:sequence-decl>}@dots{}@samp{</text:sequence-decl>}
-elements that control how various entities - tables, images, equations etc -
-are numbered.
+elements that control how various entities---tables, images, equations,
+etc.---are numbered.
 @end enumerate
 @end enumerate
 @end itemize
 @end itemize
 
 
@@ -11755,7 +11755,7 @@ OpenDocument-v1.2 Specification}}
 
 
 
 
 
 
-@subsubheading Custom table styles - an illustration
+@subsubheading Custom table styles: an illustration
 
 
 To have a quick preview of this feature, install the below setting and export
 To have a quick preview of this feature, install the below setting and export
 the table that follows.
 the table that follows.
@@ -11787,7 +11787,7 @@ Template} in @file{OrgOdtContentTemplate.xml}
 (@pxref{x-orgodtcontenttemplate-xml,,Factory styles}).  If you need
 (@pxref{x-orgodtcontenttemplate-xml,,Factory styles}).  If you need
 additional templates you have to define these styles yourselves.
 additional templates you have to define these styles yourselves.
 
 
-@subsubheading Custom table styles - the nitty-gritty
+@subsubheading Custom table styles: the nitty-gritty
 To use this feature proceed as follows:
 To use this feature proceed as follows:
 
 
 @enumerate
 @enumerate
@@ -14801,7 +14801,7 @@ These lines (several are allowed) specify link abbreviations.
 @vindex org-lowest-priority
 @vindex org-lowest-priority
 @vindex org-default-priority
 @vindex org-default-priority
 This line sets the limits and the default for the priorities.  All three
 This line sets the limits and the default for the priorities.  All three
-must be either letters A-Z or numbers 0-9.  The highest priority must
+must be either letters A--Z or numbers 0--9.  The highest priority must
 have a lower ASCII number than the lowest priority.
 have a lower ASCII number than the lowest priority.
 @item #+PROPERTY: Property_Name Value
 @item #+PROPERTY: Property_Name Value
 This line sets a default inheritance value for entries in the current
 This line sets a default inheritance value for entries in the current
@@ -15105,7 +15105,7 @@ indentation shifts by two@footnote{See the variable
 stars but the last one are made invisible using the @code{org-hide}
 stars but the last one are made invisible using the @code{org-hide}
 face@footnote{Turning on @code{org-indent-mode} sets
 face@footnote{Turning on @code{org-indent-mode} sets
 @code{org-hide-leading-stars} to @code{t} and @code{org-adapt-indentation} to
 @code{org-hide-leading-stars} to @code{t} and @code{org-adapt-indentation} to
-@code{nil}.} - see below under @samp{2.} for more information on how this
+@code{nil}.}; see below under @samp{2.} for more information on how this
 works.  You can turn on @code{org-indent-mode} for all files by customizing
 works.  You can turn on @code{org-indent-mode} for all files by customizing
 the variable @code{org-startup-indented}, or you can turn it on for
 the variable @code{org-startup-indented}, or you can turn it on for
 individual files using
 individual files using
@@ -16714,7 +16714,7 @@ a great help, and the list would not be so active without him.
 @end table
 @end table
 
 
 I received support from so many users that it is clearly impossible to be
 I received support from so many users that it is clearly impossible to be
-fair when shortlisting a few of them -- but Org's history would not be
+fair when shortlisting a few of them, but Org's history would not be
 complete if the ones above were not mentioned in this manual.
 complete if the ones above were not mentioned in this manual.
 
 
 @section List of contributions
 @section List of contributions