From: Nicolas Goaziou <n.goaziou@gmail.com>
To: William Crandall <bc3141592@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: Drupal syntax on html-export for image links
Date: Sun, 27 May 2012 09:35:09 +0200 [thread overview]
Message-ID: <87mx4u5b6a.fsf@gmail.com> (raw)
In-Reply-To: <CAENLK5U+rDe8UFHKpZfAUOsXn+O1qDShA7WEC_9brOtRPyFdOA@mail.gmail.com> (William Crandall's message of "Sat, 26 May 2012 21:43:23 -0700")
Hello,
William Crandall <bc3141592@gmail.com> writes:
> Is it true that:
>
> 1. The org-export Package is a "Generic Export Engine"
> and is intended to support a new generation of
> org export tools (to HTML, LaTeX, ODT, etc).
Correct.
> 2. It is now an "experimental" Contributed Package:
> http://orgmode.org/worg/org-contrib
Correct.
> 3. The current (old) export command (C-c C-e) executes
> a function called "org-export" in org-exp.el (line 943)
> but it is not related to the new org-export package.
Correct.
> 4. API documentation for the new org-export, and it's family
> (org-e-ascii.el, org-e-html.el, org-e-latex.el, org-e-odt.el
> org-e-publish.el org-element.el), is here:
> http://orgmode.org/worg/org-api/
Correct, but be warned that some functions in org-exp.el use org-export-*
prefix and might be found under "org-export" section.
> 5. Documentation for back-end developers working on new
> export tools is here:
> http://orgmode.org/worg/dev/org-export-reference.html
Correct.
> 6. Current org tutorials describe the old tool set, e.g.,
> "Publishing Org-mode files to HTML", not the new:
> http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html
Correct.
> 7. No end-user documentation for the org-export package
> has been created, describing for example, how to link
> to an external CSS file (as #+STYLE used to work).
Correct.
> 8. "The Manual" does not (yet) document the org-export package:
> http://orgmode.org/manual/index.html
Correct.
> 9. This mailing list is the best place to ask questions.
Correct.
> Turning to my immediate challenge, exporting to html,
> I have some questions ( M-x org-export-dispatch h ):
Since I don't maintain `e-html' back-end, I'll only answer partially.
> 5. Removing Pre- and Postamble
>
> What now works like:
>
> (setq org-export-html-preamble nil)
> (setq org-export-html-postamble nil)
>
> Now, there is no preamble.
>
> The postamble is:
>
> <div id="postamble">
> <p class="date"> Date: 2012-05-26 20:59:51 Pacific Daylight Time </p>
> <p class="author"> Author : William BC Crandall</p>
> <p class="creator"> Generated by Org mode 7.8.11 in Emacs 24.1.50.1. </p>
> <a href="http://validator.w3.org/check?uri=referer">Validate XHTML
> 1.0</a>
> </div>
>
> I'd like to remove both.
You may have a look at `org-e-html-preamble' and `org-e-html-postamble'
variables.
> --------------------------------------------------
>
>
> 6. Special strings
>
> I was able to get a TM (&trade) in the old system with:
>
> (eval-after-load "org"
> '(setq org-export-html-special-string-regexps
> (append org-export-html-special-string-regexps
> '(("-TM-" . "™")))))
>
> How now?
You can add a filter to plain text objects, which will only be applied
to `e-html' back-end:
#+begin_src emacs-lisp
(defun my-html-trademark-markup (text backend info)
(if (not (eq back-end 'e-html)) text
(replace-regexp-in-string "-TM-" "™" text)))
(add-to-list 'org-export-filter-plain-text-functions
'my-html-trademark-markup)
#+end_src
Though, I would suggest to use entity \trade instead.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-05-27 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 4:55 Drupal syntax on html-export for image links William Crandall
2012-05-24 9:01 ` Bastien
2012-05-27 4:43 ` William Crandall
2012-05-27 7:35 ` Nicolas Goaziou [this message]
2012-05-27 12:41 ` Jambunathan K
2012-05-27 12:37 ` Jambunathan K
2012-05-27 16:00 ` William Crandall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mx4u5b6a.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bc3141592@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).