emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [odt] htmlfontify + Support for src blockfontification
Date: Fri, 19 Aug 2011 18:19:04 +0530	[thread overview]
Message-ID: <81aab5k1mn.fsf@gmail.com> (raw)
In-Reply-To: <81liupk2of.fsf@gmail.com> (Jambunathan K.'s message of "Fri, 19 Aug 2011 17:56:24 +0530")

[-- Attachment #1: Type: text/plain, Size: 563 bytes --]

Jambunathan K <kjambunathan@gmail.com> writes:

>> Hi Jambunathan,
>>
>> we are discussing in abstract terms, and that might distract us from
>> DTRT together: can you show the patched version of htmlfontify.el?
>
> Here you go.
>
> Patch numbered 1 is the base htmlfontify.el (same as that in emacs-24
> trunk). I am also attaching a final copy of htmlfontify.el after it has
> gone through the series of 5 patches.

Sample test.org file to quickly understand the nature of changes. A line
by line comparison will show how patches add up.

> Jambunathan K.

-- 

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: test.org --]
[-- Type: text/x-org, Size: 959 bytes --]

* Example 1
#+begin_src emacs-lisp
  ;; This is how one changes load-path
  (setq load-path (cons "~/elisp" load-path))
#+end_src

* COMMENT This is how ODT output looks like

#+begin_src nxml
  <text:p text:style-name="OrgSrcBlock"><text:span text:style-name="OrgSrcFontLockCommentDelimiterFace">;;<text:s/></text:span><text:span text:style-name="OrgSrcFontLockCommentFace">This<text:s/>is<text:s/>how<text:s/>one<text:s/>changes<text:s/>load-path</text:span></text:p>
  <text:p text:style-name="OrgSrcBlock">(setq<text:s/>load-path<text:s/>(cons<text:s/><text:span text:style-name="OrgSrcFontLockStringFace">&quot;~/elisp&quot;</text:span><text:s/>load-path))</text:p>
#+end_src


* COMMENT This how the HTML output looks like

#+begin_src nxml
  <pre><span class="comment-delimiter">;; </span><span class="comment">This is how one changes load-path
  </span>(setq load-path (cons <span class="string">&quot;~/elisp&quot;</span> load-path))</pre>
#+end_src

  reply	other threads:[~2011-08-19 12:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15 20:36 [odt] htmlfontify + Support for src blockfontification Jambunathan K
2011-08-15 21:55 ` suvayu ali
2011-08-17  9:59 ` Bastien
2011-08-18 18:50   ` Jambunathan K
2011-08-18 18:57     ` Achim Gratz
2011-08-18 20:55     ` Jambunathan K
2011-08-18 23:10       ` suvayu ali
2011-08-19  7:31     ` Bastien
2011-08-19  8:22       ` Jambunathan K
2011-08-19  9:50         ` Bastien
2011-08-19 12:26           ` Jambunathan K
2011-08-19 12:49             ` Jambunathan K [this message]
2011-08-19 21:48             ` Bastien
2011-08-19 10:28         ` Bastien
2011-08-19 12:31           ` Jambunathan K
2011-08-19 20:20             ` Bastien
2011-08-19 10:31 ` Bastien
2011-08-19 12:13   ` Jambunathan K
2011-08-19 20:15     ` Bastien

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=81aab5k1mn.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --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).