Manuel Giraud <manuel.gir...@univ-nantes.fr> writes:
> Manuel Giraud <manuel.gir...@univ-nantes.fr> writes:
>
>> But AFAIU, with org-export-prefer-native-exporter-for-tables to nil,
>> simple table stays in HTML, no?
> ^^^^
> simple
Our understanding matches. For the sake of clarity, here it is:
For simple tables,
1. org-export-prefer-native-exporter-for-tables => Non-nil => Use the
HTML code generator in table.el => HTML *source code* has Lots of
 
2. org-export-prefer-native-exporter-for-tables => nil => Use Org's own
code generator => HTML *source code* is easy to look at.
If I consult my patch, I see that the outputs I have included for the
simple table.el table (with both the on/off options for
org-export-prefer-native-exporter-for-tables) is consistent with what is
set forth in the previous paragraph.
May be you are exporting a different table.el table? Can you post your
example? With point within a simple table.el-table, the elisp form down
below should eval to false. Is it any different in your setting?
#+begin_src emacs-lisp
(let* ((dim (table-query-dimension))
(c (nth 4 dim)) (r (nth 5 dim)) (cells (nth 6 dim)))
(not (= (* c r) cells)))
#+end_src
It is possible that I have misunderstood how table-query-dimension API
works ...
Footnotes:
[1] http://patchwork.newartisans.com/patch/764/
Tip: Search for post-patch, Table.el Table with no Spanning,
org-export-prefer-native-exporter-for-tables
Jambunathan K.
