From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: Italics support fails after non-breaking space [8.2.6 (8.2.6-67-g9e09b2-elpa @ /home/crculver/.emacs.d/elpa/org-20140602/)]
Date: Mon, 09 Jun 2014 09:51:14 +0800 [thread overview]
Message-ID: <87d2eirgtp.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87ioob2cad.fsf@aura.christopherculver.com
Christopher Culver <crculver@christopherculver.com> writes:
> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen. You don't know how to make a good report? See
>
> http://orgmode.org/manual/Feedback.html#Feedback
>
> Your bug report will be posted to the Org-mode mailing list.
> ------------------------------------------------------------------------
>
> The code for changing the font face to italics assumes that the opening
> slash in text surrounded by /.../ will be preceded by a plain
> space. However, authors preparing documents with LaTeX or HTML output in
> mind may employ a non-breaking space before the text in italics (the
> Unicode character U+00A0 NO-BREAK SPACE).
>
> I encountered this bug with the text "Fi. /mennä/", where the only space
> is a non-breaking space (as it must be in any output to a typesetter for
> my needs). Emacs keeps the text within slashes in the normal font face
> instead of changing it to italics.
Check the variable org-emphasis-regexp-components -- the first two
elements specify what characters are allowed before and after an
emphasis delimiter. You could add the non-breaking space to both of
those elements, and it ought to work. I can't speak to potental gotchas
that might arise because of this, or whether this ought to be part of
the default value...
Hope that helps,
Eric
prev parent reply other threads:[~2014-06-09 1:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 23:48 Bug: Italics support fails after non-breaking space [8.2.6 (8.2.6-67-g9e09b2-elpa @ /home/crculver/.emacs.d/elpa/org-20140602/)] Christopher Culver
2014-06-09 1:51 ` Eric Abrahamsen [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=87d2eirgtp.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).