|
|
@@ -948,7 +948,7 @@ description on Worg}.
|
|
|
Installing Info files is system dependent, because of differences in the
|
|
|
@file{install-info} program. The Info documentation is installed together
|
|
|
with the rest of Org mode. If you don't install Org mode, it is possible to
|
|
|
-install the Info documentation seperately (you need to have
|
|
|
+install the Info documentation separately (you need to have
|
|
|
install-info@footnote{The output from install-info (if any) is system
|
|
|
dependent. In particular Debian and its derivatives use two different
|
|
|
versions of install-info and you may see the message:
|
|
|
@@ -14893,7 +14893,7 @@ buffer, most useful for specifying the allowed values of a property.
|
|
|
@item #+SETUPFILE: file
|
|
|
This line defines a file that holds more in-buffer setup. Normally this is
|
|
|
entirely ignored. Only when the buffer is parsed for option-setting lines
|
|
|
-(i.e.@: when starting Org mode for a file, when pressing @kbd{C-c C-c} in a
|
|
|
+(i.e., when starting Org mode for a file, when pressing @kbd{C-c C-c} in a
|
|
|
settings line, or when exporting), then the contents of this file are parsed
|
|
|
as if they had been included in the buffer. In particular, the file can be
|
|
|
any other Org mode file with internal setup. You can visit the file the
|
|
|
@@ -15255,7 +15255,7 @@ example using the color @code{grey90} on a white background.
|
|
|
Things become cleaner still if you skip all the even levels and use only odd
|
|
|
levels 1, 3, 5..., effectively adding two stars to go from one outline level
|
|
|
to the next@footnote{When you need to specify a level for a property search
|
|
|
-or refile targets, @samp{LEVEL=2} will correspond to 3 stars, etc@.}. In this
|
|
|
+or refile targets, @samp{LEVEL=2} will correspond to 3 stars, etc.}. In this
|
|
|
way we get the outline view shown at the beginning of this section. In order
|
|
|
to make the structure editing and export commands handle this convention
|
|
|
correctly, configure the variable @code{org-odd-levels-only}, or set this on
|
|
|
@@ -15346,7 +15346,7 @@ names for natural constants or units. Instead of defining your own
|
|
|
constants in the variable @code{org-table-formula-constants}, install
|
|
|
the @file{constants} package which defines a large number of constants
|
|
|
and units, and lets you use unit prefixes like @samp{M} for
|
|
|
-@samp{Mega}, etc@. You will need version 2.0 of this package, available
|
|
|
+@samp{Mega}, etc. You will need version 2.0 of this package, available
|
|
|
at @url{http://www.astro.uva.nl/~dominik/Tools}. Org checks for
|
|
|
the function @code{constants-get}, which has to be autoloaded in your
|
|
|
setup. See the installation instructions in the file
|
|
|
@@ -16780,7 +16780,7 @@ on @file{org-element.el} and @file{org-export.el} has been outstanding, and
|
|
|
opened the doors for many new ideas and features.
|
|
|
|
|
|
@item Jambunathan K
|
|
|
-Jambunathan contributed the ODT exporter, definitly a killer feature of
|
|
|
+Jambunathan contributed the ODT exporter, definitely a killer feature of
|
|
|
Org mode. He also contributed the new HTML exporter, which is another core
|
|
|
feature of Org. Here too, I knew I could rely on him to fix bugs in these
|
|
|
areas and to patiently explain the users what was the problems and solutions.
|
|
|
@@ -16788,7 +16788,7 @@ areas and to patiently explain the users what was the problems and solutions.
|
|
|
@item Achim Gratz
|
|
|
Achim rewrote the building process of Org, turning some @emph{ad hoc} tools
|
|
|
into a flexible and conceptually clean process. He patiently coped with the
|
|
|
-many hicups that such a change can create for users.
|
|
|
+many hiccups that such a change can create for users.
|
|
|
|
|
|
@item Nick Dokos
|
|
|
The Org mode mailing list would not be such a nice place without Nick, who
|
Bastien Guerry