Bugs and patches hunt before tomorrow

Bugs and patches hunt before tomorrow

[Bastien]

Dear all,

if there is important bugs and patches left, please resubmit
them before tomorrow, as we will release 7.6 tomorrow.

Have a good day!

-- 
 Bastien

Re: Bugs and patches hunt before tomorrow

[David Maus]

[-- Attachment #1.1: Type: text/plain, Size: 418 bytes --]

At Sat, 02 Jul 2011 16:05:23 +0200,
Bastien wrote:
>
> Dear all,
>
> if there is important bugs and patches left, please resubmit
> them before tomorrow, as we will release 7.6 tomorrow.

Three patches, byte compiler complains with Emacs 22, one for a
accidentally scoped variable in org-latex's preprocessor.

Best,
  -- David

--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de

[-- Attachment #1.2: 0001-Call-kill-buffer-with-argument-nil.patch --]
[-- Type: text/plain, Size: 1721 bytes --]

From ef2ebd1e72ee3b96ffb82acf61e99255dbf712b7 Mon Sep 17 00:00:00 2001
From: David Maus <dmaus@ictsoc.de>
Date: Sat, 2 Jul 2011 16:15:14 +0200
Subject: [PATCH 1/3] Call kill-buffer with argument nil

* ob-haskell.el (org-babel-haskell-export-to-lhs): Call kill-buffer
with argument indiciating to kill current buffer. Emacs 22
compatibility.

GNU Emacs 22.3.2 (i686-pc-linux-gnu) of 2011-05-28 on x60s

C-h f kill-buffer RET

kill-buffer is an interactive built-in function in `C source code'.
It is bound to C-x k.
(kill-buffer buffer)

Kill the buffer buffer.
The argument may be a buffer or the name of a buffer.
With a nil argument, kill the current buffer.
---
 lisp/ob-haskell.el |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/lisp/ob-haskell.el b/lisp/ob-haskell.el
index 4e3e797..822f90a 100644
--- a/lisp/ob-haskell.el
+++ b/lisp/ob-haskell.el
@@ -192,7 +192,7 @@ constructs (header arguments, no-web syntax etc...) are ignored."
     (save-excursion
       ;; export to latex w/org and save as .lhs
       (find-file tmp-org-file) (funcall 'org-export-as-latex nil)
-      (kill-buffer)
+      (kill-buffer nil)
       (delete-file tmp-org-file)
       (find-file tmp-tex-file)
       (goto-char (point-min)) (forward-line 2)
@@ -202,7 +202,7 @@ constructs (header arguments, no-web syntax etc...) are ignored."
         (replace-match (save-match-data (org-remove-indentation (match-string 0)))
                        t t))
       (setq contents (buffer-string))
-      (save-buffer) (kill-buffer))
+      (save-buffer) (kill-buffer nil))
     (delete-file tmp-tex-file)
     ;; save org exported latex to a .lhs file
     (with-temp-file lhs-file (insert contents))
-- 
1.7.2.5


[-- Attachment #1.3: 0002-Add-missing-group-keyword-in-defcustom.patch --]
[-- Type: text/plain, Size: 776 bytes --]

From 18ceb101fd2b701eefed279b6a13a04119ae016e Mon Sep 17 00:00:00 2001
From: David Maus <dmaus@ictsoc.de>
Date: Sat, 2 Jul 2011 16:27:43 +0200
Subject: [PATCH 2/3] Add missing :group keyword in defcustom

* org-html.el (org-export-html-protect-char-alist): Add missing :group
keyword in defcustom.
---
 lisp/org-html.el |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/lisp/org-html.el b/lisp/org-html.el
index 6e3bc19..b775834 100644
--- a/lisp/org-html.el
+++ b/lisp/org-html.el
@@ -565,6 +565,7 @@ a file."
     ("<" . "&lt;")
     (">" . "&gt;"))
   "Alist of characters to be converted by `org-html-protect'."
+  :group 'org-export-html
   :type '(repeat (cons (string :tag "Character")
 		       (string :tag "HTML equivalent"))))
 
-- 
1.7.2.5


[-- Attachment #1.4: 0003-Use-org-string-match-p-for-backward-compatibility-wi.patch --]
[-- Type: text/plain, Size: 2683 bytes --]

From f88f16c47c3bd23ab6139992259a941b82a52451 Mon Sep 17 00:00:00 2001
From: David Maus <dmaus@ictsoc.de>
Date: Sat, 2 Jul 2011 16:30:00 +0200
Subject: [PATCH 3/3] Use org-string-match-p for backward compatibility with Emacs22

* org-freemind.el (org-freemind-convert-links-helper)
(org-freemind-convert-text-p, org-freemind-write-mm-buffer)
(org-freemind-get-node-style): Use org-string-match-p for backward
compatibility with Emacs22.
---
 lisp/org-freemind.el |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/lisp/org-freemind.el b/lisp/org-freemind.el
index 5ea941d..e418659 100644
--- a/lisp/org-freemind.el
+++ b/lisp/org-freemind.el
@@ -308,7 +308,7 @@ MATCHED is the link just matched."
   (let* ((link (match-string 1 matched))
          (text (match-string 2 matched))
          (ext (file-name-extension link))
-         (col-pos (string-match-p ":" link))
+         (col-pos (org-string-match-p ":" link))
          (is-img (and (image-type-from-file-name link)
                       (let ((url-type (substring link 0 col-pos)))
                         (member url-type '("file" "http" "https")))))
@@ -414,7 +414,7 @@ MATCHED is the link just matched."
 (defun org-freemind-convert-text-p (text)
   "Convert TEXT to html with <p> paragraphs."
   ;; (string-match-p "[^ ]" "  a")
-  (setq org-freemind-bol-helper-base-indent (string-match-p "[^ ]" text))
+  (setq org-freemind-bol-helper-base-indent (org-string-match-p "[^ ]" text))
   (setq text (org-freemind-escape-str-from-org text))
 
   (setq text (replace-regexp-in-string "\\([[:space:]]\\)\\(/\\)\\([^/]+\\)\\(/\\)\\([[:space:]]\\)" "\\1<i>\\3</i>\\5" text))
@@ -658,7 +658,7 @@ Otherwise give an error say the file exists."
 (defun org-freemind-write-mm-buffer (org-buffer mm-buffer node-at-line)
   (with-current-buffer org-buffer
     (dolist (node-style org-freemind-node-styles)
-      (when (string-match-p (car node-style) buffer-file-name)
+      (when (org-string-match-p (car node-style) buffer-file-name)
         (setq org-freemind-node-style (cadr node-style))))
     ;;(message "org-freemind-node-style =%s" org-freemind-node-style)
     (save-match-data
@@ -835,7 +835,7 @@ Otherwise give an error say the file exists."
     (dolist (style-list org-freemind-node-style)
       (let ((node-regexp (car style-list)))
         (message "node-regexp=%s node-name=%s" node-regexp node-name)
-        (when (string-match-p node-regexp node-name)
+        (when (org-string-match-p node-regexp node-name)
           ;;(setq node-style (org-freemind-do-apply-node-style style-list))
           (setq node-style (cadr style-list))
           (when node-style
-- 
1.7.2.5


[-- Attachment #1.5: 0001-Use-function-argument-instead-if-dynamically-scoped-.patch --]
[-- Type: text/plain, Size: 1063 bytes --]

From 7c9ba3975c777e85ea8822043afa21ce9f18df0a Mon Sep 17 00:00:00 2001
From: David Maus <dmaus@ictsoc.de>
Date: Sat, 2 Jul 2011 16:25:59 +0200
Subject: [PATCH] Use function argument instead of dynamically scoped symbol

* org-latex.el (org-export-latex-preprocess): Use function argument
instead of dynamically scoped symbol.

Export options are passed to org-export-preprocess-string which passes
them down to backend specific preprocessor. The :footnotes option is
included.
---
 lisp/org-latex.el |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 694f65b..8266e9e 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -2430,7 +2430,7 @@ The conversion is made depending of STRING-BEFORE and STRING-AFTER."
      (replace-match "")))
 
   ;; When converting to LaTeX, replace footnotes.
-  (when (plist-get opt-plist :footnotes)
+  (when (plist-get parameters :footnotes)
     (goto-char (point-min))
     (let (ref)
       (while (setq ref (org-footnote-get-next-reference))
-- 
1.7.2.5


[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]

Re: Bugs and patches hunt before tomorrow

[David Maus]

[-- Attachment #1.1: Type: text/plain, Size: 267 bytes --]

At Sat, 02 Jul 2011 16:05:23 +0200,
Bastien wrote:
>
> Dear all,
>
> if there is important bugs and patches left, please resubmit
> them before tomorrow, as we will release 7.6 tomorrow.

And resubmit of this one:

http://article.gmane.org/gmane.emacs.orgmode/43235


[-- Attachment #1.2: 0001-Properly-handle-relative-symlinks-when-publishing.patch --]
[-- Type: text/plain, Size: 1715 bytes --]

From 6ad9f33ccb2d8702dd1d4375dd82998f72078e60 Mon Sep 17 00:00:00 2001
From: David Maus <dmaus@ictsoc.de>
Date: Sun, 26 Jun 2011 20:02:42 +0200
Subject: [PATCH] Properly handle relative symlinks when publishing

* org-publish.el (org-publish-cache-ctime-of-src): Properly handle
relative symlinks.

At Thu, 07 Apr 2011 01:11:00 -0400,
Nick Dokos wrote:
>
> org-publish-cache-ctime-of-src tries (but does not always succeed) to
> deal with symlinks: file-symlink-p returns the target as a string, but
> if the target is relative to the symlink, that's not going to fly.
> e.g. if c is a symlink like this
>
>     /a/b/c->../d/f
>
> then (file-symlink-p "/a/b/c") -> "../d/f"
> but if the current directory is any place other than /a/b, the target
> will not be found, the file attributes are going to be nil and
> the function will blow up.
---
 lisp/org-publish.el |    9 ++++++---
 1 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/lisp/org-publish.el b/lisp/org-publish.el
index 56cc80a..5646430 100644
--- a/lisp/org-publish.el
+++ b/lisp/org-publish.el
@@ -1157,9 +1157,12 @@ Returns value on success, else nil."
 
 (defun org-publish-cache-ctime-of-src (filename)
   "Get the FILENAME ctime as an integer."
-  (let ((src-attr (file-attributes (if (stringp (file-symlink-p filename))
-				       (file-symlink-p filename)
-				     filename))))
+  (let* ((symlink-maybe (or (file-symlink-p filename) filename))
+	 (src-attr (file-attributes (if (file-name-absolute-p symlink-maybe)
+					symlink-maybe
+				      (expand-file-name 
+				       symlink-maybe
+				       (file-name-directory filename))))))
     (+
      (lsh (car (nth 5 src-attr)) 16)
      (cadr (nth 5 src-attr)))))
-- 
1.7.2.5


[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]

[PATCH 1/2] org-lparse/org-odt: Add docstring. Silence byte-compiler

[Jambunathan K]

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


I am attaching two org-odt patches for inclusion. Both are desirable and
not mandatory.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org-lparse-org-odt-Add-docstring.-Silence-byte-compi.patch --]
[-- Type: text/x-patch, Size: 5619 bytes --]

From 38d0dcbc921d69ba55c3a5bb3a219204800370c9 Mon Sep 17 00:00:00 2001
From: Jambunathan K <kjambunathan@gmail.com>
Date: Sat, 2 Jul 2011 16:51:38 +0530
Subject: [PATCH 1/2] org-lparse/org-odt: Add docstring. Silence byte-compiler.

* contrib/lisp/org-odt.el (org-odt-unit-test):
Removed. This doesn't belong to production code.

* contrib/lisp/org-lparse.el (org-lparse-and-open)
(org-lparse-to-buffer, org-lparse-backend)
(org-lparse-other-backend, org-lparse-body-only)
(org-lparse-to-buffer): Update docstring.
---
 contrib/lisp/org-lparse.el |   52 +++++++++++++++++++++++++++++++++----------
 contrib/lisp/org-odt.el    |   11 ---------
 2 files changed, 40 insertions(+), 23 deletions(-)

diff --git a/contrib/lisp/org-lparse.el b/contrib/lisp/org-lparse.el
index cff8fd6..b37b683 100755
--- a/contrib/lisp/org-lparse.el
+++ b/contrib/lisp/org-lparse.el
@@ -50,8 +50,6 @@
 ;;; See README.org file that comes with this library for answers to
 ;;; FAQs and more information on using this library.
 
-;;; Use M-x `org-odt-unit-test' for test driving the odt exporter
-
 ;;; Code:
 
 (require 'org-exp)
@@ -59,10 +57,11 @@
 
 ;;;###autoload
 (defun org-lparse-and-open (target-backend native-backend arg)
-  "Export the outline as HTML and immediately open it with a browser.
-If there is an active region, export only the region.
-The prefix ARG specifies how many levels of the outline should become
-headlines.  The default is 3.  Lower levels will become bulleted lists."
+  "Export the outline to TARGET-BACKEND via NATIVE-BACKEND and open exported file.
+If there is an active region, export only the region.  The prefix
+ARG specifies how many levels of the outline should become
+headlines.  The default is 3.  Lower levels will become bulleted
+lists."
   ;; (interactive "Mbackend: \nP")
   (interactive
    (let* ((input (if (featurep 'ido) 'ido-completing-read 'completing-read))
@@ -102,8 +101,9 @@ emacs   --batch
 
 ;;;###autoload
 (defun org-lparse-to-buffer (backend arg)
-  "Call `org-lparse` with output to a temporary buffer.
-No file is created.  The prefix ARG is passed through to `org-lparse'."
+  "Call `org-lparse' with output to a temporary buffer.
+No file is created.  The prefix ARG is passed through to
+`org-lparse'."
   (interactive "Mbackend: \nP")
   (let ((tempbuf (format "*Org %s Export*" (upcase backend))))
       (org-lparse backend backend arg nil nil tempbuf)
@@ -508,9 +508,36 @@ then that converter is used.  Otherwise
 (defvar org-lparse-toc)
 (defvar org-lparse-entity-control-callbacks-alist)
 (defvar org-lparse-entity-format-callbacks-alist)
-(defvar org-lparse-backend)
-(defvar org-lparse-body-only)
-(defvar org-lparse-to-buffer)
+(defvar org-lparse-backend nil
+  "The native backend to which the document is currently exported.
+This variable is let bound during `org-lparse'.  Valid values are
+one of the symbols corresponding to `org-lparse-native-backends'.
+
+Compare this variable with `org-export-current-backend' which is
+bound only during `org-export-preprocess-string' stage of the
+export process.
+
+See also `org-lparse-other-backend'.")
+
+(defvar org-lparse-other-backend nil
+  "The target backend to which the document is currently exported.
+This variable is let bound during `org-lparse'.  This variable is
+set to either `org-lparse-backend' or one of the symbols
+corresponding to OTHER-BACKENDS specification of the
+org-lparse-backend.
+
+For example, if a document is exported to \"odt\" then both
+org-lparse-backend and org-lparse-other-backend are bound to
+'odt.  On the other hand, if a document is exported to \"odt\"
+and then converted to \"doc\" then org-lparse-backend is set to
+'odt and org-lparse-other-backend is set to 'doc.")
+
+(defvar org-lparse-body-only nil
+  "Bind this to BODY-ONLY arg of `org-lparse'.")
+
+(defvar org-lparse-to-buffer nil
+  "Bind this to TO-BUFFER arg of `org-lparse'.")
+
 (defun org-do-lparse (arg &optional hidden ext-plist
 			  to-buffer body-only pub-dir)
   "Export the outline to various formats.
@@ -1240,6 +1267,7 @@ But it has the disadvantage, that no cell- or row-spanning is allowed."
     (org-lparse-do-format-table-table lines)
     (buffer-substring-no-properties (point-min) (point-max))))
 
+(defvar table-source-languages)		; defined in table.el
 (defun org-lparse-format-table-table-using-table-generate-source (backend
 								 lines
 								 &optional
@@ -1948,7 +1976,7 @@ Replaces invalid characters with \"_\"."
 
 (defun org-lparse-format-section-number (&optional snumber level)
   (and org-export-with-section-numbers
-       (not body-only) snumber level
+       (not org-lparse-body-only) snumber level
        (org-lparse-format 'FONTIFY snumber (format "section-number-%d" level))))
 
 (defun org-lparse-warn (msg)
diff --git a/contrib/lisp/org-odt.el b/contrib/lisp/org-odt.el
index c0b6491..3d28c60 100644
--- a/contrib/lisp/org-odt.el
+++ b/contrib/lisp/org-odt.el
@@ -27,8 +27,6 @@
 ;;
 ;;; Commentary:
 
-;;; Use M-x `org-odt-unit-test' to test drive the exporter
-
 ;;; Code:
 (eval-when-compile (require 'cl))
 (require 'org-lparse)
@@ -1499,15 +1497,6 @@ To disable outline numbering pass a LEVEL of 0."
 	  (replace-match replacement t nil))))
     (save-buffer 0)))
 
-;;;###autoload
-(defun org-odt-unit-test (&optional linger)
-  "Automatically visit the Unit Test file and export it."
-  (interactive "P")
-  (with-current-buffer
-      (find-file (expand-file-name "tests/test.org" org-odt-data-dir))
-    (unless linger
-      (call-interactively 'org-export-as-odt-and-open))))
-
 (provide 'org-odt)
 
 ;;; org-odt.el ends here
-- 
1.7.2.3


[-- Attachment #3: Type: text/plain, Size: 6 bytes --]



-- 

[PATCH 2/2] doc/org.texi: Add a new node for OpenDocumentText exporter

[Jambunathan K]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: 0002-doc-org.texi-Add-a-new-node-for-OpenDocumentText-exp.patch --]
[-- Type: text/x-patch, Size: 11471 bytes --]

From 1177aa67678e2c9b0fd1d65cd0d87436fd63a08e Mon Sep 17 00:00:00 2001
From: Jambunathan K <kjambunathan@gmail.com>
Date: Sat, 2 Jul 2011 22:40:18 +0530
Subject: [PATCH 2/2] doc/org.texi: Add a new node for OpenDocumentText exporter

---
 doc/org.texi |  180 +++++++++++++++++++++++++++++++++++++++++++++++++++++++--
 1 files changed, 173 insertions(+), 7 deletions(-)

diff --git a/doc/org.texi b/doc/org.texi
index afa1623..d3753ce 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -574,6 +574,7 @@ Exporting
 * HTML export::                 Exporting to HTML
 * LaTeX and PDF export::        Exporting to @LaTeX{}, and processing to PDF
 * DocBook export::              Exporting to DocBook
+* OpenDocumentText export::     Exporting to OpenDocumentText
 * TaskJuggler export::          Exporting to TaskJuggler
 * Freemind export::             Exporting to Freemind mind maps
 * XOXO export::                 Exporting to XOXO
@@ -610,6 +611,16 @@ DocBook export
 * Images in DocBook export::    How to insert figures into DocBook output
 * Special characters::          How to handle special characters
 
+OpenDocument export
+
+* OpenDocumentText export commands::    How to invoke OpenDocumentText export
+* Applying Custom Styles::      How to apply custom styles to the output
+* Converting to Other formats:: How to convert to formats like doc, docx etc
+* Links in OpenDocumentText export::  How links will be interpreted and formatted
+* Tables in OpenDocumentText export::    How Tables are handled
+* Images in OpenDocumentText export::    How to insert figures
+* Additional Documentation::          How to handle special characters
+
 Publishing
 
 * Configuration::               Defining projects
@@ -9378,11 +9389,13 @@ the web, while the XOXO format provides a solid base for exchange with a
 broad range of other applications.  @LaTeX{} export lets you use Org-mode and
 its structured editing functions to easily create @LaTeX{} files.  DocBook
 export makes it possible to convert Org files to many other formats using
-DocBook tools.  For project management you can create gantt and resource
-charts by using TaskJuggler export.  To incorporate entries with associated
-times like deadlines or appointments into a desktop calendar program like
-iCal, Org-mode can also produce extracts in the iCalendar format.  Currently
-Org-mode only supports export, not import of these different formats.
+DocBook tools.  OpenDocumentText export allows seamless colloboration across
+organizational boundaries.  For project management you can create gantt and
+resource charts by using TaskJuggler export.  To incorporate entries with
+associated times like deadlines or appointments into a desktop calendar
+program like iCal, Org-mode can also produce extracts in the iCalendar
+format.  Currently Org-mode only supports export, not import of these
+different formats.
 
 Org supports export of selected regions when @code{transient-mark-mode} is
 enabled (default in Emacs 23).
@@ -9395,6 +9408,7 @@ enabled (default in Emacs 23).
 * HTML export::                 Exporting to HTML
 * LaTeX and PDF export::        Exporting to @LaTeX{}, and processing to PDF
 * DocBook export::              Exporting to DocBook
+* OpenDocumentText export::     Exporting to OpenDocumentText
 * TaskJuggler export::          Exporting to TaskJuggler
 * Freemind export::             Exporting to Freemind mind maps
 * XOXO export::                 Exporting to XOXO
@@ -10416,7 +10430,7 @@ Here is a simple example Org document that is intended for beamer export.
 
 For more information, see the documentation on Worg.
 
-@node DocBook export, TaskJuggler export, LaTeX and PDF export, Exporting
+@node DocBook export, OpenDocumentText export, LaTeX and PDF export, Exporting
 @section DocBook export
 @cindex DocBook export
 @cindex PDF export
@@ -10613,7 +10627,156 @@ special characters included in XHTML entities:
 "
 @end example
 
-@node  TaskJuggler export, Freemind export, DocBook export, Exporting
+@c begin opendocument
+
+@node OpenDocumentText export, TaskJuggler export, DocBook export, Exporting
+@section OpenDocumentText export
+@cindex OpenDocumentText export
+@cindex K, Jambunathan
+
+Org-mode 7.6 supports export to OpenDocumentText format using
+@file{org-odt.el} module contributed by Jambunathan K.  This module can be
+enabled in one of the following ways based on your mode of installation.
+
+@enumerate
+@item
+If you have downloaded the Org from the Web, either as a distribution
+@file{.zip} or @file{.tar} file, or as a Git archive, enable the @code{odt}
+option in variable @code{org-modules}.
+@item
+If you are using Org that comes bundled with Emacs, then you can install the
+OpenDocumentText exporter using the package manager. To do this, customize
+the variable @code{package-archives} to include
+@uref{http://orgmode.org/pkg/releases/} as one of the package archives.
+@end enumerate
+
+@menu
+* OpenDocumentText export commands::How to invoke OpenDocumentText export
+* Applying Custom Styles::      How to apply custom styles to the output
+* Converting to Other formats:: How to convert to formats like doc, docx etc
+* Links in OpenDocumentText export::  How links will be interpreted and formatted
+* Tables in OpenDocumentText export::    Tables are exported as HTML tables
+* Images in OpenDocumentText export::    How to insert figures into DocBook output
+* Additional Documentation::    Where to find more information
+@end menu
+
+@node OpenDocumentText export commands, Applying Custom Styles, OpenDocumentText export, OpenDocumentText export
+@subsection OpenDocumentText export commands
+
+@cindex region, active
+@cindex active region
+@cindex transient-mark-mode
+@table @kbd
+@orgcmd{C-c C-e o,org-export-as-odt}
+@cindex property EXPORT_FILE_NAME
+Export as OpenDocumentText file.  For an Org file, @file{myfile.org}, the
+OpenDocumentText file will be @file{myfile.odt}.  The file will be
+overwritten without warning.  If there is an active region@footnote{This
+requires @code{transient-mark-mode} to be turned on}, only the region will be
+exported.  If the selected region is a single tree@footnote{To select the
+current subtree, use @kbd{C-c @@}.}, the tree head will become the document
+title.  If the tree head entry has, or inherits, an @code{EXPORT_FILE_NAME}
+property, that name will be used for the export.
+@orgcmd{C-c C-e O,org-export-as-odt-and-open}
+Export as OpenDocumentText file and open the resulting file.
+@end table
+
+@node Applying Custom Styles, Converting to Other formats, OpenDocumentText export commands, OpenDocumentText export
+@subsection Applying Custom Styles
+@cindex styles, custom
+@cindex template, custom
+
+@vindex org-export-odt-styles-file
+
+OpenDocumentExporter ships with a custom @file{styles.xml} for formatting of
+the exported file.  To customize the output to suit your needs you can use
+one of the following methods:
+
+@enumerate
+@item
+Customize the variable @code{org-export-odt-styles-file} to point to either a
+@file{styles.xml} file, a OpenDocument Text Template file @code{.ott} or a
+combination of Text or Template Document together with a set of member files.
+Use the first two options if the styles.xml has no references to additional
+set of files and use the last option if the @file{styles.xml} references
+additional files like header and footer images.
+@item
+Use an external tool like unoconv to apply custom templates.
+@end enumerate
+
+For best results, it is necessary that the style names used by
+OpenDocumentText exporter match that used in the @file{styles.xml}.
+
+@node Converting to Other formats, Links in OpenDocumentText export, Applying Custom Styles, OpenDocumentText export
+@subsection Converting to Other formats
+
+@cindex convert
+@cindex doc, docx
+
+@vindex org-export-odt-styles-file
+
+Often times there is a need to convert OpenDocumentText files to other
+formats like doc, docx or pdf.  You can accomplish this by one of the
+following methods:
+
+@table @kbd
+@item M-x org-lparse
+Export the outline first to one of the native formats (like OpenDocumentText)
+and immediately post-process it to other formats using an external converter.
+
+@item M-x org-export-convert
+Export an existing document to other formats using an external converter.
+@end table
+
+You can choose the converter used for conversion by customizing the variable
+@code{org-export-convert-process}.
+
+@node Links in OpenDocumentText export, Tables in OpenDocumentText export, Converting to Other formats, OpenDocumentText export
+@subsection Links in OpenDocumentText export
+@cindex tables, in DocBook export
+
+OpenDocumentExporter creates cross-references (aka bookmarks) for links that
+are destined locally. It creates internet style links for all other links.
+
+@node Tables in OpenDocumentText export, Images in OpenDocumentText export, Links in OpenDocumentText export, OpenDocumentText export
+@subsection Tables in OpenDocumentText export
+@cindex tables, in DocBook export
+
+Export of @file{table.el} tables with row or column spanning is not
+supported.  Such tables are stripped from the exported document.
+
+@node Images in OpenDocumentText export, Additional Documentation, Tables in OpenDocumentText export, OpenDocumentText export
+@subsection Images in OpenDocumentText export
+@cindex images, embedding in OpenDocumentText
+@cindex embedding images in OpenDocumentText
+
+OpenDocumentText exporter can embed images within the exported document. To
+embed images, provide a link to the desired image file with no link
+description. For example, the following links @samp{[[file:img.jpg]]} or
+@samp{[[./img.jpg]]}, will result in embedding of @samp{img.jpg} in the
+exported file.
+
+The exporter can also embed scaled and explicitly sized images within the
+exported document.  The markup of the scale and size specifications has not
+been standardized yet and is hence conveniently skipped in this document.
+
+The exporter can also make an image the clickable part of a link. To create
+clickable images, provide a link whose description is a link to an image
+file. For example, the following link
+@samp{[[http://Orgmode.org][./img.jpg]]}, will result in a clickable image
+that links to @uref{http://Orgmode.org} website.
+
+@node Additional Documentation, , Images in OpenDocumentText export, OpenDocumentText export
+@subsection Additional Documentation
+
+OpenDocumentText exporter is a beta software and is quickly evolving.  So the
+documentation in this section of the manual should not be considered as
+authoritative. For up to date information, you are requested to follow the
+Org mailing list @email{emacs-orgmode@@gnu.org} closely.
+
+@c end opendocument
+
+@node  TaskJuggler export, Freemind export, OpenDocumentText export, Exporting
 @section TaskJuggler export
 @cindex TaskJuggler export
 @cindex Project management
@@ -15327,6 +15490,8 @@ with links transformation to Org syntax.
 @i{David O'Toole} wrote @file{org-publish.el} and drafted the manual
 chapter about publishing.
 @item
+@i{Jambunathan K} contributed the OpenDocumentText exporter.
+@item
 @i{Sebastien Vauban} reported many issues with LaTeX and BEAMER export and
 enabled source code highlighling in Gnus.
 @item
@@ -15353,6 +15518,7 @@ work on a tty.
 @item
 @i{Piotr Zielinski} wrote @file{org-mouse.el}, proposed agenda blocks
 and contributed various ideas and code snippets.
+@item
 @end itemize
 
 
-- 
1.7.2.3


[-- Attachment #2: Type: text/plain, Size: 6 bytes --]



-- 

Re: [PATCH 2/2] doc/org.texi: Add a new node for OpenDocumentText exporter

[Jambunathan K]

> +If you are using Org that comes bundled with Emacs, then you can install the
> +OpenDocumentText exporter using the package manager. To do this, customize
> +the variable @code{package-archives} to include
> +@uref{http://orgmode.org/pkg/releases/} as one of the package archives.
> +@end enumerate

If you are not in agreement with the above paragraph please delete it
from the info manual. Otherwise you can copy the 3 files that you find
in the below URL.

http://repo.or.cz/w/org-mode/org-jambu.git/tree/HEAD:/packages/emacs-24.1

to the URL of your choosing under http://orgmode.org/pkg and update the
manual accordingly.

Just a suggestion. 

Jambunathan K.

[Accepted] [O, 1/2] org-lparse/org-odt: Add docstring. Silence byte-compiler

[Bastien Guerry]

Patch 820 (http://patchwork.newartisans.com/patch/820/) is now "Accepted".

Maintainer comment: none

This relates to the following submission:

http://mid.gmane.org/%3C81vcvkoa7a.fsf%40gmail.com%3E

Here is the original message containing the patch:

> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [O,1/2] org-lparse/org-odt: Add docstring. Silence byte-compiler
> Date: Sat, 02 Jul 2011 22:37:29 -0000
> From: Jambunathan K <kjambunathan@gmail.com>
> X-Patchwork-Id: 820
> Message-Id: <81vcvkoa7a.fsf@gmail.com>
> To: emacs-orgmode@gnu.org
> Cc: 
> 
> I am attaching two org-odt patches for inclusion. Both are desirable and
> not mandatory.
> 
> ---
> 
> 
> >From 38d0dcbc921d69ba55c3a5bb3a219204800370c9 Mon Sep 17 00:00:00 2001
> From: Jambunathan K <kjambunathan@gmail.com>
> Date: Sat, 2 Jul 2011 16:51:38 +0530
> Subject: [PATCH 1/2] org-lparse/org-odt: Add docstring. Silence byte-compiler.
> 
> * contrib/lisp/org-odt.el (org-odt-unit-test):
> Removed. This doesn't belong to production code.
> 
> * contrib/lisp/org-lparse.el (org-lparse-and-open)
> (org-lparse-to-buffer, org-lparse-backend)
> (org-lparse-other-backend, org-lparse-body-only)
> (org-lparse-to-buffer): Update docstring.
> ---
>  contrib/lisp/org-lparse.el |   52 +++++++++++++++++++++++++++++++++----------
>  contrib/lisp/org-odt.el    |   11 ---------
>  2 files changed, 40 insertions(+), 23 deletions(-)
> 
> diff --git a/contrib/lisp/org-lparse.el b/contrib/lisp/org-lparse.el
> index cff8fd6..b37b683 100755
> --- a/contrib/lisp/org-lparse.el
> +++ b/contrib/lisp/org-lparse.el
> @@ -50,8 +50,6 @@
>  ;;; See README.org file that comes with this library for answers to
>  ;;; FAQs and more information on using this library.
>  
> -;;; Use M-x `org-odt-unit-test' for test driving the odt exporter
> -
>  ;;; Code:
>  
>  (require 'org-exp)
> @@ -59,10 +57,11 @@
>  
>  ;;;###autoload
>  (defun org-lparse-and-open (target-backend native-backend arg)
> -  "Export the outline as HTML and immediately open it with a browser.
> -If there is an active region, export only the region.
> -The prefix ARG specifies how many levels of the outline should become
> -headlines.  The default is 3.  Lower levels will become bulleted lists."
> +  "Export the outline to TARGET-BACKEND via NATIVE-BACKEND and open exported file.
> +If there is an active region, export only the region.  The prefix
> +ARG specifies how many levels of the outline should become
> +headlines.  The default is 3.  Lower levels will become bulleted
> +lists."
>    ;; (interactive "Mbackend: \nP")
>    (interactive
>     (let* ((input (if (featurep 'ido) 'ido-completing-read 'completing-read))
> @@ -102,8 +101,9 @@ emacs   --batch
>  
>  ;;;###autoload
>  (defun org-lparse-to-buffer (backend arg)
> -  "Call `org-lparse` with output to a temporary buffer.
> -No file is created.  The prefix ARG is passed through to `org-lparse'."
> +  "Call `org-lparse' with output to a temporary buffer.
> +No file is created.  The prefix ARG is passed through to
> +`org-lparse'."
>    (interactive "Mbackend: \nP")
>    (let ((tempbuf (format "*Org %s Export*" (upcase backend))))
>        (org-lparse backend backend arg nil nil tempbuf)
> @@ -508,9 +508,36 @@ then that converter is used.  Otherwise
>  (defvar org-lparse-toc)
>  (defvar org-lparse-entity-control-callbacks-alist)
>  (defvar org-lparse-entity-format-callbacks-alist)
> -(defvar org-lparse-backend)
> -(defvar org-lparse-body-only)
> -(defvar org-lparse-to-buffer)
> +(defvar org-lparse-backend nil
> +  "The native backend to which the document is currently exported.
> +This variable is let bound during `org-lparse'.  Valid values are
> +one of the symbols corresponding to `org-lparse-native-backends'.
> +
> +Compare this variable with `org-export-current-backend' which is
> +bound only during `org-export-preprocess-string' stage of the
> +export process.
> +
> +See also `org-lparse-other-backend'.")
> +
> +(defvar org-lparse-other-backend nil
> +  "The target backend to which the document is currently exported.
> +This variable is let bound during `org-lparse'.  This variable is
> +set to either `org-lparse-backend' or one of the symbols
> +corresponding to OTHER-BACKENDS specification of the
> +org-lparse-backend.
> +
> +For example, if a document is exported to \"odt\" then both
> +org-lparse-backend and org-lparse-other-backend are bound to
> +'odt.  On the other hand, if a document is exported to \"odt\"
> +and then converted to \"doc\" then org-lparse-backend is set to
> +'odt and org-lparse-other-backend is set to 'doc.")
> +
> +(defvar org-lparse-body-only nil
> +  "Bind this to BODY-ONLY arg of `org-lparse'.")
> +
> +(defvar org-lparse-to-buffer nil
> +  "Bind this to TO-BUFFER arg of `org-lparse'.")
> +
>  (defun org-do-lparse (arg &optional hidden ext-plist
>  			  to-buffer body-only pub-dir)
>    "Export the outline to various formats.
> @@ -1240,6 +1267,7 @@ But it has the disadvantage, that no cell- or row-spanning is allowed."
>      (org-lparse-do-format-table-table lines)
>      (buffer-substring-no-properties (point-min) (point-max))))
>  
> +(defvar table-source-languages)		; defined in table.el
>  (defun org-lparse-format-table-table-using-table-generate-source (backend
>  								 lines
>  								 &optional
> @@ -1948,7 +1976,7 @@ Replaces invalid characters with \"_\"."
>  
>  (defun org-lparse-format-section-number (&optional snumber level)
>    (and org-export-with-section-numbers
> -       (not body-only) snumber level
> +       (not org-lparse-body-only) snumber level
>         (org-lparse-format 'FONTIFY snumber (format "section-number-%d" level))))
>  
>  (defun org-lparse-warn (msg)
> diff --git a/contrib/lisp/org-odt.el b/contrib/lisp/org-odt.el
> index c0b6491..3d28c60 100644
> --- a/contrib/lisp/org-odt.el
> +++ b/contrib/lisp/org-odt.el
> @@ -27,8 +27,6 @@
>  ;;
>  ;;; Commentary:
>  
> -;;; Use M-x `org-odt-unit-test' to test drive the exporter
> -
>  ;;; Code:
>  (eval-when-compile (require 'cl))
>  (require 'org-lparse)
> @@ -1499,15 +1497,6 @@ To disable outline numbering pass a LEVEL of 0."
>  	  (replace-match replacement t nil))))
>      (save-buffer 0)))
>  
> -;;;###autoload
> -(defun org-odt-unit-test (&optional linger)
> -  "Automatically visit the Unit Test file and export it."
> -  (interactive "P")
> -  (with-current-buffer
> -      (find-file (expand-file-name "tests/test.org" org-odt-data-dir))
> -    (unless linger
> -      (call-interactively 'org-export-as-odt-and-open))))
> -
>  (provide 'org-odt)
>  
>  ;;; org-odt.el ends here
> -- 
> 1.7.2.3
> 
> 

[Accepted] [O, 2/2] doc/org.texi: Add a new node for OpenDocumentText exporter

[Bastien Guerry]

Patch 821 (http://patchwork.newartisans.com/patch/821/) is now "Accepted".

Maintainer comment: none

This relates to the following submission:

http://mid.gmane.org/%3C81r568oa45.fsf%40gmail.com%3E

Here is the original message containing the patch:

> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [O,2/2] doc/org.texi: Add a new node for OpenDocumentText exporter
> Date: Sat, 02 Jul 2011 22:39:22 -0000
> From: Jambunathan K <kjambunathan@gmail.com>
> X-Patchwork-Id: 821
> Message-Id: <81r568oa45.fsf@gmail.com>
> To: emacs-orgmode@gnu.org
> Cc: 
> 
> --
> 
> 
> >From 1177aa67678e2c9b0fd1d65cd0d87436fd63a08e Mon Sep 17 00:00:00 2001
> From: Jambunathan K <kjambunathan@gmail.com>
> Date: Sat, 2 Jul 2011 22:40:18 +0530
> Subject: [PATCH 2/2] doc/org.texi: Add a new node for OpenDocumentText exporter
> 
> ---
>  doc/org.texi |  180 +++++++++++++++++++++++++++++++++++++++++++++++++++++++--
>  1 files changed, 173 insertions(+), 7 deletions(-)
> 
> diff --git a/doc/org.texi b/doc/org.texi
> index afa1623..d3753ce 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -574,6 +574,7 @@ Exporting
>  * HTML export::                 Exporting to HTML
>  * LaTeX and PDF export::        Exporting to @LaTeX{}, and processing to PDF
>  * DocBook export::              Exporting to DocBook
> +* OpenDocumentText export::     Exporting to OpenDocumentText
>  * TaskJuggler export::          Exporting to TaskJuggler
>  * Freemind export::             Exporting to Freemind mind maps
>  * XOXO export::                 Exporting to XOXO
> @@ -610,6 +611,16 @@ DocBook export
>  * Images in DocBook export::    How to insert figures into DocBook output
>  * Special characters::          How to handle special characters
>  
> +OpenDocument export
> +
> +* OpenDocumentText export commands::    How to invoke OpenDocumentText export
> +* Applying Custom Styles::      How to apply custom styles to the output
> +* Converting to Other formats:: How to convert to formats like doc, docx etc
> +* Links in OpenDocumentText export::  How links will be interpreted and formatted
> +* Tables in OpenDocumentText export::    How Tables are handled
> +* Images in OpenDocumentText export::    How to insert figures
> +* Additional Documentation::          How to handle special characters
> +
>  Publishing
>  
>  * Configuration::               Defining projects
> @@ -9378,11 +9389,13 @@ the web, while the XOXO format provides a solid base for exchange with a
>  broad range of other applications.  @LaTeX{} export lets you use Org-mode and
>  its structured editing functions to easily create @LaTeX{} files.  DocBook
>  export makes it possible to convert Org files to many other formats using
> -DocBook tools.  For project management you can create gantt and resource
> -charts by using TaskJuggler export.  To incorporate entries with associated
> -times like deadlines or appointments into a desktop calendar program like
> -iCal, Org-mode can also produce extracts in the iCalendar format.  Currently
> -Org-mode only supports export, not import of these different formats.
> +DocBook tools.  OpenDocumentText export allows seamless colloboration across
> +organizational boundaries.  For project management you can create gantt and
> +resource charts by using TaskJuggler export.  To incorporate entries with
> +associated times like deadlines or appointments into a desktop calendar
> +program like iCal, Org-mode can also produce extracts in the iCalendar
> +format.  Currently Org-mode only supports export, not import of these
> +different formats.
>  
>  Org supports export of selected regions when @code{transient-mark-mode} is
>  enabled (default in Emacs 23).
> @@ -9395,6 +9408,7 @@ enabled (default in Emacs 23).
>  * HTML export::                 Exporting to HTML
>  * LaTeX and PDF export::        Exporting to @LaTeX{}, and processing to PDF
>  * DocBook export::              Exporting to DocBook
> +* OpenDocumentText export::     Exporting to OpenDocumentText
>  * TaskJuggler export::          Exporting to TaskJuggler
>  * Freemind export::             Exporting to Freemind mind maps
>  * XOXO export::                 Exporting to XOXO
> @@ -10416,7 +10430,7 @@ Here is a simple example Org document that is intended for beamer export.
>  
>  For more information, see the documentation on Worg.
>  
> -@node DocBook export, TaskJuggler export, LaTeX and PDF export, Exporting
> +@node DocBook export, OpenDocumentText export, LaTeX and PDF export, Exporting
>  @section DocBook export
>  @cindex DocBook export
>  @cindex PDF export
> @@ -10613,7 +10627,156 @@ special characters included in XHTML entities:
>  "
>  @end example
>  
> -@node  TaskJuggler export, Freemind export, DocBook export, Exporting
> +@c begin opendocument
> +
> +@node OpenDocumentText export, TaskJuggler export, DocBook export, Exporting
> +@section OpenDocumentText export
> +@cindex OpenDocumentText export
> +@cindex K, Jambunathan
> +
> +Org-mode 7.6 supports export to OpenDocumentText format using
> +@file{org-odt.el} module contributed by Jambunathan K.  This module can be
> +enabled in one of the following ways based on your mode of installation.
> +
> +@enumerate
> +@item
> +If you have downloaded the Org from the Web, either as a distribution
> +@file{.zip} or @file{.tar} file, or as a Git archive, enable the @code{odt}
> +option in variable @code{org-modules}.
> +@item
> +If you are using Org that comes bundled with Emacs, then you can install the
> +OpenDocumentText exporter using the package manager. To do this, customize
> +the variable @code{package-archives} to include
> +@uref{http://orgmode.org/pkg/releases/} as one of the package archives.
> +@end enumerate
> +
> +@menu
> +* OpenDocumentText export commands::How to invoke OpenDocumentText export
> +* Applying Custom Styles::      How to apply custom styles to the output
> +* Converting to Other formats:: How to convert to formats like doc, docx etc
> +* Links in OpenDocumentText export::  How links will be interpreted and formatted
> +* Tables in OpenDocumentText export::    Tables are exported as HTML tables
> +* Images in OpenDocumentText export::    How to insert figures into DocBook output
> +* Additional Documentation::    Where to find more information
> +@end menu
> +
> +@node OpenDocumentText export commands, Applying Custom Styles, OpenDocumentText export, OpenDocumentText export
> +@subsection OpenDocumentText export commands
> +
> +@cindex region, active
> +@cindex active region
> +@cindex transient-mark-mode
> +@table @kbd
> +@orgcmd{C-c C-e o,org-export-as-odt}
> +@cindex property EXPORT_FILE_NAME
> +Export as OpenDocumentText file.  For an Org file, @file{myfile.org}, the
> +OpenDocumentText file will be @file{myfile.odt}.  The file will be
> +overwritten without warning.  If there is an active region@footnote{This
> +requires @code{transient-mark-mode} to be turned on}, only the region will be
> +exported.  If the selected region is a single tree@footnote{To select the
> +current subtree, use @kbd{C-c @@}.}, the tree head will become the document
> +title.  If the tree head entry has, or inherits, an @code{EXPORT_FILE_NAME}
> +property, that name will be used for the export.
> +@orgcmd{C-c C-e O,org-export-as-odt-and-open}
> +Export as OpenDocumentText file and open the resulting file.
> +@end table
> +
> +@node Applying Custom Styles, Converting to Other formats, OpenDocumentText export commands, OpenDocumentText export
> +@subsection Applying Custom Styles
> +@cindex styles, custom
> +@cindex template, custom
> +
> +@vindex org-export-odt-styles-file
> +
> +OpenDocumentExporter ships with a custom @file{styles.xml} for formatting of
> +the exported file.  To customize the output to suit your needs you can use
> +one of the following methods:
> +
> +@enumerate
> +@item
> +Customize the variable @code{org-export-odt-styles-file} to point to either a
> +@file{styles.xml} file, a OpenDocument Text Template file @code{.ott} or a
> +combination of Text or Template Document together with a set of member files.
> +Use the first two options if the styles.xml has no references to additional
> +set of files and use the last option if the @file{styles.xml} references
> +additional files like header and footer images.
> +@item
> +Use an external tool like unoconv to apply custom templates.
> +@end enumerate
> +
> +For best results, it is necessary that the style names used by
> +OpenDocumentText exporter match that used in the @file{styles.xml}.
> +
> +@node Converting to Other formats, Links in OpenDocumentText export, Applying Custom Styles, OpenDocumentText export
> +@subsection Converting to Other formats
> +
> +@cindex convert
> +@cindex doc, docx
> +
> +@vindex org-export-odt-styles-file
> +
> +Often times there is a need to convert OpenDocumentText files to other
> +formats like doc, docx or pdf.  You can accomplish this by one of the
> +following methods:
> +
> +@table @kbd
> +@item M-x org-lparse
> +Export the outline first to one of the native formats (like OpenDocumentText)
> +and immediately post-process it to other formats using an external converter.
> +
> +@item M-x org-export-convert
> +Export an existing document to other formats using an external converter.
> +@end table
> +
> +You can choose the converter used for conversion by customizing the variable
> +@code{org-export-convert-process}.
> +
> +@node Links in OpenDocumentText export, Tables in OpenDocumentText export, Converting to Other formats, OpenDocumentText export
> +@subsection Links in OpenDocumentText export
> +@cindex tables, in DocBook export
> +
> +OpenDocumentExporter creates cross-references (aka bookmarks) for links that
> +are destined locally. It creates internet style links for all other links.
> +
> +@node Tables in OpenDocumentText export, Images in OpenDocumentText export, Links in OpenDocumentText export, OpenDocumentText export
> +@subsection Tables in OpenDocumentText export
> +@cindex tables, in DocBook export
> +
> +Export of @file{table.el} tables with row or column spanning is not
> +supported.  Such tables are stripped from the exported document.
> +
> +@node Images in OpenDocumentText export, Additional Documentation, Tables in OpenDocumentText export, OpenDocumentText export
> +@subsection Images in OpenDocumentText export
> +@cindex images, embedding in OpenDocumentText
> +@cindex embedding images in OpenDocumentText
> +
> +OpenDocumentText exporter can embed images within the exported document. To
> +embed images, provide a link to the desired image file with no link
> +description. For example, the following links @samp{[[file:img.jpg]]} or
> +@samp{[[./img.jpg]]}, will result in embedding of @samp{img.jpg} in the
> +exported file.
> +
> +The exporter can also embed scaled and explicitly sized images within the
> +exported document.  The markup of the scale and size specifications has not
> +been standardized yet and is hence conveniently skipped in this document.
> +
> +The exporter can also make an image the clickable part of a link. To create
> +clickable images, provide a link whose description is a link to an image
> +file. For example, the following link
> +@samp{[[http://Orgmode.org][./img.jpg]]}, will result in a clickable image
> +that links to @uref{http://Orgmode.org} website.
> +
> +@node Additional Documentation, , Images in OpenDocumentText export, OpenDocumentText export
> +@subsection Additional Documentation
> +
> +OpenDocumentText exporter is a beta software and is quickly evolving.  So the
> +documentation in this section of the manual should not be considered as
> +authoritative. For up to date information, you are requested to follow the
> +Org mailing list @email{emacs-orgmode@@gnu.org} closely.
> +
> +@c end opendocument
> +
> +@node  TaskJuggler export, Freemind export, OpenDocumentText export, Exporting
>  @section TaskJuggler export
>  @cindex TaskJuggler export
>  @cindex Project management
> @@ -15327,6 +15490,8 @@ with links transformation to Org syntax.
>  @i{David O'Toole} wrote @file{org-publish.el} and drafted the manual
>  chapter about publishing.
>  @item
> +@i{Jambunathan K} contributed the OpenDocumentText exporter.
> +@item
>  @i{Sebastien Vauban} reported many issues with LaTeX and BEAMER export and
>  enabled source code highlighling in Gnus.
>  @item
> @@ -15353,6 +15518,7 @@ work on a tty.
>  @item
>  @i{Piotr Zielinski} wrote @file{org-mouse.el}, proposed agenda blocks
>  and contributed various ideas and code snippets.
> +@item
>  @end itemize
>  
>  
> -- 
> 1.7.2.3
> 
> 

Re: Bugs and patches hunt before tomorrow

[Bastien]

Hi David,

David Maus <dmaus@ictsoc.de> writes:

> Three patches, byte compiler complains with Emacs 22, one for a
> accidentally scoped variable in org-latex's preprocessor.

All applied, great.  Thanks!

-- 
 Bastien

Re: Bugs and patches hunt before tomorrow

[Bastien]

David Maus <dmaus@ictsoc.de> writes:

> And resubmit of this one:
>
> http://article.gmane.org/gmane.emacs.orgmode/43235

Applied, thanks.

-- 
 Bastien

Re: [PATCH 2/2] doc/org.texi: Add a new node for OpenDocumentText exporter

[Bastien]

Hi Jambunathan,

Jambunathan K <kjambunathan@gmail.com> writes:

> Otherwise you can copy the 3 files that you find in the below URL.
>
> http://repo.or.cz/w/org-mode/org-jambu.git/tree/HEAD:/packages/emacs-24.1
>
> to the URL of your choosing under http://orgmode.org/pkg and update the
> manual accordingly.

Jason, can you take care of this?

No emergency, as this must be ready only after 7.6 is release *and*
merged to Emacs trunk.

Thanks!

-- 
 Bastien