org.texi (Publishing action, Complex example): Fix names of publishing functions
* org.texi (Publishing action, Complex example): Fix names of publishing functions.
This commit is contained in:
parent
bfa47dcb94
commit
63260d0a73
|
@ -12011,12 +12011,12 @@ and @code{:exclude}.
|
|||
Publishing means that a file is copied to the destination directory and
|
||||
possibly transformed in the process. The default transformation is to export
|
||||
Org files as HTML files, and this is done by the function
|
||||
@code{org-publish-org-to-html} which calls the HTML exporter (@pxref{HTML
|
||||
@code{org-html-publish-to-html} which calls the HTML exporter (@pxref{HTML
|
||||
export}). But you also can publish your content as PDF files using
|
||||
@code{org-publish-org-to-pdf}, or as @code{ascii}, @code{latin1} or
|
||||
@code{org-latex-publish-to-pdf}, or as @code{ascii}, @code{latin1} or
|
||||
@code{utf8} encoded files using the corresponding functions. If you want to
|
||||
publish the Org file itself, but with @i{archived}, @i{commented}, and
|
||||
@i{tag-excluded} trees removed, use @code{org-publish-org-to-org} and set the
|
||||
@i{tag-excluded} trees removed, use @code{org-org-publish-to-org} and set the
|
||||
parameters @code{:plain-source} and/or @code{:htmlized-source}. This will
|
||||
produce @file{file.org} and @file{file.org.html} in the publishing
|
||||
directory@footnote{@file{file-source.org} and @file{file-source.org.html} if
|
||||
|
@ -12369,7 +12369,7 @@ right place on the web server, and publishing images to it.
|
|||
:base-directory "~/org/"
|
||||
:base-extension "org"
|
||||
:publishing-directory "/ssh:user@@host:~/html/notebook/"
|
||||
:publishing-function org-publish-org-to-html
|
||||
:publishing-function org-html-publish-to-html
|
||||
:exclude "PrivatePage.org" ;; regexp
|
||||
:headline-levels 3
|
||||
:section-numbers nil
|
||||
|
|
Loading…
Reference in New Issue