emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Václav Haisman" <vhaisman@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: non-breaking space before formatted text breaks the formatting [8.3.2 (8.3.2-51-g713fe8-elpa @ /home/wilx/.emacs.d/elpa/org-20151221/)]
Date: Sun, 17 Jan 2016 22:49:38 +0100	[thread overview]
Message-ID: <569C0C72.7040406@gmail.com> (raw)
In-Reply-To: <87egdfj32v.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

On 17.1.2016 22:42, Nicolas Goaziou wrote:
> Hello,
> 
> Václav Haisman <vhaisman@gmail.com> writes:
> 
>> * Testing output with non-breaking space
>>
>> This is to show issue with using Unicode’s non-breaking space character
>> before formatted text. Org-mode does not parse the formatting if the
>> non-breaking space is there.
> 
> Org indeed doesn't give any special meaning to Unicode's characters. For
> the time being you might want to tweak `org-emphasis-regexp-components'.
> 
>> I am using the non-breaking space character because I export some Org
>> documents using Pandoc into LaTeX to make a PDF. Pandoc then uses the
>> ’~’ character in the generated LaTeX document.
> 
> Out of curiosity, why do you need to go through Pandoc in order to
> generate LaTeX code?

I use the org-journal mode and each day has a different file. So I
convert all of them together into a single LaTeX file using Pandoc which
I further molest with a Perl script to produce a PDF.

-- 
VH


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

      reply	other threads:[~2016-01-17 21:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-17 11:55 Bug: non-breaking space before formatted text breaks the formatting [8.3.2 (8.3.2-51-g713fe8-elpa @ /home/wilx/.emacs.d/elpa/org-20151221/)] Václav Haisman
2016-01-17 21:42 ` Nicolas Goaziou
2016-01-17 21:49   ` Václav Haisman [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=569C0C72.7040406@gmail.com \
    --to=vhaisman@gmail.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).