Oops, I've asked the dumpest question ever in the mailing list :) That's
what happens when working late.
Thanks for reply.
On Thu, Jul 31, 2014 at 4:41 AM, Nicolas Goaziou
wrote:
> Hello,
>
> Nicolas Richard writes:
>
> > Oops, I forgot to remove the verbosity (initially I had wrote it as a
Hello,
Nicolas Richard writes:
> Oops, I forgot to remove the verbosity (initially I had wrote it as a
> (warn ...)). Here's an updated patch.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
> Good idea, as long as `org-export-define-backend' does the same.
Oops, I forgot to remove the verbosity (initially I had wrote it as a
(warn ...)). Here's an updated patch.
>From 117623cec251cd036b601e2481643296cc4e2c37 Mon Sep 17 00:00:00 2001
From: Nicolas Richard
Da
Hello,
Nicolas Richard writes:
> Perhaps org-export-define-derived-backend could do a sanity check that
> all keywords are known.
Good idea, as long as `org-export-define-backend' does the same.
> - (let (blocks filters menu-entry options transcoders contents)
> + (let (blocks filters menu-e
Thorsten Jolitz writes:
> Shiyuan writes:
>> (org-export-define-derived-backend 'my-html-enlish 'html
>> :traslate-alist '((bold . my-org-html-english-bold))
>
>
> :translate-alist ?
Perhaps org-export-define-derived-backend could do a sanity check that
all keywords are known. use-package does t
Shiyuan writes:
> Hi,
> I try to define a new export backend in the new export framework. My
> export backend should behaves like the html except that it transcodes
> *bold* differently. I try to following the Worg tutorial
> http://orgmode.org/worg/dev/org-export-reference.html , ox-html.el and
Hi,
I try to define a new export backend in the new export framework. My
export backend should behaves like the html except that it transcodes
*bold* differently. I try to following the Worg tutorial
http://orgmode.org/worg/dev/org-export-reference.html , ox-html.el and use
org-export-define-d
