Browse Source

Fix spacing after e.g. and i.e. in the guide

Carsten Dominik 14 years ago
parent
commit
b7cfc159a3
1 changed files with 8 additions and 20 deletions
  1. 8 20
      doc/orgguide.texi

+ 8 - 20
doc/orgguide.texi

@@ -24,18 +24,6 @@
 @iftex
 @c @hyphenation{time-stamp time-stamps time-stamp-ing time-stamp-ed}
 @end iftex
-@macro Ie {}
-I.e.,
-@end macro
-@macro ie {}
-i.e.,
-@end macro
-@macro Eg {}
-E.g.,
-@end macro
-@macro eg {}
-e.g.,
-@end macro
 
 @c Subheadings inside a table.
 @macro tsubheading{text}
@@ -401,7 +389,7 @@ Show all, including drawers.
 @end table
 
 When Emacs first visits an Org file, the global state is set to
-OVERVIEW, i.e. only the top level headlines are visible.  This can be
+OVERVIEW, i.e.@: only the top level headlines are visible.  This can be
 configured through the variable @code{org-startup-folded}, or on a
 per-file basis by adding a startup keyword @code{overview}, @code{content},
 @code{showall}, like this:
@@ -1455,7 +1443,7 @@ be listed on that date after it has been marked DONE.  If you don't like
 this, set the variable @code{org-agenda-skip-scheduled-if-done}.}.  In
 addition, a reminder that the scheduled date has passed will be present
 in the compilation for @emph{today}, until the entry is marked DONE.
-I.e. the task will automatically be forwarded until completed.
+I.e.@: the task will automatically be forwarded until completed.
 
 @smallexample
 *** TODO Call Trillian for a date on New Years Eve.
@@ -2259,7 +2247,7 @@ include your @file{.emacs} file, you could use:
 #+INCLUDE: "~/.emacs" src emacs-lisp
 @end smallexample
 @noindent
-The optional second and third parameter are the markup (e.g. @samp{quote},
+The optional second and third parameter are the markup (e.g.@: @samp{quote},
 @samp{example}, or @samp{src}), and, if the markup is @samp{src}, the
 language for formatting the contents.  The markup is optional, if it is not
 given, the text will be assumed to be in Org mode format and will be
@@ -2327,9 +2315,9 @@ Insert template with export options, see example below.
 #+AUTHOR:      the author (default taken from @code{user-full-name})
 #+DATE:        a date, fixed, of a format string for @code{format-time-string}
 #+EMAIL:       his/her email address (default from @code{user-mail-address})
-#+DESCRIPTION: the page description, e.g. for the XHTML meta tag
-#+KEYWORDS:    the page keywords, e.g. for the XHTML meta tag
-#+LANGUAGE:    language for HTML, e.g. @samp{en} (@code{org-export-default-language})
+#+DESCRIPTION: the page description, e.g.@: for the XHTML meta tag
+#+KEYWORDS:    the page keywords, e.g.@: for the XHTML meta tag
+#+LANGUAGE:    language for HTML, e.g.@: @samp{en} (@code{org-export-default-language})
 #+TEXT:        Some descriptive text to be inserted at the beginning.
 #+TEXT:        Several lines may be given.
 #+OPTIONS:     H:2 num:t toc:t \n:nil @@:t ::t |:t ^:t f:t TeX:t ...
@@ -2511,7 +2499,7 @@ The structure of code blocks is as follows:
 
 Where @code{<name>} is a string used to name the code block,
 @code{<language>} specifies the language of the code block
-(e.g. @code{emacs-lisp}, @code{shell}, @code{R}, @code{python}, etc...),
+(e.g.@: @code{emacs-lisp}, @code{shell}, @code{R}, @code{python}, etc...),
 @code{<switches>} can be used to control export of the code block,
 @code{<header arguments>} can be used to control many aspects of code block
 behavior as demonstrated below, and @code{<body>} contains the actual source
@@ -2596,7 +2584,7 @@ re-run when their inputs have changed.
 A header argument of @code{:noweb yes} will expand ``noweb'' style references
 on evaluation and tangling.
 @item :file
-Code blocks which output results to files (e.g. graphs, diagrams and figures)
+Code blocks which output results to files (e.g.@: graphs, diagrams and figures)
 can accept a @code{:file filename} header argument in which case the results
 are saved to the named file, and a link to the file is inserted into the
 Org-mode buffer.