emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Baoqiu Cui <cbaoqiu@yahoo.com>
To: emacs-orgmode@gnu.org
Subject: Re: org export as twiki - Failure to export with error: (wrong-type-argument stringp nil)
Date: Thu, 04 Mar 2010 21:08:49 -0800	[thread overview]
Message-ID: <byc8wa78ie6.fsf@muchbodyking-lm.corp.yahoo.com> (raw)
In-Reply-To: 4B900F08.3070401@ieee.org

"Mario E. Munich" <mariomu@ieee.org> writes:

> Dear Baoqiu,
>
> thanks a lot for the reply... I have done some level of debugging (I
> should have probably done it before, but I was not sure of what was
> going on) and I had realized that the problem is in using  brackets [ ]
> in the text.

Hi Mario,

Thanks for posting your example Org file.  Now I am able to reproduce
the problem and know where the bug is.

Just as what you said, the problem is caused by the last line that
contains strings "double[9]" and "double[3][3]".  Here "[9]" and "[3]"
are considered footnote references (and I don't think this is what you
expected), so some code is executed to find the footnote definitions.

The problem happens when the *second* "[3]" is being processed.
Strictly speaking, the second "[3]" is NOT considered as a footnote
reference according to ``org-footnote-re'' (see org-footnote.el), but
some code in org-docbook.el and org-html.el does not use
``org-footnote-re'' and still treats it as a footnote reference.  This
inconsistency causes the error you saw, which is only visible in
org-docbook.el.

Before I try to fix this problem, I would like to get the confirmation
from Carsten on the footnote syntax: whether the second "[3]", which
immediately follows a character "]", should be treated as a footnote
reference.

To get around of the problem, you can try changing the last line to
something like:

  - =double[9]= was less efficient that =double[3][3]=,

Please let me know if you have further questions.

> Please find enclosed a simple file that will depict the issue.
>
> Best regards,
>
> -Mario
> #+FILETAGS: personal
>
> * Converting org pages to Twiki
>   - use docbook2twiki http://code.google.com/p/docbook2twiki/ 
>     - Checkout docbook2twiki: <2009-09-24 Thu>
>       svn checkout http://docbook2twiki.googlecode.com/svn/trunk/ docbook2twiki-read-only
>       - retrieved r5 from that repository
>     - Load org-twiki.el
>     - Publish buffer with: M-x org-export-as-twiki
>   - double[9] was less efficient that double[3][3],

Thanks,

-- 
Baoqiu

  reply	other threads:[~2010-03-05  7:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 19:50 org export as twiki - Failure to export with error: (wrong-type-argument stringp nil) Mario E. Munich
2010-03-05  5:08 ` Baoqiu Cui [this message]
2010-03-05  5:30 ` Baoqiu Cui
2010-03-05  7:47   ` Carsten Dominik
2010-03-05 18:51     ` Baoqiu Cui
2010-03-05  8:15   ` Mario E. Munich
  -- strict thread matches above, loose matches on Subject: below --
2010-03-03  8:48 Mario E. Munich
2010-03-04  2:26 ` Baoqiu Cui

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=byc8wa78ie6.fsf@muchbodyking-lm.corp.yahoo.com \
    --to=cbaoqiu@yahoo.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).