Jon Miller <joneb...@gmail.com> writes: > I'm willing to help hack out a solution. I just need a hint to help me > along. > > - I specifically do not know how to produce a latin1 or utf8 export via the > existing `org-export-string-as' function call that is being used.
Use EXT-PLIST argument, e.g., (org-export-string-as string 'ascii nil '(:ascii-charset utf-8)) (org-export-string-as string 'ascii nil '(:ascii-charset latin1)) (org-export-string-as string 'ascii nil '(:ascii-charset ascii)) > - As for updating the parameter to support any valid back-end, I assume that > means updating the defcustom from a choice list to a symbol that is then > later checked as a valid back-end and defaults to a simple choice when it > is non-valid? We could accept any symbol, try to (require 'ox-SYMBOL) and then (org-export-string-as string SYMBOL) Regards,
