Nicolas Goaziou writes: > Jon Miller <joneb...@gmail.com> writes: > >> At this point, I'm not sure if there is any further hacking left to be done >> to the original patch I sent? Are we okay with just leaving the two options >> of 'ascii and 'org? > > I don't think we're at a conclusion yet. In addition to providing ascii > and org, we might also > > - provide org, ascii, latin-1 and utf8 > - provide any symbol that will be understood as an export back-end > > WDYT?
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. - 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? -- Jon Miller
