Browse Source

Update example :publishing-function names in manual

* doc/org-manual.org (Publishing action): Fix references to
org-latex-publish-to-pdf and org-org-publish-to-org.
Greg Minshall 4 years ago
parent
commit
d156399445
1 changed files with 2 additions and 2 deletions
  1. 2 2
      doc/org-manual.org

+ 2 - 2
doc/org-manual.org

@@ -15771,12 +15771,12 @@ and possibly transformed in the process.  The default transformation
 is to export Org files as HTML files, and this is done by the function
 is to export Org files as HTML files, and this is done by the function
 ~org-html-publish-to-html~ which calls the HTML exporter (see [[*HTML
 ~org-html-publish-to-html~ which calls the HTML exporter (see [[*HTML
 Export]]).  But you can also publish your content as PDF files using
 Export]]).  But you can also publish your content as PDF files using
-~org-publish-org-to-pdf~, or as ASCII, Texinfo, etc., using the
+~org-latex-publish-to-pdf~, or as ASCII, Texinfo, etc., using the
 corresponding functions.
 corresponding functions.
 
 
 If you want to publish the Org file as an =.org= file but with
 If you want to publish the Org file as an =.org= file but with
 /archived/, /commented/, and /tag-excluded/ trees removed, use
 /archived/, /commented/, and /tag-excluded/ trees removed, use
-~org-publish-org-to-org~.  This produces =file.org= and put it in the
+~org-org-publish-to-org~.  This produces =file.org= and put it in the
 publishing directory.  If you want a htmlized version of this file,
 publishing directory.  If you want a htmlized version of this file,
 set the parameter ~:htmlized-source~ to ~t~.  It produces
 set the parameter ~:htmlized-source~ to ~t~.  It produces
 =file.org.html= in the publishing directory[fn:140].
 =file.org.html= in the publishing directory[fn:140].