Thank you very much. Ihor Radchenko <yanta...@posteo.net> writes:
> Sébastien Gendre <s...@k-7.ch> writes: > >> I have attached, to this e-mail, the corrected patch that include your >> requests. > > Thanks! > Applied, onto main, with minor amendments to the manual text. > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=26bbffb280 > > I also added you to the contributor list. > https://git.sr.ht/~bzg/worg/commit/48ab759e > >>> In fact, it may be a good idea to go through all the built-in backends >>> and provide OPTIONS/KEYWORD values for more export options. >> >> I could do that, at least for the HTML backend. And maybe the LaTeX one. > >> Is it possible for an option to have an OPTIONS and a KEYWORD ? > > Yes. > Check out `org-export-get-environment' and > `org-export--get-inbuffer-options' for code details. > >> For example the preamble. It already have an OPTION, but it's mostly to >> enable/disable it with `t' or `nil'. And maybe set it to a function >> name. But if a user want to set a preamble as a multi-lines string, it >> could be difficult with an OPTION. > > I agree that having both OPTION and KEYWORD would make sense in such scenario. > >> Maybe I can modify the preamble option to accept a file as a value. Like >> `(file "./preamble.html")'. If the file is an HTML, it's content is used >> in the preamble. If the file is an Org-mode file, it's body only is >> exported as HTML and then it is inserted as the preamble. And same with >> the postamble. What do you think. > > I do not object, but that would be a separate feature. > >> PS: I am still working on the search engine support for Org-publish to >> HTML. But I wanted to understand more how the Export/Pubilsh work >> before. > > Check out https://orgmode.org/manual/Advanced-Export-Configuration.html > for the complete export process flow. Commentary in ox.el source code is > also helpful.
signature.asc
Description: PGP signature
