emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Matt Price <moptop99@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-odt list bug - help reproducing?
Date: Sat, 13 Nov 2010 02:21:52 +0530	[thread overview]
Message-ID: <81iq02l0yf.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTiku+Lv4A0sMA+9mRwi8iLikoyW287SATn9BK9W2@mail.gmail.com> (Matt Price's message of "Fri, 12 Nov 2010 07:10:04 -0500")


Matt

> On Wed, Nov 10, 2010 at 11:14 AM, Jambunathan K <kjambunathan@gmail.com> wrote:
>
>     Matt
>
>     I am unable to reproduce the said behaviour.
>
>     From my work-area (which is same as that in git), the odt produced is
>     valid. I am attaching the odts produced in my work area. Let me know if
>     what is attached is not what you expect.
>
>
> I wonder if anyone on the list can reproduce the bug I'm finding in
> Jambunathan's odt exporter?   The attached org file creates the attached
> invalid odt file for me -- this is true both on my main laptop and in a clean
> environment I just went to some trouble to create on another computer, but J
> cannot reproduce the error.  I'm wondering if perhaps there's some implicit
> dependency in J's code somewhere that neither of us sees, and that isn't
> fulfilled on either of my systems.  I can't think of any other explanation....
>

Looks like it had been a pretty rough start for you ... Tried one more
round in reproducing the problem. But I cannot reproduce it at all.

If someone helps me in reproducing the bug, I will be happy to address
it in no time.

To encourage new users to try out the OpenOffice exporter, I have
revised the instructions in "How to export to OpenOffice?" section of
the README.org file.

- http://repo.or.cz/w/org-mode/oo.git/blob/HEAD:/contrib/odt/README.org

I suggest that you download the entire repo or the snapshot. Check that
you are using the URL that ends in "oo.git".

I am *pretty confident* that the OpenOffice exporter can handle simple
text - headlines, paragraphs, lists - very reliably.

How I tried reproducing the problem and failed:

1. I freshly cloned the repository.
2. Started emacs without any customization.
   "C:\Program Files\emacs-23.1.91\bin\runemacs.exe" --debug-init -Q
3. M-: (setq org-odt-base-dir "~/src/oo/") RET
4. M-x (load-file (expand-file-name "./contrib/odt/setup.el" org-odt-base-dir))
5. C-x C-f desc_test_short_2.org
6. I did a C-c C-e O.
7. I am seeing that OpenOffice launches and opens the file
   desc_test_short_2.odt without any complaints.

Jambunathan K.

  parent reply	other threads:[~2010-11-12 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 12:10 org-odt list bug - help reproducing? Matt Price
2010-11-12 12:43 ` Matt Price
2010-11-12 20:51 ` Jambunathan K [this message]
2010-11-12 21:36   ` Matt Price

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=81iq02l0yf.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=moptop99@gmail.com \
    /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).