From: Jambunathan K <kjambunathan@gmail.com>
To: Chong Yidong <cyd@gnu.org>
Cc: Vivek Dasmohapatra <vivek@etla.org>, 9914@debbugs.gnu.org
Subject: bug#9914: 24.0.91; htmlfontify.el: Add support for code block fontification on ODT export
Date: Mon, 12 Mar 2012 14:48:10 +0530 [thread overview]
Message-ID: <81ipiadvot.fsf@gmail.com> (raw)
In-Reply-To: <87vcmaxqtu.fsf@gnu.org> (Chong Yidong's message of "Mon, 12 Mar 2012 14:42:53 +0800")
Thanks Chong.
> Jambunathan: Could you write a ChangeLog entry for these changes?
There are 5 patches. The patches are generated with "git format-patch"
so the changelogs are embedded within the patch themselves. I had
downloaded htmlfontify separately and put it under local git before
generating the patches.
Vivek
org-odt.el is part of regular Emacs-24.1 pretest builds.
You will find it convenient to proceed as follows.
0. Put the modified htmlfontify.el in to load-path.
1. Export test.org file to ODT with C-c C-e O (or you can use the
test.odt file used in the bug report) Open the test.odt with
LibreOffice, if you need some visual cues on what the patch does.
2. Open the test.odt file in archive-mode or equivalently you can unzip
it.
3. Under test.odt/content.xml file you can see the OpenDocument tags
used for markup.
4. Under test.odt/styles.xml you can see the various style-names (the
css equivalent) for the various faces.
For some insight in to how these changes in htmlfontify are used,
1. Changes in content.xml is being generated by
`org-odt-format-source-code-or-example-colored'.
The main entry point in to htmlfontify library is
`htmlfontify-string' - Fontification happens line by line as opposed
to en-bloc.
2. Changes in styles.xml is being generated by
`org-odt-insert-custom-styles-for-srcblocks'. An Orgmode file can
have multiple src blocks of different languages. So a single export
of Org file can potentially run multiple htmlfontifys. As a result
styles are collected, duplicates eliminated and unique stylenames
dumped to styles.xml at the end of the export.
I will be happy to provide further clarifications.
Jambunathan K.
next prev parent reply other threads:[~2012-03-12 9:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 9:04 bug#9914: 24.0.91; htmlfontify.el: Add support for code block fontification on ODT export Jambunathan K
2011-11-07 9:20 ` Bastien
2012-01-25 10:23 ` Jambunathan K
2012-01-25 13:44 ` Stefan Monnier
2012-01-25 14:50 ` Bastien
2012-03-12 6:42 ` Chong Yidong
2012-03-12 9:18 ` Jambunathan K [this message]
2012-03-12 9:28 ` Chong Yidong
2012-03-12 9:40 ` Jambunathan K
2012-03-13 3:35 ` Vivek Dasmohapatra
2012-03-13 8:03 ` Jambunathan K
2012-03-17 5:05 ` Jambunathan K
2012-03-17 14:04 ` Chong Yidong
2012-03-12 9:40 ` Jambunathan K
2012-03-12 13:10 ` Vivek Dasmohapatra
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81ipiadvot.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=9914@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=vivek@etla.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.