From: Carsten Dominik <carsten.dominik@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: bug: html export, latex fragments and emphasize
Date: Fri, 12 Nov 2010 07:22:21 -0600 [thread overview]
Message-ID: <23641707-153F-4F09-B3E1-2AF9CD5CA80F@gmail.com> (raw)
In-Reply-To: <87y68z2uv1.wl%n.goaziou@gmail.com>
On Nov 11, 2010, at 7:28 PM, Nicolas Goaziou wrote:
> Hello,
>
> Here is a problem when a latex fragment is split across two lines and
> an emphasize follows. The text won't be italicized upon exporting to
> HTML.
>
> =====
> * latex-fragments bug
>
> Imagine we have a formula starting here $e^{i\pi} +
> 1 = 0$. Now we have a problem with /emphasize/.
> =====
>
> This is because the line starts with a char with 'org-protected
> property and, thus, get caught by the "Protected HTML" (org-html.el
> l. 1216) part of `org-export-as-html'. In others words, the line is
> inserted as-is in the output buffer, before getting any
> transformation.
>
> I'm not sure how it should be done (I don't get yet the usefulness of
> this "Protected HTML" part), but that piece of code may be moved after
> the `org-html-expand' call, as long as every sub-function in
> `org-html-expand' has a check to prevent modifying protected stuff
> (this not yet the case for `org-export-with-emphasize' and
> `org-html-protect' while others seem ok).
>
> But even in this case, every function getting called after that would
> be ignored. So, for example, links would not be inserted.
>
> Couldn't the "Protected HTML" part be removed altogether?
Hi Nicolas,
I am not entirely sure if it could be removed. The origin of this
is to make begin_html ... end_html work to keep entire blocks
unmodified. It is possible that the code after this line by now has
enough checks for protectedness - but I am not sure.
For the time being, I have pushed a different fix which does fix the
specific issue you show, but will still fail if the math expression in
more than 2 lines :(
It might be worth while to switch the protected html part off and see
what happens - but that would have to be done on a special branch with
significant testing by a number of people.
Regards
- Carsten
prev parent reply other threads:[~2010-11-12 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 1:28 bug: html export, latex fragments and emphasize Nicolas Goaziou
2010-11-12 10:52 ` Eric S Fraga
2010-11-12 13:22 ` Carsten Dominik [this message]
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=23641707-153F-4F09-B3E1-2AF9CD5CA80F@gmail.com \
--to=carsten.dominik@gmail.com \
--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).