The following Elisp code modifies the html export backend so that it accepts an additional option HTML_TABLEEL_ORG.
If you set this option to t or yes table cells in table.el-tables are rendered as org-mode strings.
You can copy the code into your init file if the first line of your init file contains the file-local setting lexical-binding: t as ...
As mentioned in my comment, there are tags that can be used to control the export of a (sub)tree: a tree that is tagged "noexport" will (by default) not be exported: e.g.
** Exported section
This section is not tagged, so it will be exported by default.
** Hidden section :noexport:
Change the syntax of character - from symbol to punctuation in org-mode.
You can do that by:
(defun my-org-change-minus-syntax-fun ()
(modify-syntax-entry ?- "."))
(add-hook 'org-mode-hook #'my-org-change-minus-syntax-fun)
You can add these lines to your init file.
Note that I have running that setup for ages now with no relevant negative effects.
The doc you linked says:
You may also use properties TABLE_EXPORT_FILE and TABLE_EXPORT_FORMAT to specify the file name and the format for table export in a subtree.
They are properties and not keywords. So you set them in the properties drawer of the subtree.
* Section with table
I don't know if this is proper, but here is a version that seems close. The idea is to use a copy of the buffer to insert it, and convert it to html. There result seems to get wrapped in <p></p>, but maybe you can use a substring to get rid of these.
(defun tv/org-string-to-html (string &optional macros)
(if (or (not string) (string-empty-...
Export to pdf is handled by LaTeX, and org-mode only manages a small subset of the possible options. EXAMPLE blocks are exported as verbatim environments, which will change none of your text - it respects all your whitespace, but will not process any macros (such as your subscripts).
On the other hand, quote blocks are exported as quote environments. These ...
For reference I found this message on the org-mode mailing list which mentions a way to do this by means of file local #+LATEX_HEADER lines which use the fancyvrb package and redefine the verbatim environment that org-mode #+RESULTS blocks get exported to via: