From: Daniele Pizzolli <dan@toel.it>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: dates in heading break beamer export
Date: Wed, 02 Oct 2013 18:10:57 +0200 [thread overview]
Message-ID: <524C4591.9020804@toel.it> (raw)
In-Reply-To: <8761tfu0ov.fsf@gmail.com>
On 10/02/2013 05:55 PM, Nicolas Goaziou wrote:
> Daniele Pizzolli writes:
>
>> Yes, I think is fair to drop the markup.
>
> OK.
>
>> I would also think that this is safe default when nested markup is
>> bad.
>
> Do you have an exhaustive list of such cases?
No, not really but I try to report them as soon I found them. I do
want to replace latex entirely with org, so I will use it extensively
in the near future.
>> Maybe the exporter can emit a notice/warning.
>
> That it dropped the markup?
Yes, I do not know if there is already a standard in reporting back
but I would go for something like "Latex-exporter: Warning: dropped
code markup at line XX of originalorgfile.org because it is not
supported by this exporter. More info at ..." or even a shorter one
can be fine to me.
>> Yes, sorry, I mixed two not-so-related problem. The beamer exporter do
>> not work with this code:
>>
>> #+OPTIONS: H:3
>> * title test[fn:1]
>> ** section
>> *** subsection
>>
>> [fn:1] text
>
> Of course, that's a similar problem: footnotes are not allowed in
> headlines. Though, in this case, it isn't possible to drop the markup.
> What LaTeX code do you suggest?
Mmm, I think you are asking to the wrong person. I do not know enough
about latex and its error reporting capabilities...
I would appreciate if the exporter does not break and/or a
notification to the user of the problem in and understandable
language, even for newcomers.
I know when latex do not know how to resolve some references put some
question marks... but I do not really know if this is the case to
follow this convention.
Regards,
Daniele
next prev parent reply other threads:[~2013-10-02 16:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 10:33 Bug: dates in heading break beamer export Daniele Pizzolli
2013-09-29 14:53 ` Nicolas Goaziou
2013-09-29 15:27 ` Marcin Borkowski
2013-09-30 16:02 ` Daniele Pizzolli
2013-09-30 17:05 ` Marcin Borkowski
2013-10-01 16:01 ` Nicolas Goaziou
2013-10-01 16:33 ` Marcin Borkowski
2013-10-02 6:50 ` Bug: code and footnotes (was Bug: dates in heading break beamer export) Daniele Pizzolli
2013-10-01 8:09 ` Bug: dates in heading break beamer export Eric S Fraga
2013-10-02 6:47 ` Daniele Pizzolli
2013-10-02 13:45 ` Nicolas Goaziou
2013-10-02 15:36 ` Daniele Pizzolli
2013-10-02 15:55 ` Nicolas Goaziou
2013-10-02 16:10 ` Daniele Pizzolli [this message]
2013-10-02 20:47 ` Marcin Borkowski
2013-10-03 13:30 ` Nicolas Goaziou
2013-10-03 15:59 ` Daniele Pizzolli
2013-10-04 19:17 ` Nicolas Goaziou
2013-10-02 22:12 ` Suvayu Ali
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=524C4591.9020804@toel.it \
--to=dan@toel.it \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).